Skip to main content
Glama

Related Servers

Alternatives to QGISMCP

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
      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
    • 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
      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
    • 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,093
      -
    • A
      license
      A
      quality
      A
      maintenance
      Enables Claude Desktop to view and interact with the currently open QGIS project, including layers, styling, selections, Processing algorithms, attribute editing, and geocoding, all running locally.
      10
      GPL 2.0

    TDQS

    B3.3/5.0

    Scored across 15 tools

    Disambiguation5/5

    All tools have clearly distinct purposes. Layer operations (add, remove, get, zoom) are separate from project operations (create, load, save) and execution tools (code vs processing). Ping is a standalone health check.

    Naming Consistency5/5

    Nearly all tools follow a consistent verb_noun pattern with underscores (e.g., add_raster_layer, get_layers, remove_layer). The only exception is 'ping', which is a standard single-word health check command.

    Tool Count5/5

    With 15 tools, the count is well within the ideal range. Each tool serves a core QGIS function—project management, layer operations, execution, retrieval, rendering—without redundancy or gaps.

    Completeness4/5

    The tool set covers essential CRUD for projects and layers, plus code execution, processing algorithms, and rendering. Missing advanced features like layer style updates or feature editing, but core workflows are complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues