2GIS MapGL MCP server
2GIS MCP (mapgl-mcp-server)
2GIS's official MCP server on top of the MapGL JS API: place search, geocoding, routes and isochrones, works with a demo key out of the box
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- Only reads maps, places and routes, does not change anything in external systems
- Each request spends the API key's quota
Install
Manual install
git clone https://github.com/2gis/2gis-mcp.git && cd 2gis-mcp && npm install && npm run buildThe package is not published on npm; build it from source per the repository's package.json.
This is third-party code. Review the repository files before installing.
What it does
The server gives the agent six tools built on 2GIS's MapGL JS API: search_poi finds businesses and places near a point within a radius, calculate_route builds a route between points that can be given as coordinates or a text address, geocode and reverse_geocode convert addresses to coordinates and back, create_map_view builds map view parameters, and calculate_isochrone computes a reachability zone. The MAPGL_API_KEY defaults to demo, so basic requests work without registering your own, while a separate ROUTING_API_KEY is needed for routes.
Who it is for. For developers and analysts who need 2GIS maps, place search and routing for Russian and CIS cities right inside an agent.
Good fit when
- You need to find businesses of a certain type near a map point
- You need a route between addresses or coordinates
- You want to quickly try the MapGL API without registering your own key
Not a fit when
- You need routes in production: the demo MAPGL_API_KEY is not meant for sustained load
- The project is not published on npm, you will need to build it from source yourself
Example request
Find coffee shops within 500 meters of Red Square and build a walking route to the nearest oneLimitations
The package is not published on npm; install by cloning the repository and building it with npm run build. The project's README does not describe the tools and environment variables, they are only visible in the source. The demo MAPGL_API_KEY is limited and not meant for sustained use, and routes additionally need a ROUTING_API_KEY. The project has no releases or stars yet, but it belongs to the official 2GIS organization.
How to disable. Remove the server block from your MCP client config and stop the node process.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| MAPGL_API_KEY secret | The MapGL API key, defaults to demo for initial requests. |
| ROUTING_API_KEY secret | A separate key for routes and isochrones. |
Security check
- Only reads maps, places and routes, does not change anything in external systems
- Each request spends the API key's quota
README in short
The repository README is a single paragraph: name, purpose and a link to the docs.2gis.com/api/ai/mcp-server documentation. The full list of six tools, their parameter schemas and the MAPGL_API_KEY and ROUTING_API_KEY environment variables are only visible in the src/index.ts and src/mapgl-client.ts source. MIT license, with an English and a Russian license file.
FAQ
Do I need my own key to start?
No, MAPGL_API_KEY defaults to demo and works for initial search and geocoding requests.
Why don't routes work?
calculate_route and isochrones need a separate ROUTING_API_KEY; the demo map key does not cover it.
Related
166 skills for scientific work: bioinformatics, cheminformatics, clinical data, geospatial analysis and 100+ databases
Google's open-source MCP server for databases: ready tools for Postgres, MySQL, BigQuery, Spanner and more, plus custom tools in tools.yaml
Official Hugging Face skills: Hub operations via the hf CLI, datasets, model training, Spaces, evals and deployment
A visualization language for agents and an MCP server: neat charts from a simple semantic spec