Skip to main content
Glama

Related Servers

Alternatives to QGISMCP

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
      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
      A
      quality
      B
      maintenance
      A 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.
      9
      89
      MIT
    • 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,082
      -
    • A
      license
      B
      quality
      A
      maintenance
      An MCP server that enables AI assistants to directly control QGIS for tasks like layer management, feature editing, and map rendering. It provides a suite of 50 tools to execute processing algorithms and manage GIS projects through natural language commands.
      118
      281
      GPL 2.0

    TDQS

    B3.1/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have distinct purposes, such as add_raster_layer vs add_vector_layer, but some overlap exists: get_layers retrieves all layers, while get_layer_features retrieves features from a specific vector layer, which could cause confusion if an agent needs general layer info. However, descriptions clarify their differences, preventing major misselection.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, such as add_raster_layer, execute_code, and get_project_info. There are no deviations in naming conventions, making the set predictable and easy to parse for agents.

    Tool Count5/5

    With 15 tools, this server is well-scoped for QGIS operations, covering project management, layer handling, rendering, and code execution. Each tool serves a clear purpose without redundancy, fitting the typical range of 3-15 tools for a focused domain.

    Completeness4/5

    The tool set provides comprehensive coverage for core QGIS workflows, including project CRUD (create, load, save), layer management (add, remove, zoom), and information retrieval. A minor gap is the lack of tools for editing layer attributes or geometries, but agents can work around this using execute_code or execute_processing for advanced operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues