Yatmo MCP server

A read-only Model Context Protocol server that lets AI agents, assistants and real-estate copilots query Yatmo’s neighbourhood intelligence with well-described tools instead of mapping the REST API by hand.

What is the Yatmo MCP server?

The Yatmo MCP server is a thin AI-ready façade over the existing Yatmo REST API. It exposes the same neighbourhood data — nearby schools, nurseries, supermarkets, public transport, train stations, motorway access, accessibility profiles — as Model Context Protocol tools that AI clients (Claude, Cursor, in-house agents, real-estate copilots) can call directly.

It is hosted at https://mcp.yatmo.com and is read-only by design: no writes, no SQL, no destructive operations, no separate sign-up.

Who is it for?

• Real-estate portals building “find me a property near a school and the metro” natural-language search.
• CRMs and multi-site groups embedding an AI assistant on listing pages.
• Integrators wiring Claude.ai, Cursor or any remote-MCP-capable client to neighbourhood data.
• Yatmo plugin users who want to layer conversational AI on top of an existing map / summary integration.

Endpoint

Single MCP endpoint, versioned in the URL:

POST https://mcp.yatmo.com/mcp/v1
Header: LicenceKey: <your-yatmo-key>

The same LicenceKey you already use for the Yatmo REST API works here — no additional sign-up or OAuth. Country authorisation inherits from your existing Yatmo plan.

Tools at a glance

• yatmo_get_location_summary — human-readable neighbourhood paragraph plus structured facts (nearest school, nursery, supermarket, transport, reverse-geocoded place).
• yatmo_get_nearby_pois — points of interest around a property, filterable by category, within a radius.
• yatmo_get_nearest_by_category — single nearest POI for a category, with distance and travel time.
• yatmo_get_accessibility_profile — public-transport presence, nearest stop, nearest train station, nearest motorway access.

Full list of categories: school, nursery, supermarket, public_transport, train_station, motorway. school returns actual schools (preschool through high school) and excludes daycare; nursery returns crèches / daycare only.

Coverage

Belgium, France, the Netherlands, Luxembourg, Germany, Switzerland, Spain, Italy, Portugal, the United Kingdom, Ireland, Austria, Canada, Greece, Morocco, Australia, Croatia, Malta, Slovenia, Serbia, Cyprus, Bosnia and Herzegovina, Montenegro, Bulgaria, and Albania. Each call requires a country argument and your licence must include that country — see Countries & languages.

MCP vs REST API — which to use?

• Use the MCP server when your client is an AI assistant or agent: Claude.ai, Cursor, an in-house LLM agent. The tools come with descriptions, structured input schemas and AI-shaped responses.
• Use the REST API when you need lower-level control or fields the MCP doesn’t expose, when you bulk-process listings, or when you call from a non-AI backend.
• You can mix and match — both use the same LicenceKey and the MCP tools internally call the REST API.

Next steps

• Quick start — first MCP call from the shell in five minutes.
• Connect an AI client — ready-to-paste JSON config for Claude, Cursor and generic remote-MCP clients.
• Authentication — LicenceKey details and error codes.
• FAQ — common questions about browser usage, OAuth, and the school/nursery split.