MCP setup

Nosy Neighbor is a remote MCP server for New York City property data. Add it to any MCP client with the URL below. Nothing to install.

Add the server

Claude Code, one command:

claude mcp add --transport http nosy-neighbor https://mcp.nosyneighbor.nyc/mcp

Every other client takes the same URL as a config entry. Paste this into your Claude Desktop config (Settings, Developer, Edit Config), a project .mcp.json, or your editor’s MCP settings:

{
  "mcpServers": {
    "nosy-neighbor": {
      "url": "https://mcp.nosyneighbor.nyc/mcp"
    }
  }
}

The endpoint on its own, for a client that asks only for a URL:

https://mcp.nosyneighbor.nyc/mcp

First connection

The server speaks streamable HTTP with OAuth 2.1 and registers each client on the fly, so the URL is all most clients need. On first connect your client opens a browser window for Google sign-in. Approve it once and the grant is remembered.

MCP access is a Pro feature. A free account can complete the OAuth handshake, and the grant is only issued to a Pro account. See Pricing to upgrade, and the developer dashboard to check your tier.

Tools

The MCP tool names, one per REST operation:

• lookup_property
• search_listings
• get_comps
• get_rental_estimates
• get_mortgage_rates
• get_listing_updates

Parameters, response fields and per-call costs are documented once for both surfaces on the REST API guide, the API reference and Rate Limits. Coverage is the five boroughs of New York City. An address or area outside them returns a short coverage message.

Troubleshooting

• Tools list is empty, or the connection is refused. Confirm the URL includes the /mcp path, and that you completed the OAuth consent screen (some clients silently fail the handshake rather than surfacing the prompt, so try reconnecting the server).
• "Forbidden" or tools return empty results. MCP requires a Pro account (above). Check your tier on the developer dashboard.
• Prompted to re-accept Terms of Use. Consent is not one-time. It is tied to the current Terms version, so a Terms update re-gates every user (API and MCP callers included) on their next call until they accept again. Sign in to the web app once to clear it, then retry the MCP call.
• NYC-only coverage. Every tool rejects an address or area outside the five boroughs with a short message rather than a partial answer. This is expected behavior, not an error to work around by retrying elsewhere.
• Rate limited. API and MCP calls share one allowance. See Rate Limits for the numbers.