Skip to main content
Glama

Related Servers

Alternatives to MWAA MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables inspection and management of Apache Airflow DAGs, runs, and logs across multiple instances. It provides tools for monitoring workflows and performing gated write operations like triggering DAGs or clearing task instances.
      16
      33 PyPI
      2
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for Amazon MWAA that enables managing Airflow environments, DAGs, runs, task instances, and configurations through natural language, using secure AWS-native API access and read-only by default.
      21
      Apache 2.0
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server that wraps the Apache Airflow REST API, enabling clients to manage DAGs, monitor task instances, and handle workflows through a standardized interface. It provides comprehensive access to Airflow features including DAG runs, variables, connections, and XComs.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Apache Airflow through the Model Context Protocol, allowing users to manage DAGs, task instances, variables, connections, pools, XComs, and datasets.
      MIT

    TDQS

    A3.6/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific MWAA/Airflow resources (environments, DAGs, tasks, connections, variables), but there is some overlap between airflow_best_practices and dag_design_guidance as both provide guidance rather than operational actions. The descriptions help differentiate them, but an agent might initially confuse these two guidance tools.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern throughout (e.g., create_environment, list_dags, get_dag_run, update_environment). All tools use snake_case with clear action-object naming, making the set predictable and easy to navigate.

    Tool Count4/5

    With 21 tools, the count is slightly high but reasonable for the comprehensive MWAA management scope, covering environment lifecycle, DAG operations, task monitoring, and system components. It might feel heavy, but each tool serves a specific function in this domain.

    Completeness5/5

    The toolset provides complete coverage for MWAA management, including environment CRUD (create, get, update, delete), DAG operations (list, get, trigger, source), task monitoring (instances, logs), and auxiliary functions (connections, variables, tokens, guidance). No obvious gaps exist for core workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues