Standardised MCP for
Property Insights
Use one remote Streamable HTTP MCP endpoint to expose all documented Property Insights API Hub tools directly to Claude, Cursor, and other AI agents.
Connection Details
Use your existing API key as bearer auth. Credits, rate limits, and usage logs stay on your current API account.
MCP Endpoint
https://mcp.propertyinsights.co.uk/mcp
Authorisation Header
Authorization: Bearer YOUR_API_KEY
Architecture Features
- Thin Proxy ToolingDirect MCP representations of all 46 documented API Hub tools.
- Schema ValidationStrict real-time input validation to guarantee clean API requests.
- Safety GuardrailsBuilt-in timeouts, automatic retries, strict response size capping, and session limits to protect context windows.
- Native RoutingAutomatic, transparent forwarding to production
/api/v1/*routes.
Billing details in MCP tool results
MCP forwards the complete upstream API response. For a successful chargeable call, read structuredContent.data.billing to see the charge, remaining prepaid balance and next refresh timestamp.
"billing": {
"mode": "prepaid",
"creditsCharged": 1,
"creditsRemaining": 1999,
"creditsRefreshAt": "2026-08-14T09:30:00.000Z"
}Failed upstream calls are not charged.
Client Configuration Guide
Ready-to-use snippets for your AI IDE or CLI agent.
Claude Desktop / CLI
Run this in your terminal to automatically configure the MCP server:
Or manually add it to ~/.claude/settings.json:
Cursor IDE
Add the definition to .cursor/mcp.json in your project root folder:
Custom Integrations
If you are building your own MCP host via the official SDKs (e.g. OpenAI Codex), wire it up to our stream URL over HTTP transport.
https://mcp.propertyinsights.co.uk/mcp
Authorization: Bearer YOUR_API_KEY