Skip to main content
Glama

Related Servers

Alternatives to cesium-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Connect QGIS to Claude AI through the Model Context Protocol (MCP), enabling Claude to directly control QGIS — manage layers, edit features, run processing algorithms, render maps, and more.
      100
      1
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables users to search for geographic locations and visualize them on an interactive 3D globe powered by CesiumJS and OpenStreetMap. It provides tools for geocoding addresses and rendering maps with specific bounding boxes through the Model Context Protocol.
      319 npm
      MIT
    • 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants (Claude, Cursor, etc.) to QGIS 4.x via MCP, enabling natural language-driven GIS workflows through 37+ tools, including data loading, processing, and spatial analysis.
      GPL 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that connects AI agents to cloud-native geospatial data via STAC metadata and DuckDB with H3 spatial indexing, enabling zero-configuration SQL queries on terabyte-scale datasets over S3.
      23
      BSD 3-Clause
    • 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

    TDQS

    A3.5/5.0

    Scored across 33 tools

    Disambiguation4/5

    Most tools pair a clear action with a clear object, so camera, layer, entity, and viewpoint operations are generally distinguishable. A few similar tools exist—such as addMarker vs addGeoJsonLayer, or addGeoJsonLayer vs addGeoJsonPrimitive—but their descriptions give enough behavioral difference for an agent to select appropriately.

    Naming Consistency4/5

    The dominant camelCase verb+noun convention is readable and predictable, e.g. addPolygon, removeEntity, listLayers, updateLayerStyle. The clear exceptions are list_toolsets and enable_toolset, which use underscore formatting and break the otherwise fairly uniform naming style.

    Tool Count2/5

    At 33 tools, the surface is heavy and above the range where an agent can quickly discover and select the right tool. The set covers many legitimate Cesium workflows, but several entity and layer operations could be consolidated or grouped to reduce cognitive load.

    Completeness4/5

    The tools cover the main scene workflow: create/manage layers and entities, navigate and save camera state, style, capture, measure, and export scene state. The most obvious gaps are the lack of a scene import counterpart to exportScene, no removeViewpoint operation, and no direct add imagery/3D Tiles tool, but these are workable or minor for common workflows.

    Maintenance

    ActivityActive
    ResponsivenessResponsive