GIS MCP Server
Related Servers
Alternatives to GIS MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA Model Context Protocol server that connects Large Language Models to the GeoServer REST API, enabling AI assistants to query and manipulate geospatial data through natural language.989MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that connects Claude AI to QGIS, enabling direct interaction with the GIS software for project creation, layer manipulation, code execution, and processing algorithms through natural language prompts.1510Creative Commons Zero v1.0 Universal
- FlicenseNot gradedqualityDmaintenanceA geographic ontology layer MCP server that exposes hierarchical relations, topological adjacency, toponym disambiguation, spatial operations, and geo-constraint verification, enabling LLMs to reason with geographic structures instead of raw SQL.-
- AlicenseAqualityDmaintenanceAn MCP server that gives LLMs access to geographic data conversion tools, enabling transformations between different formats like WKT, GeoJSON, CSV, TopoJSON, and KML, as well as performing reverse geocoding.9716MIT
- AlicenseAqualityCmaintenanceAn OpenStreetMap MCP server that provides location-based services including geocoding, route directions, points of interest search, and neighborhood analysis to enhance LLMs with geospatial capabilities.121MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects LLMs with Autodesk Fusion, enabling CAD operations through natural language dialogue.4MIT
TDQS
Scored across 87 tools
Many tools have overlapping functionality (e.g., union vs unary_union_geometries, merge_gpd vs append_gpd, build_transform_and_save_weights vs build_and_transform_weights, getis_ord_g vs getis_ord_g_local, morans_i vs moran_local). Some tools like 'read_file_gpd' vs 'write_file_gpd' are clearly opposite, but the presence of near-duplicates creates ambiguity.
Naming is inconsistent: some tools use verb_noun (e.g., get_centroid, buffer, union), some include '_gpd' suffix (e.g., merge_gpd, sjoin_gpd), some are camelCase (e.g., morans_i, adbscan), and some are longer descriptive phrases (e.g., build_transform_and_save_weights). No clear pattern emerges across the entire set.
With 87 tools, this far exceeds the typical well-scoped count (3-15). Even for a comprehensive GIS server, this is excessive, and many tools are near-duplicates or could be combined, leading to cognitive overload and increased risk of misselection.
The surface covers an extensive range of vector, raster, and spatial statistics operations, including CRUD-like file operations, geometry analysis, raster processing, and spatial autocorrelation. Minor gaps exist (e.g., no explicit raster classification or network analysis), but the domain is well-covered overall.