myosm-mcp-server
Provides geocoding, reverse geocoding, place search, nearby POIs, routing, map tiles, public transport, and energy infrastructure data using OpenStreetMap services.
Click on "Install 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., "@myosm-mcp-serverSuggest a central meeting point for 3 people in Berlin."
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.
myosm-mcp-server — OpenStreetMap MCP Server (Node.js)
An OpenStreetMap MCP server that enhances LLM capabilities with location-based services and geospatial data.
This is a Node.js/TypeScript reimplementation of jagan-shanmugam/open-streetmap-mcp (Python), extended with map-layer, public-transport and energy-infrastructure tools.
Features
The server gives LLMs tools to interact with OpenStreetMap data:
Geocode addresses and place names to coordinates (and the reverse)
Find nearby points of interest
Get route directions and commute analysis between locations (OSRM)
Search for places by category within a bounding box
Suggest optimal meeting points for multiple people
Explore areas and run neighborhood livability analysis
Find schools, EV charging stations and parking facilities
Map layers: fetch rendered map tiles (standard, transport, cycle, …) as images
Public transport layer: stops, stations and transit route lines (bus, tram, train, subway, light rail, ferry)
Energy layer: power lines, underground cables, substations and transformers (with voltage filtering), plus electricity production facilities (power plants and generators, filterable by source and output)
Related MCP server: OpenStreetMap MCP Server
Installation
Requires Node.js ≥ 18.17.
git clone https://github.com/visuelconcept/myosm-mcp-server.git
cd myosm-mcp-server
npm install
npm run buildRunning the server
The server supports both MCP transports; stdio is the default.
stdio (local MCP hosts: Claude Desktop, Claude Code, Cursor, Windsurf, …)
{
"mcpServers": {
"myosm-mcp-server": {
"command": "node",
"args": ["/path/to/myosm-mcp-server/dist/index.js"]
}
}
}With Claude Code:
claude mcp add myosm -- node /path/to/myosm-mcp-server/dist/index.jsClaude Desktop config file locations:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%/Claude/claude_desktop_config.json
Streamable HTTP (remote deployments, shared server, multiple clients)
Start the server in HTTP mode:
node dist/index.js --http --port 3000 # or: npm run start:http
# equivalent: MCP_TRANSPORT=http PORT=3000 node dist/index.jsThe MCP endpoint is http://127.0.0.1:3000/mcp (sessions are managed per client
via the Mcp-Session-Id header) and GET /health reports liveness for
deployment probes.
Declare it in an MCP host by URL:
{
"mcpServers": {
"myosm-mcp-server": {
"type": "http",
"url": "http://127.0.0.1:3000/mcp"
}
}
}With Claude Code:
claude mcp add --transport http myosm http://127.0.0.1:3000/mcpCLI options: --http, --stdio, --host <address>, --port <number>, --help.
Security: the HTTP server binds to
127.0.0.1by default and has no built-in authentication. To expose it (--host 0.0.0.0), put it behind a reverse proxy that handles TLS and auth, and setMCP_ALLOWED_HOSTS(comma-separatedHostheader values, e.g.MCP_ALLOWED_HOSTS=mcp.example.com) to enable DNS-rebinding protection.
Tools
Geocoding
Tool | Description |
| Convert an address or place name to coordinates with rich metadata |
| Convert coordinates to a detailed address |
Places & analysis
Tool | Description |
| Discover POIs near a location, grouped by category/subcategory |
| Find places of given categories/subcategories in a bounding box |
| Compute a central meeting point and suggest venues around it |
| Comprehensive profile of all features in an area |
| Livability analysis with category scores and walkability |
| Educational institutions around a point, sorted by distance |
| EV charging stations with connector/power filtering |
| Parking facilities with type, capacity and fee info |
Routing
Tool | Description |
| Route between two points (car/bike/foot) with turn-by-turn directions |
| Compare home→work commute across several transport modes |
Map layers & transport
Tool | Description |
| Rendered map tile (PNG image) covering a location — styles: |
| Public transport layer: stops/stations/terminals plus transit route lines ( |
Energy
Tool | Description |
| Electricity grid: power lines, underground cables, substations, transformers (and on request towers, poles, switches, …) with voltage parsing, |
| Production facilities: |
Resources
location://place/{query}— information about a place by name (JSON)location://map/{style}/{z}/{x}/{y}— styled map tile at tile coordinates (PNG)
Configuration
All configuration is optional and done through environment variables:
Variable | Default | Purpose |
|
|
|
|
| HTTP bind address |
|
| HTTP port |
| — | Comma-separated |
|
| Geocoding endpoint (self-hosted Nominatim) |
|
| Overpass API endpoint |
|
| Routing endpoint (self-hosted OSRM) |
|
| Tile server for the |
| — | Required for the |
|
| User-Agent sent to the OSM services |
Behind a corporate proxy, run Node with NODE_USE_ENV_PROXY=1 (Node ≥ 22.15) so fetch honors HTTPS_PROXY.
Fair use: by default the server talks to free, community-run services. Respect the Nominatim usage policy (max 1 req/s), the Overpass fair-use policy and the OSRM demo server policy. For production workloads, point the environment variables at your own instances. Note: the public OSRM demo server routes every profile with car data; self-host OSRM to get real bike/foot routing (the server already maps modes to the canonical
driving/cycling/walkingprofiles).
Development
npm run build # compile TypeScript to dist/
npm run watch # recompile on change
npm test # smoke + integration + HTTP transport tests (all offline)
SMOKE_LIVE=1 npm run smoke # additionally exercise the real public OSM APIs
npm run inspector # debug with the MCP InspectorThe integration and HTTP tests (test/integration.mjs, test/http.mjs) run the
server against local mock implementations of Nominatim, OSRM, Overpass and the
tile server, so they work without network access.
Differences from the Python original
Same 12 tools and 2 resources, plus:
4 new tools:
get_map_tile,find_public_transport,find_power_infrastructure,find_power_plantsStreamable HTTP transport (
--http) in addition to stdio, with per-client sessions and a/healthendpointOverpass queries use
out center, so ways/relations (building-mapped schools, parking lots, …) return usable coordinates instead of being droppedsearch_categorysubcategory filtering uses a valid Overpass regex filter (the original generated invalid QL)Transport modes are mapped to canonical OSRM profiles (
driving/cycling/walking)Endpoints are configurable via environment variables
Turn-by-turn instructions are synthesized from OSRM maneuvers (
"turn left onto …")
License
MIT — see LICENSE. Original Python implementation © open-streetmap-mcp contributors.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityDmaintenanceAn MCP server that gives LLMs access to geographic data conversion tools, enabling transformations between different formats like WKT, GeoJSON, CSV, TopoJSON, and KML, as well as performing reverse geocoding.91416MIT
- AlicenseBqualityDmaintenanceA comprehensive MCP server providing 30 tools for geocoding, routing, and OpenStreetMap data analysis. It enables AI assistants to search for locations, calculate travel routes, and perform quality assurance checks on map data.303MIT
- Alicense-qualityBmaintenanceFree geospatial MCP server for AI agents, providing geocoding, reverse geocoding, POI search, and route planning using OpenStreetMap data via Nominatim, Overpass, and OSRM.1GPL 3.0
Related MCP Connectors
MCP server providing access to the Scorecard API to evaluate and optimize LLM systems.
Hosted MCP server for LLM cost estimation, model comparison, and budget-aware routing.
Hosted MCP with 91 agent tools: X, domains, SEO, Maps, Trends, Search, YouTube, TikTok, and more.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/visuelconcept/myosm-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server