Borough NYC Real Estate API
Query NYC rentals, sales, building records, and market analytics from an agent while scoping proptech ideas or wiring Borough data into a product.
Overview
Borough is a MCP server for the Idea phase that lets agents search NYC rentals, sales, buildings, and market analytics via Borough’s real-estate API.
What is this MCP server?
- Search NYC rentals and sales with property and building detail tools
- Market analytics oriented to New York City parcels and listings
- Hosted remote at borough.qwady.app/mcp plus npm package @borough/mcp (npx)
- Requires BOROUGH_API_KEY—free tier available at borough.qwady.app/pricing
- Server version 1.1.0 with GitHub source at jdmay2/borough packages/mcp-server
What problem does it solve?
NYC market research from scratch means juggling listing sites and incomplete building records while your agent cannot query structured property data in one place.
Who is it for?
Indie proptech or investment researchers focused on New York City who want MCP-native comps and building intelligence.
Skip if: Builders outside NYC who need national MLS coverage or offline-only datasets with no API key.
What do I get? / Deliverables
You get agent-callable NYC property and market answers backed by Borough’s API for research notes, validation, or product prototypes.
- Agent-queryable NYC rental and sales search results
- Property, building, and market analytics snippets for specs or dashboards
Recommended MCP Servers
Journey fit
Market and parcel intelligence belongs earliest in the journey when you are deciding whether an NYC real-estate angle is worth building. Research subphase covers competitive and market analytics—rent comps, building attributes, and sales trends—before you commit engineering time.
How it compares
NYC property data MCP integration, not a generic CRM or mortgage calculator skill.
Common Questions / FAQ
Who is app.qwady/borough for?
Solo builders and analysts working on NYC real estate—rental tools, investment memos, or agent apps—who want structured listings and building data through MCP.
When should I use app.qwady/borough?
Use it during market research, MVP scoping for NYC proptech, or when integrating Borough’s API into an agent-driven workflow with a BOROUGH_API_KEY.
How do I add app.qwady/borough to my agent?
Either add the remote MCP URL https://borough.qwady.app/mcp or run npx @borough/mcp with BOROUGH_API_KEY set from https://borough.qwady.app/pricing, per docs at https://docs.qwady.app.