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
      C
      maintenance
      Enables natural language interaction with Apache Airflow for querying DAGs, monitoring execution, and troubleshooting failures.
      42 PyPI
      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
      46 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 84 tools

    Disambiguation4/5

    Most tools map to distinct resources and actions, and the descriptions clarify close pairs such as get_pipeline/get_pipeline_data/pipeline_context and list_task_runs vs list_task_runs_for_pipeline_run. A few adjacent areas remain, like pipeline-run listing vs whats_broken and workspace integrations vs agent integrations, but they are generally readable.

    Naming Consistency4/5

    The set is predominantly consistent snake_case verb_noun naming across resource families. Exceptions like diagnose, whats_broken, and pipeline_context are readable but break the otherwise predictable pattern.

    Tool Count1/5

    84 tools is far beyond the typical 3-15 range and creates an extremely heavy surface for an agent to navigate. Even though the domain is broad, the many CRUD and list variants across each resource family make this an extreme mismatch.

    Completeness4/5

    Coverage is extensive: pipelines, runs, task runs, incidents, monitors, agents, sessions, skills, environments, connections, assets, and audit events all have relevant lifecycle operations. Minor gaps remain, such as no obvious integration discovery/list tool and limited write coverage for assets or operations, likely by design.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources