mcp · Global

open-streetmap-mcp

An OpenStreetMap MCP server implementation that enhances LLM capabilities with location-based services and geospatial data.

Claim this listing

Represent open-streetmap-mcp? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Data offered docs-verified: geocoding: address or place name to coordinates · reverse geocoding: coordinates to human-readable address · nearby points of interest · turn-by-turn route directions between locations · places by category within a bounding box · optimal meeting point for multiple people · area exploration summary (comprehensive location information) · schools and educational institutions near a location · commute option comparison (home to work) · EV charging stations with connector and power filtering · neighbourhood livability analysis for real estate · parking facilities with availability and fee information · styled map tiles (location://map resource)
Coverage llm-inferred: Global (per catalogue regions metadata; docs do not state a geographic extent)
Formats docs-verified: MCP stdio
Access llm-inferred: Public use via uvx per README; no credentials documented; MIT licence (catalogue metadata)

Use cases llm-inferred: Geocode a site address to coordinates and map its location context for a site appraisal or FRA report · List schools, parking and EV charging near a development site for a site logistics or planning-context note · Compare commute and route options for site staff or sub-consultant travel to a project location · Gather neighbourhood livability and amenity context as a desk-study baseline before a site visit
Audience llm-inferred: GIS analysts · planners · civils engineers (site logistics and access)

Constraints llm-inferred: No UK-specific coverage, data provenance or update cadence documented; catalogue lists region as Global · No time span, spatial resolution or data currency documented · Debugging is harder because the server runs over stdio · README client example uses an HTTP URL (http://localhost:8000) while the server is described as stdio, so transport setup needs checking · No rate limits or upstream OSM service terms documented · Parking, EV charging and school results depend on how features are tagged in OpenStreetMap, so completeness will vary · Tool input parameters beyond geocode_address are not documented

Tools/install/auth auto-extracted from README; quality score heuristic (stars, recency, tool count, licence).

Metadata observed 15/10/2026 · research sweep: github-search