Skip to main content
Glama
Sowjanyakaki

osm-mcp-server

by Sowjanyakaki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to osm-mcp-server

No user-submitted related servers found.

    Related Servers

    • geo-mcp

      FaresKi
      F
      license
      A
      quality
      C
      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
      -

    • osm-mcp

      abangbroy
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that provides live geospatial data such as geocoding, POI search, isochrones, and area density from open data sources to LLM clients like Claude, Cursor, or Claude Code.
      6
      MIT

    • OpenStreetMap MCP Server

      GRABOSM
      A
      license
      B
      quality
      D
      maintenance
      A comprehensive MCP server providing 30 tools for geocoding, routing, and OpenStreetMap data analysis. It enables AI assistants to search for locations, calculate travel routes, and perform quality assurance checks on map data.
      30
      251 npm
      5
      MIT

    • Geo MCP Worker

      Kerry1020
      A
      license
      Not graded
      quality
      C
      maintenance
      Free geospatial MCP server for AI agents, providing geocoding, reverse geocoding, POI search, and route planning using OpenStreetMap data via Nominatim, Overpass, and OSRM.
      1
      GPL 3.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.9/5.0

    Scored across 12 tools

    Disambiguation2/5

    Several tools have overlapping purposes: find_nearby_places, explore_area, and analyze_neighborhood all take coordinates and radius to return information about an area, differing mainly in aggregation style. search_category also overlaps with find_nearby_places. While descriptions add some detail, an agent could easily select the wrong tool for a generic nearby-places query.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (e.g., find_parking_facilities, analyze_neighborhood, geocode_address). Names are lowercase with underscores and verbs are descriptive. Minor deviations like reverse_geocode and get_route_directions are still within the same convention, making the set predictable.

    Tool Count5/5

    Twelve tools is well within the ideal 3–15 range. Each tool serves a distinct geospatial need, and the specialized find_* tools add focus without bloating the surface.

    Completeness4/5

    The set covers forward/reverse geocoding, place discovery, routing, commute analysis, and several specialized POI searches, covering the core geospatial workflows. Missing a specific 'place details by ID' tool is a minor gap, but agents can work around it with geocode_address or find_nearby_places.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources