Skip to main content
Glama
NodeGIS

GeoSpatial MCP Server

by NodeGIS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to GeoSpatial MCP Server

No user-submitted related servers found.

    Related Servers

    • LocuSync Server

      matbel91765
      A
      license
      Not graded
      quality
      D
      maintenance
      A geospatial MCP server that provides tools for geocoding, routing, elevation profiles, and spatial analysis. It enables AI agents to process GIS file formats like GeoJSON and Shapefiles while performing complex coordinate transformations and distance calculations.
      4
      MIT

    • GIS MCP Server

      mahdin75
      A
      license
      C
      quality
      A
      maintenance
      A Model Context Protocol server that connects LLMs to GIS operations, enabling AI assistants to perform accurate geospatial analysis including geometric operations, coordinate transformations, and spatial measurements.
      87
      193
      MIT

    • GIS MCP Server

      briannag1692
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to perform geospatial analysis, spatial data processing, vector and raster operations, coordinate transformations, spatial statistics, mapping, and access to climate, satellite, and other geospatial data through MCP-compatible clients.
      MIT
    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.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: calculate_area for polygon area, calculate_distance for polyline distance, and convert for coordinate system conversion. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency5/5

    All tool names follow a consistent pattern: mcp_geo_ followed by a verb (calculate or convert) and a noun (area, distance, or no noun for convert). This predictability enhances usability and reduces confusion.

    Tool Count3/5

    With only 3 tools, the server feels thin for a geospatial domain, which typically involves more operations like buffering, intersection, or spatial queries. While the tools cover basic calculations and conversion, the scope is limited, potentially requiring agents to work around missing functionality.

    Completeness2/5

    The tool set is severely incomplete for geospatial operations. It lacks essential CRUD or lifecycle coverage, such as creating or querying spatial data, performing spatial joins, or handling more complex analyses like buffering or overlay operations. This will likely cause agent failures in broader geospatial tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources