Skip to main content
Glama
yo-1
by yo-1

Related Servers

Alternatives to qgis-dev-probe-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to control QGIS by executing PyQGIS commands, managing layers and projects, exporting maps, and running Processing algorithms through either a GUI plugin or a headless Python process.
      13
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to see, control, and debug PySide6 desktop applications without modifying their source code, by capturing screenshots, inspecting widget trees, performing clicks and typing, reading logs, and running Python inside the app process.
      22
      63 PyPI
      6
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables LLMs to control a live Siril GUI session through a bridge, allowing them to run Siril commands and scripts, inspect image state, get previews and statistics, and perform edits such as selections and undo.
      9
      1
      GPL 3.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables LLM clients to control a live Siril GUI session through an in-app Python bridge, exposing tools to inspect image state and selection, run commands or scripts, get previews and statistics, and undo operations.
      9
      GPL 3.0
    • 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

    TDQS

    B3.2/5.0

    Scored across 24 tools

    Disambiguation4/5

    Each resource family has clear action boundaries (list vs run vs inspect), and the click_widget/trigger_action distinction is explicitly documented. Minor overlap remains between execute_code and the specialized run_recipe/run_algorithm tools, and ping/get_info both expose diagnostic information, so an agent may occasionally hesitate.

    Naming Consistency4/5

    All names use lowercase snake_case, and the dominant pattern is verb_noun (list_layers, run_algorithm, get_info). A few utility commands such as ping, wait, and screenshot break the verb_noun pattern but do not create mixed or confusing conventions.

    Tool Count3/5

    24 tools sit at the upper end of the heavy range, covering many subdomains including GUI control, layers, Processing, plugins, recipes, and diagnostics. Most tools are justified, but the breadth makes the set feel borderline rather than tightly scoped.

    Completeness4/5

    The surface covers the main dev-probe workflows: GUI inspection/control, layer add/remove/list/inspect, Processing discovery/execution, plugin reload, recipes, logs, and screenshots. Gaps exist in layer/project mutation and feature editing (for example, no update_layer, save_project, or feature CRUD), though execute_code provides a workaround.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive