Skip to main content
Glama
Sign In
OpenStreetMap MCP Server v2

OpenStreetMap MCP Server v2

by ogSINGH
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to OpenStreetMap MCP Server v2

No user-submitted related servers found.

    Related Servers

    • geo-mcp

      FaresKi
      F
      license
      A
      quality
      D
      maintenance
      OSM-backed multimodal navigation MCP server enabling geocoding, route planning, POI discovery, and urban layout analysis. It provides a structured city graph to LLM apps without proprietary map APIs.
      8
      -

    • maps-mcp

      shivam221098
      A
      license
      A
      quality
      C
      maintenance
      Gives AI assistants map capabilities — geocoding, places search, routing, distance matrices, isochrones and static maps — from Google Maps Platform, OpenStreetMap, open-source routing engines and open geocoders behind one provider-agnostic tool surface. Early development: both stdio and streamable HTTP transports run and a ping tool is exposed, but provider adapters are not yet implemented.
      1
      MIT
    • Magic Lane MCP Server

      Magic Lane MCP Serverofficial

      magiclane
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to become geospatially intelligent assistants with tools for location search, smart routing, round trip planning, reverse geocoding, isochrone analysis, route visualization, geofence management, and interactive map display.
      8
      17 npm
      8
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 12 tools

    Disambiguation3/5

    Several tools overlap substantially: explore_area, find_nearby_places, analyze_neighborhood, and search_category all return categorized POIs in an area, and find_schools_nearby, find_ev_charging_stations, and find_parking_facilities are essentially specialized subsets that find_nearby_places could handle. The descriptions help distinguish analysis-oriented tools (analyze_neighborhood, explore_area) from search-oriented ones, but an agent could still easily misselect among the area-search family.

    Naming Consistency5/5

    Every tool follows a clean verb_noun pattern (explore_area, reverse_geocode, geocode_address, find_nearby_places, get_route_directions, search_category, suggest_meeting_point, analyze_commute, etc.). Verbs are consistent (find_/get_/analyze_/search_) and naming is fully snake_case with no deviations.

    Tool Count4/5

    12 tools is a reasonable, well-scoped size for an OSM geospatial server covering geocoding, routing, search, and analysis. It's slightly heavy given the redundant specialized search tools, but nothing feels padded to the point of being unmanageable.

    Completeness4/5

    Core geospatial workflows are well covered: both geocoding directions, routing, POI/category search, area and neighborhood analysis, and specialized searches. Minor gaps exist (e.g., isochrones, elevation, map/static image generation, or boundary/administrative lookups), but agents can accomplish most realistic tasks.

    Resources