Skip to main content
Connect PAID to Claude and ask about UK property in plain English. Claude queries our data directly and reasons over the results — no copying figures between tabs.
Free to try. Every account includes 200 credits a month, no card required. A full working-up of one property — search it, value it, pull the comparables, then fetch the full report — costs 14 credits, so the free allowance covers roughly 14 complete property analyses a month. See what the free credits buy for the arithmetic.

​
What Claude can do once connected

The comparables are the part worth knowing about: every comparable carries a confidence tier — gold, silver, bronze, supporting or excluded — and sales that were repossessions, right-to-buy, auctions or family transfers are flagged as non-standard, as are likely flips. Those flagged sales are capped at supporting however well they otherwise match, because the price reflects a distressed or related-party sale rather than open-market value. Claude is told to treat them with caution when averaging, so a headline ”£/sqft” is not quietly skewed by a repossession three doors down. A draw that comes back entirely supporting is therefore a real answer about a hard-to-match subject, not an empty result.

​
Connect from claude.ai

1

Sign in to PAID

You need a PAID account — sign up free. The MCP connection is tied to your account, and your credit allowance is shared with any REST API keys you hold.
2

Add the connector in Claude

In claude.ai, go to Settings → Connectors → Add custom connector and enter exactly:
3

Authorise

Claude opens the PAID sign-in page (our authorisation is handled by Clerk, the same provider that signs you into the dashboard). Sign in if you aren’t already, review the consent screen, and approve. You are returned to Claude with the seven tools available. The token Claude receives works only against the MCP server — it cannot be replayed against your dashboard session.
4

Ask something

Try: “Using PAID, what would a 2-bed flat in M1 4BT be worth, and what comparable sales support that?”

​
Connect from Claude Desktop

Claude Desktop shares connectors with your claude.ai account. Add the connector once — Settings → Connectors → Add custom connector → https://api.propaideals.co.uk/mcp — either in the desktop app or on the web, authorise as above, and it is available in both.

​
Connect from Claude Code

Add the server from your terminal:
Then, inside a Claude Code session, run /mcp and pick paid-property to complete the OAuth sign-in in your browser. Once authorised, ask things like:
To remove it later: claude mcp remove paid-property. Authorisation is standard OAuth 2.1 with PKCE, run by Clerk on our behalf:
  1. Your MCP client discovers the authorisation server from the protected-resource metadata at https://api.propaideals.co.uk/.well-known/oauth-protected-resource.
  2. It registers itself automatically (RFC 7591 dynamic client registration) — no client id to copy anywhere.
  3. You sign in with your normal PAID account and approve the consent screen.
  4. The client receives an access token whose audience is the MCP server only. We validate signature, expiry and audience on every request; dashboard session tokens are rejected here, and MCP tokens are rejected at the dashboard.
Removing the connector in Claude (or in Claude Code, claude mcp remove) stops further access; tokens are short-lived and expire on their own.

​
Credit costs per tool

Discovery is free — listing the tools never costs anything. Each tool call costs the sum of the underlying REST endpoints it fans out to (REST and MCP share one cost table, so there is nothing separate to learn): Your usage is visible at /dashboard/api. When the monthly allowance runs out, Claude receives a clear message and stops calling the tools rather than failing silently.

​
What the free 200 credits buy you

A typical full analysis of one property: 200 credits ÷ 14 ≈ 14 complete property analyses a month, free. Lighter usage stretches much further — an area check (get_area_market, 4 credits) fifty times a month fits inside the free allowance on its own.

​
Plans

MCP calls and REST API calls draw from one shared monthly allowance on your account. Any plan below applies to both: If you already subscribe to a paid platform plan, MCP access is included — no separate API subscription needed. Starter includes 1,000 credits/month, Pro 5,000, and Max 10,000. Sign in with the same account and it is picked up automatically. The Starter and Growth API tiers are rolling out now and appear at checkout as they go live; Advanced is the plan previously sold as Starter. Full ladder: Rate limits › Plan comparison.

​
Troubleshooting

The connector shows zero tools. This is protocol-version negotiation, not an auth problem: a server and client that fail to agree a protocol revision produce an empty tool list. Our server speaks every revision from 2025-06-18 through 2026-07-28, so first remove and re-add the connector (stale sessions pin an old negotiation), and update your Claude client if it is very old. If it persists, email us with the approximate time — we log the version each handshake requested. 401 on every call after connecting. Almost always an audience mismatch — the token was minted for a different resource than the server expects. Check the connector URL is exactly https://api.propaideals.co.uk/mcp (no trailing slash, no www.), then remove and re-add the connector so a fresh token is issued for the right audience. Rejected audiences are logged on our side with the exact value the token presented, so support can resolve a stubborn case quickly. Tools stop mid-conversation with a quota message. You have used the month’s credits. Check usage at /dashboard/api; upgrade or wait for the month to roll over. Nothing is broken — the server refuses cleanly rather than failing silently. A property tool returns “not found”. score_deal, get_property_details and get_property_report key on a property UUID that comes from search_properties (the postcode-keyed tools — search, valuation, comparables, area market — don’t need one). Ask Claude to search first; ids from outside the platform (portal URLs, other APIs) will not resolve.

​
Notes for developers

  • Transport: Streamable HTTP at POST /mcp. Protocol revisions 2025-06-18 through 2026-07-28 are all served, so the endpoint works with older and newer clients alike.
  • Authorisation: OAuth 2.1. The server publishes RFC 9728 protected-resource metadata at /.well-known/oauth-protected-resource; tokens are validated for signature, expiry and audience.
  • No AI proxying. The MCP server exposes data tools only. Claude does the reasoning; we do not bill you for a second model behind the scenes.
  • One quota. MCP calls and REST API calls draw from the same monthly allowance on your account, so there is nothing to reconcile between them.
  • Costs are the REST costs. Each tool’s credit price is the sum of the per-endpoint request costs of the endpoints it wraps — a single cost table governs both surfaces.
For the REST API covering the same data, see the Quickstart.