Skip to main content

What is Borough MCP?

Borough provides a Model Context Protocol (MCP) server that lets AI agents query NYC real estate data through natural language tool calls. Instead of writing code to call the REST API, you can ask your AI assistant questions like:
  • “Find me 2-bedroom apartments in Williamsburg under $4,000/month”
  • “Compare rents between Park Slope, Astoria, and the East Village”
  • “Get details on property 4961849”
The MCP server exposes 10 tools that map to Borough’s REST API endpoints, with the same tier-based access, rate limits, and quota enforcement.

How It Works

Authenticated MCP sessions are mapped to Borough tiers, so the same tool restrictions, rate limits, and monthly quotas apply as the REST API.

Authentication Methods

Borough MCP supports two connection patterns: OAuth is the recommended method for MCP clients that support it. Free-tier MCP access is available through the Borough auth flow, and paid Borough API keys enable additional MCP tools.

Compact and location-aware by default

Borough MCP is optimized for chat clients:
  • search and building-listing tools return small default result sets
  • tool responses are compact projections instead of full raw API payloads
  • exact neighborhood names such as Chelsea, Astoria, or Park Slope can be resolved directly without manually looking up IDs first (each name resolved costs one extra API request; pass numeric area IDs to avoid it)
  • list_areas is the safest path when you want to lock a precise area ID before searching
  • if a location is ambiguous, Borough returns a short clarification list instead of a large fallback payload
  • search and building-listing results include render-oriented fields such as price, displayPrice, geoPoint, leadPhotoUrl, and renderHints
  • photo rendering is still client-dependent in this version because Borough returns photo URLs, not inline MCP image blocks

Available Tools

Next Steps

Quick Start

Get connected in 2 minutes

Tools Reference

Detailed tool documentation