Casafari MCP

npx add-mcp 'https://mcp.casafari.com/'

Casafari API and MCP Platform

Casafari is the AI agent-native real estate data intelligence platform. The most complete property index in Europe: a deduplicated, cleaned property graph of residential and commercial property, for sale and for rent, in 16 countries.

Every property in the graph is one record, merged from every source that advertises it and cleaned, with its full history: every price change, every status change, when it came on the market and when it was delisted. Residential and commercial property alike, for sale and for rent. How the property graph is built.

Casafari's MCP servers connect AI assistants and agents to it as Model Context Protocol tools: place lookup, comparables and valuations, area insights, and agency and agent analysis. They are part of the Casafari API and MCP Platform, where each product is its own MCP server with its own URL and OAuth sign-in.

The same data is also available over a REST API (46 operations at https://api.casafari.com). Docs are organised by product, and each product lists its MCP tools and its REST operations; MCP and REST compared shows where the two overlap and where they do not.

Already a Casafari API customer? Your token keeps working, and the existing API's reference is now on this site. Log in to your API account to see your token.

Endpoints

One MCP server per product on the platform (Streamable HTTP, OAuth 2.1 sign-in in the browser, no key to copy):

• Location Lookup: https://platform.casafari.com/mcp/locations
• Area Insights: https://platform.casafari.com/mcp/area-insights
• Comparables: https://platform.casafari.com/mcp/comparables
• AgentGraph AI: https://platform.casafari.com/mcp/agentgraph (verified businesses only)
• Claro AI: https://platform.casafari.com/mcp/claro

In Claude Code, for example: claude mcp add --transport http casafari-comparables https://platform.casafari.com/mcp/comparables. In Claude or ChatGPT, add a custom connector with the product's URL. Steps for Claude, ChatGPT, Claude Code, Cursor, VS Code, Codex CLI, Gemini CLI, Zed and other clients: Connect and Connect to the Casafari Platform.

Already a Casafari client? Use the same servers: sign up at https://platform.casafari.com/console/, and if you have a contract, Casafari sets your account up on the Custom plan. mcp.casafari.com has been retired; use https://platform.casafari.com/mcp/<product>.

Each server publishes its own card at <server URL>/.well-known/mcp/server-card.json, for example https://platform.casafari.com/mcp/comparables/.well-known/mcp/server-card.json. Sign-in: Authentication.

Claro AI is a platform product too; with a platform API key instead of OAuth, see Connect Claro.

Products

Product	MCP tools	REST operations	What it answers
Property Sourcing	—	10	Find properties in the property graph, where every property is one record however many agencies and portals advertise it: search by structured filters or in plain language, page through the results, read one property with everywhere it is advertised and its price history, and resolve a portal or agency link or a reference to the property it belongs to. REST only.
High Potential Seller Leads	—	2	Homes likely to sell: properties around a point whose asking price was cut repeatedly, by how many cuts and how much in total, over their whole time on the market or since a date. Each lead links to its property and its price history. REST only; Spain, France, Italy, Germany, Greece and Andorra.
Comparables & Valuation	1	4	Comparable properties and estimated prices for a home: properties on the market, past sales and rentals, and official registry records, matched around a point, an address or a cadastral reference.
Area Insights	7	6	Insights for an area: price, supply and activity over time, distributions by price, bedrooms and time on market, and market analysis. Over MCP also growth and volatility measures and heatmaps by district.
New Market Leads	—	12	Alert feeds that follow the property graph for a set of filters: new properties, price rises and cuts, reservations, delistings and sales. Create a feed, read its alerts, or have them delivered to your webhook.
References	—	10	The reference data requests are built from: property types, features and conditions, agencies, agents and the sources the graph is built from, locations with typeahead, and zip-code boundaries.
AgentGraph AI	13	—	Find the real estate agencies and agents worth partnering with: area screens against partner profiles, full profiles, territory maps, partner briefs and watchlists.

Claro AI

Claro AI is Casafari's business expansion search agent for commercial premises across Spain. It is a platform product: its own MCP server and REST API on the platform, with a platform key or the platform's OAuth. Connect Claro.

How tools are named

Each server names its tools <server>_<tool>: the prefix is the last segment of the server's URL, the rest is the tool's own name, for example comparables_get-comparables, area-insights_get_heatmap or agentgraph_screen_agencies. Location Lookup's tools are locations_search and locations_get, and every server also has account_status. Always call a tool by its full name, as the server lists it.

An API for AI agents

Casafari is an API for AI agents in two forms, on the same property graph:

• The MCP servers (one per product under https://platform.casafari.com/mcp/), for agents that discover the tools and decide which to call: in Claude, ChatGPT and other MCP clients, or from your own code through the OpenAI API or the Claude API.
• The REST API (reference), for agents and apps whose code makes fixed requests.

These docs are written for agents too: every page is Markdown, and /llms.txt indexes them all.

Units, payment and verification

Every call costs a fixed number of units on your platform account, the same over MCP and REST. account_status, on every server, shows your plan and balance. When units run out, a tool answers with a payment error that carries a link a person opens to pay; AgentGraph AI's tools answer verification_required until the business is verified. Limits per plan: Limits.

Start with a location

Most data tools take a location as ids, a circle or a polygon rather than a name: resolve a place name to ids with Location Lookup's locations_search first (https://platform.casafari.com/mcp/locations, free). AgentGraph AI has its own agentgraph_find_location for Germany.

Read these docs as Markdown

Every page has a Markdown version: add .md to its URL, or send Accept: text/markdown. /llms.txt lists every page and tool; /llms-full.txt is the whole reference in one file. More in For AI agents.

Questions and answers

What is the difference between Casafari MCP and the Casafari REST API, and which should I use?

Use MCP when an AI assistant or agent calls Casafari's data as tools; use REST when your own code calls it over HTTP. The products differ between the two.

If you're a Casafari client: the Casafari REST API (https://api.casafari.com) stays as it is, with 39 operations; POST /login with email and password returns an access and a refresh token. Property Sourcing, New Market Leads (alerts) and References are REST only there. For MCP, use the self-serve platform's servers like everyone else: sign up, and if you have a contract, Casafari sets your account up on Custom. See MCP and REST compared and REST API.

If you're new to Casafari: on the self-serve platform, MCP serves assistants, which sign in with OAuth 2.1 and need no key (Authentication), for Location Lookup, Area Insights, Comparables & Valuation, AgentGraph AI and Claro AI. REST serves your code, with an API key or an OAuth client, for Account, Location Lookup, Area Insights, Property Sourcing, High Potential Seller Leads, Alerts, Comparables & Valuation and Claro AI. Every operation costs the same number of units over REST and MCP.

See which address to use and MCP-only and REST-only.

Permalink: /docs/faq/mcp-vs-rest-api

How does authentication work on Casafari MCP? Does it use OAuth scopes?

Casafari MCP signs in with OAuth 2.1 on the self-serve platform's MCP servers, with no API key; the REST APIs sign in with separate credentials.

If you're a Casafari client: the Casafari REST API takes a JWT from email and password, or a token for an API client (REST authentication), as before. For MCP, you sign in to the self-serve platform's servers like everyone else, with a platform account.

If you're new to Casafari: assistants sign in to the self-serve platform's MCP servers with OAuth 2.1 and dynamic client registration; no key is needed. Which OAuth scopes that sign-in uses is not published. The platform's REST API takes an API key (cf_sk_…) in the X-API-Key header or as Authorization: Bearer <api_key>, or an OAuth client using client credentials with the resource parameter, whose tokens last 15 minutes (key or OAuth client?).

See Authentication and REST API.

Permalink: /docs/faq/how-authentication-works

Who can use Casafari MCP and the Casafari API?

Anyone can sign up at platform.casafari.com without talking to sales, and that is where every assistant connects over MCP; existing Casafari clients also keep their Casafari REST API contract.

If you're a Casafari client: your Casafari REST API access stays bound to your Casafari account and contract, and a token carries exactly that account's rights; an unattended integration uses an API client the account owner creates (REST authentication). For MCP, sign up on the self-serve platform like everyone else; if you have a contract, Casafari sets your account up on Custom (Connect your assistant).

If you're new to Casafari: anyone can create an account at https://platform.casafari.com, start on the Free plan, a trial that needs no card, and pay by usage. No business verification is needed, except for AgentGraph AI, which holds personal contact data of real estate agents (verification). A Free account has 1 member and an Agent account 3 (plans). Steps: how to sign up.

Not sure which route is yours? See which address to use.

Permalink: /docs/faq/who-can-use

What are Casafari's rate limits, quotas and usage limits?

Casafari publishes no rate-limit or quota figures for existing REST API contracts; the self-serve platform meters usage in units, with limits set per plan: Free, Agent and Custom, published on Limits and usage windows.

If you're a Casafari client: for quota and rate-limit figures on the Casafari REST API, contact Casafari: https://www.casafari.com/ (quota versus units). Over MCP you use the self-serve platform, where the limits below apply to your account; if you have a contract, Casafari sets it up on the Custom plan, with limits per contract.

If you're new to Casafari: usage is metered in units, the same over REST and MCP; place lookups cost 0.

• Free: 1,000 units for 30 days (free trial); 2 requests in flight, 10 a minute, 10 places a day.
• Agent: 1,000 units per rolling 3 hours and 4,000 per rolling 7 days (usage windows); 3 requests in flight, 20 a minute, 50 places a day, and a hard cap of 50,000 units a day, a security guard against bulk data extraction (limits). Extra usage comes from prepaid credits only, capped by default at 25,000 units (€1,000, excluding VAT) per subscription period.
• Accounts on credits (no plan or a cancelled subscription): Agent's request guards and at most 25,000 units a day.
• Custom: limits per contract; "Contact us".

Over REST, a used-up Agent window with no credits answers 429 usage_limit_reached with its refill time, and running out of units 402 payment_required; MCP answers a payment error (out of units). A used-up request guard answers 429 request_limit_reached with Retry-After. Every limit is on Limits and usage windows.

Permalink: /docs/faq/rate-limits-and-quotas

Can I read these docs as Markdown, and is there an llms.txt?

Yes: add .md to any page's URL or send Accept: text/markdown, and /llms.txt indexes every page and tool. None of it needs a key.

• /llms.txt is the index, and /llms-full.txt holds the whole reference in one file.
• /tools.json gives every tool's name, title, input schema and output schema.
• You'll also find the API catalog, MCP server card, agent skill, agentic resource manifest and the sitemap at /sitemap.xml.
• Markdown responses are served as text/markdown, with an x-markdown-tokens header that estimates their size.
• In a browser that supports navigator.modelContext, pages register these WebMCP tools: search_casafari_mcp_docs, get_casafari_tool_reference, get_casafari_rest_operation, get_casafari_connection_config and open_casafari_docs_page.
• The self-serve platform publishes its own https://platform.casafari.com/llms.txt and https://platform.casafari.com/llms-full.txt, plus an OpenAPI for each product.

See: For AI agents.

Permalink: /docs/faq/machine-readable-docs

All questions