Connect to the Casafari Platform
The self-serve Casafari API and MCP Platform at https://platform.casafari.com: you sign up on your own, start on the Free plan with 1,000 tokens for 30 days and no card, and pay by usage after that. This page shows the two ways in: an AI assistant over MCP, or your own software over REST. Casafari's MCP servers are all here, for existing Casafari clients too (mcp.casafari.com is the legacy gateway, still answering, moving to https://platform.casafari.com/mcp/<product>); a client with a contract is set up on the Custom plan. For the existing REST API, see Moving from the existing Casafari API.
Which way in
| You are connecting | Use | Sign-in |
|---|---|---|
| An AI assistant or agent (Claude, ChatGPT, Cursor, VS Code, Codex CLI, Zed, any MCP client) | The one MCP server, https://platform.casafari.com/mcp | OAuth 2.1 in the browser; no key |
| Your own software, a script or a backend | The product's REST API at https://platform.casafari.com/v1/<product> | An API key (cf_sk_...) from the console |
Connect an AI assistant
Add one connector, https://platform.casafari.com/mcp, sign in once, and every product's tools are there:
https://platform.casafari.com/mcp- In your client, add a custom MCP connector, or a remote MCP server entry, named
Casafariwith that URL. Where each client takes it is under Client by client. - The client registers itself (OAuth 2.1 with dynamic client registration and PKCE) and opens Casafari's sign-in page in your browser. Sign in or create your account there, accept the Platform Terms of Use and approve. A new account starts on the Free plan. No key goes in any client.
- Ask a question. The tools are named after their product (
comparables_get_comparables,area-insights_get_heatmap);locations_searchandaccount_statusare free.
Alerts is REST only: it has no MCP server. High Potential Seller Leads is REST only too. See MCP or REST API?.
Using Claude Team or Enterprise? In a company Claude workspace only an organisation owner can add a custom connector; members see Add custom connector greyed out ("Ask an organization owner to add this for your team"). An owner adds the one connector once, under Organization settings → Connectors → Add custom connector, named Casafari with the URL https://platform.casafari.com/mcp.
Each member then chooses Connect on the connector and signs in with their own Casafari Platform account, so plans and usage stay with each person's account. No owner at hand? Claude Code adds a server for you alone: claude mcp add --transport http casafari https://platform.casafari.com/mcp.
A client that needs the authorization server's address reads it from https://platform.casafari.com/.well-known/oauth-authorization-server.
Client by client
Every line uses the one server, https://platform.casafari.com/mcp, with the entry name casafari. Sign-in is OAuth in every one: the client opens Casafari's sign-in page in your browser at the step the line names.
- Claude (claude.ai, Claude Desktop, the mobile apps): Customize → Connectors → + Add → Add custom connector, paste the URL, then Connect (on Claude Team or Enterprise an owner adds it, as above).
- ChatGPT: turn on developer mode, create a connector with the URL and choose OAuth.
- Claude Code:
claude mcp add --transport http casafari https://platform.casafari.com/mcp, then/mcpand Authenticate. - Cursor:
"casafari": { "url": "https://platform.casafari.com/mcp" }undermcpServersin~/.cursor/mcp.json; sign-in opens on first connect. - VS Code:
"casafari": { "type": "http", "url": "https://platform.casafari.com/mcp" }underserversin.vscode/mcp.json; sign-in opens on first connect. - Codex CLI:
codex mcp add casafari --url https://platform.casafari.com/mcp, thencodex mcp login casafari. - Gemini CLI:
gemini mcp add --transport http casafari https://platform.casafari.com/mcp, then/mcp auth casafari. - Devin Desktop (formerly Windsurf):
"casafari": { "url": "https://platform.casafari.com/mcp" }undermcpServersin~/.config/devin/mcp_config.json; sign-in opens on first use. - Visual Studio:
"casafari": { "url": "https://platform.casafari.com/mcp" }underserversin%USERPROFILE%\.mcp.json, then Manage Authentication in the CodeLens. - Zed: Settings → AI → MCP Servers → Add Server → Add Remote Server, or
"casafari": { "url": "https://platform.casafari.com/mcp" }undercontext_serversin~/.config/zed/settings.json; sign-in opens on connect. - Cline: MCP Servers → Remote Servers:
https://platform.casafari.com/mcp, transport Streamable HTTP; sign in in the browser (Cline CLI:cline mcp, Authorize OAuth). - JetBrains Junie:
"casafari": { "url": "https://platform.casafari.com/mcp" }undermcpServersin~/.junie/mcp/mcp.json, then Authorize from/mcpin Junie CLI. - Kiro:
"casafari": { "url": "https://platform.casafari.com/mcp" }undermcpServersin~/.kiro/settings/mcp.json; sign-in opens on connect. - Warp: Settings → Agents → MCP servers → + Add:
{ "casafari": { "url": "https://platform.casafari.com/mcp" } }; sign-in opens on first start. - goose:
goose configure→ Add Extension → Remote Extension (Streamable HTTP):https://platform.casafari.com/mcp; sign-in opens on first use.
One product at a time
Each product is also its own server, for a connector limited to one product or an existing connection:
- Location Lookup:
https://platform.casafari.com/mcp/locations - Area Insights:
https://platform.casafari.com/mcp/area-insights - Comparables:
https://platform.casafari.com/mcp/comparables - Comparables with Transactions:
https://platform.casafari.com/mcp/comparables-transactions - Property Sourcing:
https://platform.casafari.com/mcp/property-sourcing - Private Seller Leads:
https://platform.casafari.com/mcp/private-sellers - AgencyGraph:
https://platform.casafari.com/mcp/agencygraph - Cadastre:
https://platform.casafari.com/mcp/cadastre - Parcel Zoning:
https://platform.casafari.com/mcp/parcel-zoning - Claro AI:
https://platform.casafari.com/mcp/claro
For one of these, use its URL in the lines above and name the entry casafari-<product>. Each is its own protected resource with its own sign-in.
Call it from software
- Open the console at https://platform.casafari.com/console, sign in and create an API key. It starts with
cf_sk_and is shown once: store it like a password. - Send it as a bearer token on every request:
Authorization: Bearer <api_key>. (X-API-Key: <api_key>is accepted too.) - Call the product's base path,
https://platform.casafari.com/v1/<product>.
First call: Location Lookup
Every other product takes places as location ids, and looking them up is free (0 tokens):
curl "https://platform.casafari.com/v1/locations/search?query=Lisbon" \
-H "Authorization: Bearer $CASAFARI_API_KEY"Pass the ids it returns to Area Insights, Property Sourcing, Comparables or Alerts. Each product's operations and token costs are in its OpenAPI description at https://platform.casafari.com/v1/<product>/openapi.json, and the whole API is at https://platform.casafari.com/v1/openapi.json.
Agents that sign up on their own
An AI agent can open a trial account for a person through the Platform's sign-up API: GET https://platform.casafari.com/v1/signups/terms returns the current terms version, POST https://platform.casafari.com/v1/signups starts the sign-up, and the person enters the code sent to their email, which accepts the terms and opens the account. The endpoints are described at https://platform.casafari.com/v1/openapi.json.
See your usage
The console at https://platform.casafari.com/console shows your usage and balance. An assistant can call the account_status tool that every product MCP server has, and software can call GET https://platform.casafari.com/v1/account. What each plan includes, the usage limits and what happens when you reach one are on Limits.
Plans and terms
Free: 1,000 tokens for 30 days, no card. Agent: EUR 49 a month, or EUR 39 a month billed yearly, with 1,500 tokens a month. Agency: EUR 149 a month, or EUR 119 a month billed yearly, with 5,000 tokens a month. Custom: for larger needs. Extra usage is bought as credits at EUR 0.04 a token. Prices exclude VAT. Every plan is on Pricing. Use of the Platform is governed by the Platform Terms of Use and personal data is handled under the Platform Privacy Notice.