NAVITEL introduces Navitel Geo MCP — an MCP server that opens the company’s geodata to AI agents
24 tools in five groups: addresses and place search, routes and detour optimization, isochrones and coverage analytics, geometry, and a map right in the chat. Connects to Claude, ChatGPT, Open WebUI, Cursor and VS Code over the open Model Context Protocol — with no code written for each geo scenario.
JSC “CNT” (trading as NAVITEL), a Russian developer of navigation software and geoinformation services, announces the launch of Navitel Geo MCP — a server built on the open protocol that gives AI agents and LLM applications standardized access to NAVITEL’s cartographic data, geocoding, routing and geoanalytics.
What Navitel Geo MCP is and why it exists
The Model Context Protocol is an open standard through which language models connect to external data and tools via a single interface. Put simply, it is a common language in which an assistant agrees terms with a service: what can be asked of it, and in what form the answer comes back.
Previously, without such a standard, everything had to be done by hand. For an AI assistant to build a route or find pharmacies, a team had to write a separate connector for each geo scenario, explain to the model where to go and with which parameters, and then monitor changes in the services. One API update later, and the integration had to be rebuilt.
Navitel Geo MCP takes that work on itself: the server describes all 24 of its tools, and the client receives the list automatically. The user asks a question in ordinary words, the assistant picks the right tool, the server calls the NAVITEL Maps API and returns an answer suitable for the model — the result, the request spend and, if the user asked for it, a map right in the chat. The model needs no knowledge of how the API is structured and no handling of coordinates.
The service closes the gap between what modern models can do and live geodata: a logistics agent, a trip-planning assistant or an internal corporate tool gets structured access to NAVITEL’s geospatial information without having to “invent” the integration from scratch.
Key capabilities
The server covers the full cycle of working with geodata — from validating an address to a finished map. All capabilities are gathered into five groups.
Addresses and place search. Converting an address to coordinates and back — from coordinates to a readable address. Text search for objects around a reference point and batch processing of up to 200 addresses with a separate verdict on each. Validation of address databases with spelling correction, plus searching for objects along an existing route with a permitted detour limit — by time or by distance.
Routes and optimization. Multi-stop routes — on foot, by bicycle, by car and by truck — accounting for traffic, departure time, with segment breakdown and a list of roads. This group also covers choosing the best visiting order, planning a tour within a time budget, a distance and travel-time matrix, and comparing the reachability of several options. Separate tools help pick the nearest depot or station for an incident and allocate orders across vehicles with capacity constraints.
Service areas and coverage analytics. The territory reachable within given time intervals — including in reverse: “who can get to you in time.” Checking whether points fall within a zone, finding coverage gaps with the share of uncovered territory and the geometry of each gap, filtering locations by several conditions, and selecting a site for a new facility based on weighted demand points with competitors taken into account.
Geometry. Polygon area in square meters, hectares or square kilometers, and compass bearing between points are computed on the server — instantly and without consuming the daily request limit.
Map in the response. A raster map with markers, route lines and zones. The resulting geometry can be reused by link for a limited period instead of being recalculated. In a conversation the map arrives as an image, as a temporary link — for emails and presentations — or as an embedded window: the format depends on the client.
How the service works
How the service works. If a request cannot be fulfilled — insufficient resources, not enough data, or an unavailable link — the service names a clear reason instead of giving an approximate answer. When some sources did not respond, the answer is explicitly marked as partial: missing numbers are not invented.
Request economy. Local geometric computations and reuse of geometry by link reduce calls to external services. Every response states the actual number of requests sent.
A single entry point. The whole cycle — from address validation to a finished map — is covered by one connection, with no separate integrations per scenario.
Read-only. The tools do not create or modify data and do not manage vehicles. Before the first call, the client requests the user’s permission.
Nothing to install on the client side. The service runs as a cloud server over Streamable HTTP on top of HTTPS. MCP clients with custom headers are supported; clients supporting only SSE or stdio are not.
Who it is for and how to start
Navitel Geo MCP is aimed at developers of AI applications and product teams working with geodata: in logistics and delivery, emergency and field services, retail and real estate development, tourism, municipal services and corporate analytics. The server helps bring geo features to market faster and lowers integration costs — the team focuses on product logic rather than on the infrastructure for accessing maps.
The service is open for testing and pilot projects: the trial period runs on the same key and daily limit as the NAVITEL Maps API. Access is arranged through the partner form, documentation, tool descriptions and connection instructions are published at site.
The company invites AI developers, integrators and product teams to collaborate.
