Yatmo MCP — frequently asked questions

Q: What is the Yatmo MCP server?

The Yatmo MCP server is a read-only Model Context Protocol facade in front of the Yatmo REST API. It exposes neighbourhood intelligence — nearby schools, nurseries, supermarkets, public transport, train stations, motorway access and accessibility profiles — as MCP tools that AI agents (Claude, Cursor, in-house copilots) can call directly. Hosted at https://mcp.yatmo.com.

Q: What can the Yatmo MCP server do?

Four read-only tools: yatmo_get_location_summary (neighbourhood paragraph plus structured nearest school, nursery, supermarket, transport), yatmo_get_nearby_pois (POIs around a property filtered by category and radius), yatmo_get_nearest_by_category (single nearest school, nursery, train station, motorway, supermarket, etc.), and yatmo_get_accessibility_profile (transit presence, nearest stop, nearest train station, nearest motorway access).

Q: Do I need a separate licence for the Yatmo MCP server?

No. The Yatmo MCP server reuses your existing Yatmo LicenceKey. The same key works for the REST API and the MCP server, and quotas count against the same daily allowance.

Q: Does the Yatmo MCP server support OAuth?

Not in v1. Authentication is a single LicenceKey HTTP header (the same one used by the Yatmo REST API). OAuth is on the roadmap for clients that want per-user delegation; for now, treat the LicenceKey as a server-side secret.

Q: Is the Yatmo MCP server read-only?

Yes, by design. There is no create_, update_ or delete_ tool, no SQL, and no free-form query tool. An AI agent connected to Yatmo cannot mutate any data — it can only read neighbourhood intelligence.

Q: What is the difference between school and nursery in the Yatmo MCP server?

school returns actual schools — preschool, primary, secondary and high school — and excludes daycare. nursery returns crèches and daycare only. yatmo_get_location_summary surfaces both as nearestSchool and nearestNursery in the same response.

Q: Can I call the Yatmo MCP server from a browser?

No. The LicenceKey grants quota-bearing access to your account and must never be exposed in client-side JavaScript. Use the Yatmo plugins for browser integration (they use a separate frontend key with stricter limits) or proxy the MCP server through your own backend.

Short answers to the questions developers and AI integrators ask before adopting the Yatmo MCP server.

What is the Yatmo MCP server?

The Yatmo MCP server is a read-only Model Context Protocol façade in front of the Yatmo REST API. It exposes neighbourhood intelligence — nearby schools, nurseries, supermarkets, public transport, train stations, motorway access and accessibility profiles — as MCP tools that AI agents (Claude, Cursor, in-house copilots) can call directly. Hosted at https://mcp.yatmo.com.

How is the Yatmo MCP server different from the Yatmo REST API?

Same data, different shape. The MCP server speaks the Model Context Protocol so an AI client can discover and call tools by description, while the REST API speaks HTTP/JSON for traditional backends. The MCP server internally calls the REST API, so quotas count once and a single LicenceKey covers both.

What can the Yatmo MCP server do?

Four read-only tools:

yatmo_get_location_summary — neighbourhood paragraph plus structured nearest school, nursery, supermarket, transport.
yatmo_get_nearby_pois — POIs around a property filtered by category and radius.
yatmo_get_nearest_by_category — single nearest school, nursery, train station, motorway, supermarket, etc.
yatmo_get_accessibility_profile — transit presence, nearest stop, nearest train station, nearest motorway access.

Which countries does the Yatmo MCP server cover?

Belgium, France, the Netherlands, Luxembourg, Germany, Switzerland, Spain, Italy, Portugal, the United Kingdom, Ireland and Austria. Each tool call requires a country argument and your licence must include that country — see Countries & languages.

Do I need a separate licence for the Yatmo MCP server?

No. The Yatmo MCP server reuses your existing Yatmo LicenceKey. The same key works for the REST API and the MCP server, and quotas count against the same daily allowance. See License & keys.

Does the Yatmo MCP server support OAuth?

Not in v1. Authentication is a single LicenceKey HTTP header (the same one used by the REST API). OAuth is on the roadmap for clients that want per-user delegation; for now, treat the LicenceKey as a server-side secret.

Is the Yatmo MCP server read-only?

Yes, by design. There is no create_, update_ or delete_ tool, no SQL, and no free-form query tool. An AI agent connected to Yatmo cannot mutate any data — it can only read neighbourhood intelligence.

What is the difference between school and nursery in the Yatmo MCP server?

school returns actual schools — preschool, primary, secondary and high school — and excludes daycare. nursery returns crèches and daycare only. yatmo_get_location_summary surfaces both as nearestSchool and nearestNursery in the same response.

How are quotas and rate limits counted on the Yatmo MCP server?

Quotas count against the same per-account daily allowance as the REST API summary endpoint. Identical calls hit the upstream 7-day cache plus an additional 1-hour local cache on the MCP server, so repeated queries on the same coordinate consume no extra quota. Exceeding the quota returns 429.

Can I call the Yatmo MCP server from a browser?

No. The LicenceKey grants quota-bearing access to your account and must never be exposed in client-side JavaScript. Use the Yatmo plugins for browser integration (they use a separate frontend key with stricter limits) or proxy the MCP server through your own backend.

Need more? See Quick start, Authentication, or write to info@yatmo.com.