Enterprise DNA
M MCP Servers Developer low

jagan-shanmugam/open-streetmap-mcp

by Various

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

J

MCP

jagan-shanmugam/open-streetmap-mcp

Added 1 June 2026

#anthropic-claude #llm #mcp #mcp-server #openstreetmap

Overview

An MCP server that gives LLMs access to OpenStreetMap data for location-based queries and geospatial operations. It exposes endpoints for geocoding, reverse geocoding, and map data retrieval through the Model Context Protocol.

Best for

Best for
Developers building location-aware LLM applications or assistants that need geospatial context

Use cases

  • Look up coordinates or addresses from place names
  • Retrieve map features and points of interest for a given area
  • Integrate geospatial context into LLM-driven applications

Notes

An MCP server that gives LLMs access to OpenStreetMap data for location-based queries and geospatial operations. It exposes endpoints for geocoding, reverse geocoding, and map data retrieval through the Model Context Protocol.

196 stars on GitHub. Last updated 2025-07-12. Licensed MIT.

Use cases

  • Look up coordinates or addresses from place names
  • Retrieve map features and points of interest for a given area
  • Integrate geospatial context into LLM-driven applications

Pros

  • Connects LLMs to real-world geographic data without custom API code
  • Leverages the extensive and free OpenStreetMap dataset
  • Simple MCP interface works with any compatible LLM host

Cons

  • Depends on OpenStreetMap’s availability and rate limits
  • Limited to data that exists in OpenStreetMap (may lack local detail)
  • Requires running or hosting the MCP server separately

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Connects LLMs to real-world geographic data without custom API code
  • Leverages the extensive and free OpenStreetMap dataset
  • Simple MCP interface works with any compatible LLM host

Cons

  • Depends on OpenStreetMap's availability and rate limits
  • Limited to data that exists in OpenStreetMap (may lack local detail)
  • Requires running or hosting the MCP server separately