Skip to main content
Glama
LLLeoLi

osm-mcp-server

by LLLeoLi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to osm-mcp-server

No user-submitted related servers found.

    Related Servers

    • OpenStreetMap MCP Server v2

      ogSINGH
      A
      license
      A
      quality
      C
      maintenance
      Enables LLMs to geocode and reverse geocode places, find nearby points of interest, search categories within an area, get turn-by-turn routing, suggest meeting points, and analyze neighborhoods, commutes, schools, EV charging, and parking through OpenStreetMap data services. It also serves place and map tile resources over stdio, SSE, or Streamable HTTP transports.
      12
      MIT

    • OSM Edit MCP Server

      skywinder
      A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to search, validate, and edit OpenStreetMap data through natural language commands and built-in safety protections. It supports discovery of nearby amenities, geographic data exploration, and secure map editing via OAuth authentication.
      31
      4
      MIT

    • chuk-mcp-geocoder

      fastmcp-me
      A
      license
      A
      quality
      D
      maintenance
      Provides forward/reverse geocoding, bounding box extraction, nearby places discovery, batch geocoding, route waypoints, and administrative boundary lookup using OpenStreetMap data.
      10
      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

    A4.1/5.0

    Scored across 12 tools

    Disambiguation2/5

    Several tools perform similar place searches (find_nearby_places, search_category, explore_area, analyze_neighborhood) with only subtle differences in scope and output. The specialized find_* tools overlap with generic search capabilities, making misselection likely.

    Naming Consistency5/5

    All tool names follow a consistent lowercase verb_noun pattern (reverse_geocode, find_nearby_places, analyze_neighborhood, etc.). The naming convention is uniform and predictable.

    Tool Count5/5

    The server contains 12 tools, which is well within the ideal 3-15 range. Each tool serves a distinct geospatial use case, and the count feels appropriate for the domain.

    Completeness4/5

    The tool set covers geocoding, reverse geocoding, place search, routing, and neighborhood analysis. Minor gaps exist, such as missing direct OSM object detail lookup, but the core functionality is well represented.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources