Skip to main content
Glama
Sign In
QGIS MCP

QGIS MCP

by GIS-GEORGIA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to QGIS MCP

No user-submitted related servers found.

    Related Servers

    • QGIS MCP Server

      Bytes-007
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables any MCP-speaking AI agent to drive QGIS directly by managing layers, editing features, running processing algorithms, rendering maps, and authoring layouts through 125 tools. It bridges agents to a running QGIS instance over a plugin socket connection, supporting QGIS 3.28-4.x and virtually any MCP client.
      1
      GPL 2.0

    • QGIS MCP Server

      israelwcg011
      F
      license
      Not graded
      quality
      B
      maintenance
      Lets MCP clients inspect and manipulate the project open in the desktop application, including layers, geoprocessing, styles, and map/layout exports, all through tools that run inside the live QGIS session.
      -

    • Maggeloku MCP

      farhan0431
      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

    • dcc-mcp-qgis

      dcc-mcp
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables clients to create, query and edit QGIS projects and vector data in an isolated, new headless PyQGIS process, exporting GeoJSON/GeoPackage, saving and reopening editable QGZ bundles, and rendering PNG maps through typed MCP tools. All operations are workspace-relative with strict path and geometry validation, and never attach to or modify a running QGIS desktop session.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 13 tools

    Disambiguation3/5

    Several capabilities are duplicated across GUI and headless modes: headless_command can invoke list_layers, layer_info, add_layer, export_map, and run_pyqgis, so an agent must decide between equivalent entry points. qgis_status and project_info also overlap in project details. The descriptions do explain GUI vs. headless context, but the boundaries remain somewhat loose.

    Naming Consistency3/5

    Most names use snake_case, and the headless_* family is consistent. However the set mixes verb_noun (list_layers, add_layer, export_map) with noun_phrase (qgis_status, layer_info, project_info) and a proper-noun verb (run_pyqgis), so the pattern is readable but not uniform.

    Tool Count4/5

    13 tools is reasonable for a QGIS bridge covering project, layer, export, scripting, and headless-processing workflows. The only redundancy is the meta headless_command, but it does not push the count into bloat.

    Completeness4/5

    Core workflows are covered: project load/save/info/status, layer add/remove/list/info, map export, PyQGIS, and headless Processing algorithms. Explicit layer update, project creation, and styling operations are absent, but run_pyqgis/headless_command provide escape hatches for many gaps.

    Resources