Skip to main content
Glama
shimizu

OSM-GeoJSON-MCP-Server

by shimizu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to OSM-GeoJSON-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

    • overpass-mcp

      RigaOnTheRocks
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an agent to run Overpass QL queries against the OpenStreetMap Overpass API and get raw responses back. It handles configurable endpoints and timeouts, retries transient rate-limit and server errors, and truncates oversized responses to protect the model's context.
      50 npm
      MIT

    • Maps MCP App

      russianryebread
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables users to search for locations, businesses, and points of interest on an interactive OpenStreetMap map within ChatGPT conversations.
      -
    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.8/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct OSM feature type (amenities, buildings, green spaces, railways, roads, waterways) or server functionality (stats, connection test), with no overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent 'get_' prefix followed by a noun (e.g., get_amenities, get_buildings), making the pattern predictable.

    Tool Count5/5

    With 8 tools, the server covers the major OSM feature categories plus utility functions, well-scoped for its purpose without being excessive or insufficient.

    Completeness4/5

    The tool set covers common geographic features but lacks freeform querying (e.g., by tags) or less common layers like land use or administrative boundaries, leaving minor gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources