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.
      439 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
      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

    B3.3/5.0

    Scored across 36 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions: the entity creators (addMarker, addModel, addPolygon, addPolyline, addLabel) each handle a different geometry, and camera tools (flyTo, setView, zoomToExtent, loadViewpoint) are differentiated by animation vs. instant vs. bbox vs. named restore. Minor overlap exists between addGeoJsonLayer and addGeoJsonPrimitive, and between queryEntities and getEntityProperties, but descriptions largely disambiguate them.

    Naming Consistency2/5

    The server mixes camelCase (exportScene, listSessions, removeLayer, getLayerSchema) with snake_case (list_toolsets, enable_toolset, addGeoJsonLayer, storeResource) within the same tool list. There is no single predictable convention an agent can rely on, though individual names remain readable.

    Tool Count2/5

    36 tools is well above the 25-tool threshold for a heavy surface. The toolset gating system (list_toolsets/enable_toolset) is a thoughtful mitigation, but the exposed set is still large and increases selection cost.

    Completeness4/5

    Coverage is broad across camera control, entity add/update/remove/query, layer management, resource storage, viewpoints, screenshots, highlighting, and measurement. Gaps remain: no tools to add imagery/terrain layers or to create animations/trajectories despite clearAll referencing them, though these may sit behind disabled toolsets.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week