Prerequisites
- An MCP-compatible AI client
- Optional: a Borough API key from a paid plan if you want paid-tier tools. Clients that support MCP OAuth (such as Claude) can use the free tools (search, areas, and market data) without one: choose Continue without key on the consent screen. Keyless free usage is counted per connecting IP address, so with a hosted client it may be shared with other users; see MCP Server
Remote Connection (Recommended)
Most MCP clients support connecting to remote servers directly. Use the Borough MCP endpoint:Authorization header. This needs a key from a paid plan; the keyless free tier is only available through the OAuth consent flow.
Client Setup
- Claude Connectors
- Claude Desktop
- Cursor
- VS Code
- npx
Borough supports an OAuth-based connector flow for Claude custom connectors.
- In Claude, go to Settings → Connectors
- Click Add custom connector
- Enter the URL:
https://borough.qwady.app/mcp - Claude auto-discovers the OAuth flow and opens the consent page
- Enter your Borough API key to enable paid tools, or continue without a key for the free Borough MCP tool set
- Click Authorize
See Add Borough to Claude for the exact current flow, including free-plan and team/org setup.
ChatGPT (GPT Actions)
ChatGPT does not support MCP natively. Instead, you can create a custom GPT with an Action that calls the Borough REST API directly using the Borough OpenAPI spec:- Go to ChatGPT GPT Builder
- Under Actions, click Create new action
- Import the OpenAPI spec from the URL above (or paste the YAML)
- Under Authentication, select API Key with header
Authorizationand prefixBearer - Enter your Borough API key (from a paid plan) as the value
Test It
Once connected, try asking your AI agent:- “Search for no-fee 1-bedroom apartments in Manhattan under $3,500”
- “List all Brooklyn neighborhoods”
- “What’s the median rent in the East Village?”
Troubleshooting
If tools aren’t showing up:- If you connected with an API key, verify your subscription is active in the customer portal
- Check that the MCP endpoint is reachable:
curl https://borough.qwady.app/mcp(a401response is expected and confirms it’s up; the endpoint requires authentication) - Restart your AI client after configuration changes
- See the troubleshooting guide for more help