mcp · Global

osm-mcp

Model Context Protocol server for OpenStreetMap data

Claim this listing

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

Data offered docs-verified: OpenStreetMap data queried via SQL against PostgreSQL/PostGIS
Coverage llm-inferred: Global per ENTRY regions metadata; actual coverage depends on the OSM extract loaded into the database
Formats llm-inferred: MCP stdio
Access llm-inferred: Local install; requires a PostgreSQL/PostGIS database reached via PG* connection settings; no API key or OAuth documented; licence not stated

Use cases llm-inferred: Extract OSM roads, watercourses and buildings within a site boundary for early constraints screening · Plot site boundaries, drainage outfalls or survey points as markers and polygons on a map for client briefings · Check OSM-mapped features around a development footprint during desk-based environmental or civils review
Audience llm-inferred: GIS analysts · civils engineers · drainage engineers · environmental consultants · planners

Constraints llm-inferred: Needs a running PostgreSQL/PostGIS database already populated with OSM data; how to load it is not documented · Docs list default PG credentials (postgres/postgres), which conflicts with ENTRY auth saying no credentials are documented · Map viewer web server runs on localhost:8889 by default and is only local unless FLASK_HOST is changed · No licence stated in ENTRY or docs; no version or maintenance status shown · Tool parameter schemas are not documented beyond tool names and short descriptions

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

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