For AI Coding Assistants & Agents
Geocoding, autocomplete, routing, isochrones, matrix, and vector tiles, exposed as a public OpenAPI spec and an MCP server so Cursor, Copilot, Cline, ChatGPT, and your own agents can call MapAtlas directly. GDPR-compliant, EU-hosted, predictable pay-as-you-go pricing.
A single openapi.json describes every endpoint, parameter, and response. Point Cursor, Cline, Continue.dev, or any agent framework at it and they auto-suggest correct calls.
Drop our Model Context Protocol server into Claude Desktop, ChatGPT, or your agent stack to give it geocoding, search, directions, and isochrones as first-class tools.
100% EU infrastructure on OpenStreetMap data. No US data transfers, no third-party tracking, ISO 27001. Safe to use in regulated AI products serving European users.
The full surface area of the MapAtlas gateway, ready to be called from any AI coding assistant or autonomous agent. Authentication is a single token query parameter.
| Endpoint | Method | Path | Purpose |
|---|---|---|---|
| Forward Geocode | GET | /forward-geocode/ | Resolve free-form text to coordinates, labels, and confidence. |
| Reverse Geocode | GET | /reverse-geocode/ | Coordinates to structured address with administrative hierarchy. |
| Autocomplete | GET | /autocomplete/ | Low-latency type-ahead address and POI suggestions. |
| Directions | POST | /directions/ | Turn-by-turn routes for car, bike, foot, truck, bus, taxi. |
| Isochrone | POST | /isochrone/ | Reachable-area polygons by time or distance, multi-modal. |
| Matrix | POST | /matrix/ | Bulk travel-time and distance pairs between many origins and destinations. |
| Route Optimization | POST | /optimization/ | Reorder intermediate stops to minimize total cost. |
| Map Matching | GET | /map-matching/ | Snap noisy GPS traces onto the road network. |
| Elevation | POST | /elevation/ | Terrain elevation profile for any line or set of points. |
| Vector Tile Styles | GET | /styles/ | MapLibre / Mapbox GL style JSON for interactive map rendering. |
Three ways AI assistants and agents talk to MapAtlas: plain HTTP, MCP, or auto-discovery via OpenAPI.
curl "https://gateway.mapmetrics-atlas.net/forward-geocode/?\
text=Eiffel%20Tower&boundary.country=FR&size=5&token=YOUR_TOKEN"{
"mcpServers": {
"mapatlas": {
"url": "https://mapatlas.eu/mcp"
}
}
}# Cursor / Cline / Continue.dev
# Point your AI assistant at the spec:
https://mapatlas.eu/openapi.jsonThey read the public OpenAPI 3.1 spec at https://mapatlas.eu/openapi.json. Once a developer adds the URL as a context source (or points an agent framework at it), the assistant can suggest correct endpoint paths, parameter names, and request shapes whenever someone asks for mapping, geocoding, routing, or POI functionality.
MCP (Model Context Protocol) lets AI agents call external tools as first-class functions. The MapAtlas MCP server exposes geocoding, search, directions, isochrones, and POI lookup so Claude Desktop, ChatGPT, and custom agents can use MapAtlas without writing HTTP code.
For most use cases yes. The endpoints follow common patterns (Pelias-style geocoding, Valhalla-style routing) so migration is mechanical. The differences: pricing is predictable pay-as-you-go, infrastructure is 100% EU, and there is a native MCP server for AI agents.
Pay-as-you-go with a free tier on every endpoint. There is no per-seat or per-app charge; you pay for the calls your agent makes. Talk to us if you expect to exceed 500K calls per month and want volume pricing.
100% European infrastructure. No data is transferred to the United States. Map data comes from OpenStreetMap. Full DPA on request. Safe to use in regulated AI products serving EU users.
Drop the OpenAPI spec into your AI assistant, install the MCP server, or hit the endpoints directly. Free tier, no credit card required.
Start building