overpass-mcp
Allows running Overpass QL queries against the OpenStreetMap Overpass API to retrieve OpenStreetMap data, with configurable endpoint and request timeout.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@overpass-mcpfind cafes within 300 meters of Trafalgar Square"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
overpass-mcp
An MCP server that lets an agent run Overpass QL queries against the OpenStreetMap Overpass API.
Install
npm installRelated MCP server: mcp-overpass
Run
npm startIt speaks MCP over stdio.
Configure (opencode)
{
"mcp": {
"overpass": {
"type": "local",
"command": ["node", "/absolute/path/to/overpass-mcp/index.js"]
}
}
}Tool: overpass_query
Runs an Overpass QL query and returns the raw response.
argument | required | description |
| yes | Overpass QL, e.g. |
| no | Overpass API endpoint (default |
| no | request timeout in ms (default 60000) |
Responses are truncated at 200 kB to protect the model's context; narrow the query if you see a truncation notice.
Test
npm test # offline unit tests (retry + truncation), CI-safe
npm run test:live # one live query against a public endpointtest never touches the network. test:live does, and can fail when a public
instance is busy.
Notes
A User-Agent header is sent because the public Overpass endpoint rejects requests from unknown clients (notably Node's default
undiciUA) with HTTP 406.The public instances intermittently shed load with HTTP 429/503/504. The client retries those twice with a short backoff before giving up.
Public Overpass instances are rate limited. For heavy use, point
endpointat your own instance.
Disclaimer
The default endpoints are free, community-run public services. They are not yours and they are not guaranteed.
Respect the servers. Space out queries, cache results, and avoid heavy or automated bulk querying. Do not hammer the endpoint.
Allow time. Queries may be slow, rate limited, or intermittently return HTTP 429/503/504. The client retries a little, but patience is expected.
Follow the rules. You are responsible for complying with the usage policies and terms of whichever endpoint you use, and with the OpenStreetMap licence (data © OpenStreetMap contributors, ODbL).
No warranty, no liability. This software is provided "as is", without warranty of any kind. The author is not responsible for any use, misuse, rate limiting, blocks, data loss, or damages arising from it.
If you need volume or reliability, run your own Overpass instance and point
endpoint at it.
License
MIT. Use, modify, and distribute freely; keep the copyright and license notice.
This server cannot be deployed
Maintenance
Related MCP Connectors
Geocode, reverse geocode, and run Overpass spatial queries on OpenStreetMap data.
Geocode, reverse geocode, and run Overpass spatial queries on OpenStreetMap data.
Gateway between LLM agents and world data through eight tools and a bundled endpoint catalog.
OpenStreetMap Overpass MCP — programmatic queries against the OSM database
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables querying OpenStreetMap data (buildings, roads, amenities, etc.) via Overpass API and converts them to GeoJSON format for GIS analysis and visualization.86MIT
- AlicenseNot gradedqualityBmaintenanceEnables programmatic queries against the OpenStreetMap database using the Overpass API.15 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query TomTom Search and Routing APIs, including geocoding, places, and route planning.10 npmMIT
- AlicenseAqualityDmaintenanceQuery Overture Maps data — places (POIs), buildings, and administrative divisions — from MCP-compatible LLMs with token-efficient summaries.58 npmMIT