Skip to main content
Glama

Related Servers

Alternatives to cesium-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      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.
      1,159 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
      D
      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
      B
      maintenance
      Connects QGIS to any MCP-speaking AI agent, exposing 125 tools that let the agent manage layers, edit features, run processing algorithms, render and style maps, author layouts and atlases, query across layers with SQL, and administer the QGIS session. Works with any MCP client and QGIS 3.28–4.x.
      GPL 2.0

    TDQS

    C2.9/5.0

    Scored across 41 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions: camera, layers, entities, resources, basemap, measurement, and meta-toolsets are separated well. There is some overlap around map connection (openCesiumMap vs connectCesiumMap/internal transport) and GeoJSON rendering (addGeoJsonLayer vs addGeoJsonPrimitive), but the descriptions generally clarify when to use each.

    Naming Consistency3/5

    The dominant pattern is camelCase verb_noun, which is readable and mostly predictable. However, list_toolsets and enable_toolset use snake_case, and a few tools are standalone verbs or nouns (screenshot, highlight, measure), so the set is not fully consistent.

    Tool Count2/5

    At 41 tools, the surface is heavy for a Cesium map server and exceeds the typical 3-15 well-scoped range. The tools are grouped logically, but exposing internal transport tools and many specialized operations makes the set over-scoped.

    Completeness3/5

    Core CRUD and lifecycle coverage is strong for entities, layers, camera viewpoints, basemaps, resources, screenshots, measurement, and clearing. Notable gaps remain: there are no explicit animation/trajectory tools despite clearAll referencing them, no clear CZML rendering path despite storeResource accepting CZML, and no viewpoint deletion operation.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week