🎩 You're Invited:Meet the Socket team at Black Hat in Las Vegas, August 3-6.RSVP
Sign In

@borough/mcp

Package Overview
Dependencies
Maintainers
1
Versions
4
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@borough/mcp

MCP server for Borough NYC Real Estate API — search rentals, sales, property details, and building data across all five NYC boroughs

latest
npmnpm
Version
1.2.2
Version published
Maintainers
1
Created
Source

@borough/mcp

Remote MCP bridge package for Borough, a read-only NYC real estate connector for Claude, ChatGPT, Cursor, VS Code, and other MCP-compatible clients.

Borough MCP gives AI tools authenticated access to:

  • rental and sales search across the five boroughs
  • area and neighborhood discovery
  • market snapshots and trends
  • property and building detail tools for paid tiers
  • compact, chat-friendly responses designed for remote connector clients

Preferred Connection Model

For hosted MCP clients, use Borough's remote MCP endpoint:

https://borough.qwady.app/mcp

OAuth-capable clients should prefer the built-in Borough OAuth flow. That is the primary connector path for Claude and other hosted remote MCP clients.

Docs:

Remote Connector URL

https://borough.qwady.app/mcp

Discovery metadata:

https://borough.qwady.app/.well-known/mcp/server.json

Tool Access By Tier

Authenticated Free

  • search_rentals
  • search_sales
  • list_areas
  • get_market_snapshot
  • get_market_trends
  • compare_neighborhoods

Starter And Above

  • get_property
  • get_property_by_url
  • get_building
  • get_building_listings

All Borough MCP tools are read-only.

The search and market tools accept either area IDs or neighborhood names. Search tools also support compact amenity-aware filtering, including DISHWASHER and WASHER_DRYER.

Claude And Remote Clients

If your MCP client supports remote connectors and OAuth, use the hosted endpoint directly and complete the Borough sign-in flow when prompted.

For Claude-specific steps:

Direct Bearer-Token Usage

For MCP clients that do not support Borough's OAuth flow, use a Borough API key in the Authorization header:

Authorization: Bearer BOROUGH-<your_key>

Examples:

Cursor

{
  "mcpServers": {
    "borough": {
      "url": "https://borough.qwady.app/mcp",
      "headers": {
        "Authorization": "Bearer BOROUGH-<your_key>"
      }
    }
  }
}

VS Code

{
  "servers": {
    "borough": {
      "type": "http",
      "url": "https://borough.qwady.app/mcp",
      "headers": {
        "Authorization": "Bearer BOROUGH-<your_key>"
      }
    }
  }
}

npx Bridge Usage

This package is mainly useful when you want to bridge the hosted Borough MCP endpoint into a stdio-only client.

BOROUGH_API_KEY=BOROUGH-<your_key> npx @borough/mcp

BOROUGH_API_KEY is required for the direct stdio bridge path.

Example Questions

Ask your AI client:

  • "Find me 2-bedroom apartments in Williamsburg under $4,000"
  • "Find studios in Chelsea with dishwasher and in-unit washer/dryer"
  • "Compare rents between Astoria, Park Slope, and the East Village"
  • "Show me current market stats for Long Island City"
  • "Get details for property 4961849"
  • "Which buildings in Chelsea have the most active listings?"

Get Access

Support

For support, contact api@qwady.com.

Keywords

mcp

FAQs

Package last updated on 20 Jul 2026

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts