Skip to main content
Glama

Related Servers

Alternatives to Quarto MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides any MCP-capable coding agent with shared, warm language-server intelligence and project-local configuration, so diagnostics, definitions, references, hover, symbols, code actions, formatting, rename, and sync behave consistently across harnesses and sessions. This lets users switch agent tools without reconfiguring LSP integrations or falling back to CLI verification.
      8 npm
      MIT
    • 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
    • A
      license
      C
      quality
      C
      maintenance
      Enables MCP clients to inspect, validate, test, export, and query Godot projects, including live state from an open editor via a bridge addon.
      20
      24 npm
      MIT
    • 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.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides project management capabilities through terminal, web UI, or MCP stdio, including plans, code analysis, and filesystem-safe operations.
      12 npm
      MIT

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: default metadata retrieval/set, project creation, rendering, and inspecting Quarto metadata. There is no overlap or ambiguity between the tools.

    Naming Consistency3/5

    The naming pattern is mixed: defaults_get/defaults_set use noun_verb order, while create_project, render, and inspect use verb or verb_noun order. Despite the inconsistency, the names are still readable and somewhat predictable.

    Tool Count5/5

    With 5 tools, the server is well-scoped for Quarto project management. Each tool covers a distinct necessary action without redundancy or excessive surface area.

    Completeness4/5

    The tool surface covers the core workflows: creating projects, rendering, inspecting metadata, and managing defaults. Minor gaps exist, such as no way to list or delete projects, but projects are temporary and the main workflow is supported.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive