Openstreetmap Mcp Server
Let your coding agent geocode addresses and run OpenStreetMap Overpass queries while you ship location-aware listings, logistics, or map features.
Overview
io.github.cyanheads/openstreetmap-mcp-server is a MCP server for the Build phase that geocodes, reverse-geocodes, and runs Overpass spatial queries on OpenStreetMap data through your agent.
What is this MCP server?
- Forward geocoding and reverse geocoding through Nominatim with a configurable base URL
- Overpass API spatial queries against OpenStreetMap tag and geometry data
- stdio local run plus hosted streamable-http remote at openstreetmap.caseyjhand.com
- Environment knobs for Nominatim, Overpass endpoints, and a policy-compliant OSM_USER_AGENT
- npm package @cyanheads/openstreetmap-mcp-server v0.2.5 with Bun-oriented stdio startup
- Catalog version 0.2.5
- npm identifier @cyanheads/openstreetmap-mcp-server
- Transports: stdio and streamable-http remote
Community signal: 2 GitHub stars.
What problem does it solve?
Agents guess at coordinates or paste brittle curl examples instead of calling Nominatim and Overpass with correct policy and parsing.
Who is it for?
Shipping map search, local directories, or logistics features where the agent must resolve real-world places from OpenStreetMap.
Skip if: Turn-key map tiles, routing engines, or prod scale without respecting OSM rate limits and hosting your own mirrors when traffic grows.
What do I get? / Deliverables
Your agent returns structured OSM-backed locations and query results you can drop into features, tests, or seed data without leaving the IDE.
- Geocoded coordinates and formatted addresses from Nominatim
- Reverse-geocoded place metadata for lat/lon pairs
- Overpass query results for OSM nodes, ways, and relations in agent context
Recommended MCP Servers
Journey fit
Solo builders install this when they are wiring real product features that need coordinates and OSM data, not when they are only brainstorming markets. Integrations is the shelf for Nominatim and Overpass APIs exposed as MCP tools alongside your app backend or agent workflow.
How it compares
OpenStreetMap data MCP integration, not a hosted Maps SDK or turn-by-turn routing product.
Common Questions / FAQ
Who is io.github.cyanheads/openstreetmap-mcp-server for?
Solo builders and small teams who want Claude Code, Cursor, or similar agents to query OSM geocoding and Overpass while building location features.
When should I use io.github.cyanheads/openstreetmap-mcp-server?
Use it during Build when you need geocoding, reverse geocoding, or spatial OSM queries inside agent-driven implementation—not for generic brainstorming without geo data.
How do I add io.github.cyanheads/openstreetmap-mcp-server to my agent?
Install @cyanheads/openstreetmap-mcp-server from npm, run stdio via bun with start:stdio, set OSM_USER_AGENT (and optional Nominatim/Overpass URLs), then register the MCP server in your editor’s MCP config or use the streamable-http remote.