Skip to main content
Glama
Orchestra MCP Server

Orchestra MCP Server

Official
by orchestra-hq

Related Servers

Alternatives to Orchestra MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language interaction with Apache Airflow for querying DAGs, monitoring execution, and troubleshooting failures.
      38 PyPI
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables interaction with an Airbyte instance through natural language, supporting workspaces, sources, destinations, connections, jobs, logs, tags, streams, and connector definitions.
      36
      43 PyPI
      5
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to interact with Apache Airflow orchestration platform through natural language to query pipeline statuses, troubleshoot DAG failures, trigger DAGs, and analyze configurations.
      11
      MIT

    TDQS

    B3.4/5.0

    Scored across 85 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, and the detailed descriptions clarify boundaries between related tools like whats_broken, diagnose, and get_task_run. However, there is some overlap among pipeline retrieval tools (get_pipeline, get_pipeline_data, pipeline_context) and among task-run listing/downloading tools that could still lead to misselection in a surface this large.

    Naming Consistency4/5

    The vast majority of tools follow a clear snake_case verb_noun convention (list_pipelines, create_agent, update_monitor, delete_environment). A few outliers like whats_broken, diagnose, and pipeline_context break the verb_noun pattern, but they remain readable and consistent in casing.

    Tool Count1/5

    With 85 tools, this server is far beyond a reasonable MCP tool surface and well past the 50+ threshold for an extreme mismatch. Even for a broad orchestration platform, the volume is likely to overwhelm tool selection and increase the chance of wrong-tool calls.

    Completeness4/5

    Coverage is very broad across pipelines, runs, tasks, incidents, monitors, agents, skills, integrations, environments, assets, and audit events, with CRUD where appropriate. Minor gaps remain, such as no explicit pipeline-run retry, no integration catalog listing tool, and no manual incident create/delete operations.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues