OpenStreetMap MCP Server

uvx osm-mcp-server

{
  "mcpServers": {
    "openstreetmap-mcp": {
      "command": "uvx",
      "args": [
        "osm-mcp-server"
      ]
    }
  }
}

The interesting part is not the geocoder but the shape of the tool list. Alongside the primitives — geocode, reverse geocode, nearby places, directions, category search — sit tools that answer a whole question at once: suggest_meeting_point takes several people's locations and proposes where to meet, analyze_commute compares transport options between a home and a work address, and analyze_neighborhood scores an area for liveability. Chaining raw calls to reach those answers is exactly where models drift, so folding the chain into one tool removes a class of mistakes. There are also narrow lookups for schools, EV charging points and parking, plus map tiles and place data exposed as MCP resources. No API key is involved.