Skip to main content
Glama

Related Servers

Alternatives to QGIS MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      D
      maintenance
      QGISMCP connects QGIS to Claude AI through the Model Context Protocol (MCP), allowing Claude to directly interact with and control QGIS for project creation, layer loading, code execution, and more.
      15
      1
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Connects QGIS to Claude AI through the Model Context Protocol, enabling AI-assisted project creation, layer manipulation, processing algorithm execution, and Python code running within QGIS.
      7
      -
    • 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
      B
      quality
      D
      maintenance
      A 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.
      15
      10
      Creative Commons Zero v1.0 Universal
    • 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
    • F
      license
      B
      quality
      F
      maintenance
      Connects Claude AI to QGIS through the Model Context Protocol, allowing Claude to directly interact with and control QGIS for tasks like project creation, layer manipulation, and code execution.
      15
      1,131
      -

    TDQS

    A3.5/5.0

    Scored across 102 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but some overlap exists, e.g., get_canvas_screenshot vs render_map (both capture canvas, one faster no re-render), and get_layers vs get_layer_tree vs get_active_layer (hierarchical vs flat vs single). Descriptions generally clarify, but the large set introduces minor ambiguity.

    Naming Consistency5/5

    Tool names overwhelmingly follow a consistent verb_noun pattern (e.g., add_bookmark, get_layers, set_canvas_extent). Minor exceptions like field_calculator or batch_commands are still descriptive and do not break the overall predictability.

    Tool Count3/5

    102 tools is very high for a typical MCP server. While QGIS is a complex GIS platform that can justify many tools, the count may overwhelm agents. A more focused set (e.g., 50-60) might balance completeness and usability.

    Completeness5/5

    The tool surface covers nearly all core GIS workflows: layer management, styling, print layouts, processing algorithms, expressions, spatial analysis, and more. Obvious gaps (e.g., advanced geoprocessing) are addressed by the execute_processing tool that wraps all Processing algorithms.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues