Skip to main content
Glama
orchestra-hq

Orchestra MCP Server

Official
by orchestra-hq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Orchestra MCP Server

No user-submitted related servers found.

    Related Servers

    • Airflow MCP

      ponderedw
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with Apache Airflow for querying DAGs, monitoring execution, and troubleshooting failures.
      1
      MIT

    • airbyte-mcp

      trustxai
      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
      77 PyPI
      5
      Apache 2.0

    • Airflow MCP

      hipposys-ltd
      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
    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.4/5.0

    Scored across 49 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but the pipeline retrieval trio (get_pipeline, get_pipeline_data, pipeline_context) and the task-run list variants (list_task_runs vs list_task_runs_for_pipeline_run) create some overlap. Descriptions help differentiate, but an agent could still misselect among them.

    Naming Consistency4/5

    Predominantly consistent verb_noun pattern (get_, list_, create_, update_, etc.), with a few outliers like whats_broken, pipeline_context, and diagnose that break the pattern. Overall the naming is readable and mostly predictable.

    Tool Count2/5

    49 tools is well above the recommended 3-15 range and is heavy even for a broad orchestration platform. Many tools could be consolidated or omitted, and the sheer count risks overwhelming an agent and increasing selection errors.

    Completeness4/5

    Covers core CRUD and lifecycle operations for pipelines, incidents, monitors, environments, and task runs, but lacks delete operations for several resources (e.g., delete_pipeline, delete_monitor, delete_environment) and manual incident creation. Agents can work around most gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources