Skip to main content
Glama
algolayertechnologies

mapsi-mcp

by algolayertechnologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to mapsi-mcp

No user-submitted related servers found.

    Related Servers

    • Magic Lane MCP Server by magiclane

      Magic Lane MCP Serverofficial

      magiclane
      A
      license
      B
      quality
      B
      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
      16 npm
      7
      Apache 2.0

    • 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

    • 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

    • 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.3/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: autocomplete for UI, geocode for forward, reverse_geocode for reverse, batch variants for bulk, elevation, static/tile URLs, H3 indexing, isochrone, map matching, matrix, nearest road, normalization, places search, point-in-polygon, routing, and timezone. Even geocode and normalize_address differ in goal (coordinates vs. data quality). No overlap.

    Naming Consistency4/5

    Most tools follow verb_noun or noun patterns (e.g., batch_geocode, get_static_map_url, reverse_geocode, timezone). A few are single words (elevation, route, matrix), which is acceptable. No mixing of camelCase or snake_case (all lower_snake). Minor inconsistency but still predictable.

    Tool Count4/5

    18 tools is slightly above the typical 3-15 range but justified by the broad geospatial domain. Each tool covers a distinct operation (forward/reverse/bulk geocoding, routing, matrix, isochrone, map matching, etc.). No redundant or trivial tools.

    Completeness5/5

    The tool set covers the full lifecycle of geospatial operations: geocoding (forward, reverse, batch), routing (with multiple travel modes), matrix calculations, isochrones, map matching, place search, elevation, H3 indexing, point-in-polygon, timezone, tile/static map generation, and address normalization. No obvious gaps; it handles both common and advanced use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources