mcp

{
  "id": "aix_f7c6a561f5",
  "name": "mcp",
  "operator": "(unclaimed - source: registry-official · publisher: com.googleapis.composer)",
  "description": "Interact with your Google Cloud Composer resources using natural language commands.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-11-11",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "general-tools"
  ],
  "protocols": {
    "mcp": "https://composer.googleapis.com/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 326,
    "uptime_30d": 1,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 76,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-11-11T23:00:54.280Z"
  },
  "pricing_model": "unknown",
  "unreachable": false,
  "profile": {
    "mcp_server": "StatelessServer",
    "mcp_version": "ESF",
    "tool_count": 16,
    "tools": [
      {
        "name": "create_environment",
        "description": "Initiates the creation of a new Managed Airflow environment with default settings.\n\nThis tool creates a small private IP environment with a default configuration, including\ndefault networking settings.\n\nCreating public IP environments, or customizing most settings (such as network, subnetwork,\nnetwork attachment, environment size, CMEK or custom environment bucket) is not supported.\n\nIf the user requests settings that aren't supported by the tool\nparameters, inform them that this tool can't create an environment in the requested\nconfiguration, and that they should use gcloud CLI or Cloud Conso"
      },
      {
        "name": "get_environment",
        "description": "Retrieves details about a specific Managed Airflow environment, including its configuration\nand status.\n\nUse this tool to check the current state of an environment, its Airflow version, Airflow UI URL,\nenvironment's bucket, or other configuration details.\n"
      },
      {
        "name": "list_environments",
        "description": "Lists all Managed Airflow environments in a given project and location.\n\nUse this tool to when you need to know which environments exist in a specific project and\nlocation.\n\nResults are paginated; use `page_size` to control the number of results per page and\n`page_token` from a previous response to get the next page. If `page_token` is not present\nin the response, there are no more results.\n"
      },
      {
        "name": "delete_environment",
        "description": "Initiates the deletion of a Managed Airflow environment.\n\nWarning: This is a destructive action permanently deletes an environment and can't be undone.\nAlways ask the user to confirm the deletion before proceeding.\n\nThis tool triggers the environment deletion process, which is a long-running operation that\ntypically takes 10-20 minutes. The tool returns an operation object. Use the `get_operation`\ntool with the operation name returned by this tool to poll for deletion status.\n"
      },
      {
        "name": "manage_pypi_packages",
        "description": "Manages PyPI packages in a Managed Airflow environment.\n\nUse this tool to install and uninstall PyPI packages in the Managed Airflow environment, or\nchange PyPI package versions or extras.\n\nTo install packages or change versions or extras, use the `update_packages` field. To\nremove packages, use the `remove_packages` field. At least one package must be\nspecified in one of these fields. The same package can't be specified in both fields.\n\nThis tool triggers an environment update, which is a long-running operation that can take\nseveral minutes. The tool returns an operation object. Use the `get_"
      },
      {
        "name": "get_operation",
        "description": "Gets the latest status of a long-running operation.\n\nSeveral tools like `create_environment`, `delete_environments`, and `manage_pypi_packages`\nreturn an operation object, because they initiate processes that take time to complete. Use\nthis tool to check if such an operation has finished and whether it was successful.\n\nProvide the `name` of the operation as returned by the tool that initiated it.\n\nA completed operation may include the details specific to the operation, described in the\ndescription of the tool that initiates the operation.\n"
      },
      {
        "name": "get_dag",
        "description": "Retrieves metadata and status of a specific DAG in a Managed Airflow environment.\n\nUse this tool when you need to check if a DAG exists, inspect its metadata (such as schedule\nor current state), or verify whether a newly uploaded/updated DAG file has been imported by\nAirflow (see `list_import_errors` tool description for more details). In particular, if a\nDAG was recently uploaded but `get_dag` returns NOT_FOUND, use `list_import_errors` to check\nif any errors occurred during the import.\n"
      },
      {
        "name": "list_dags",
        "description": "Lists all DAGs in a Managed Airflow environment.\n\nUse this tool to get a list of all DAGs in the environment, for example to discover the DAGs\npresent in the environment or get the state or properties of each DAG.\n\nResults are paginated; use `page_size` to control the number of results per page and\n`page_token` from a previous response to get the next page. If `page_token` is not present\nin the response, there are no more results.\n"
      },
      {
        "name": "get_dag_source_code",
        "description": "Retrieves the DAG source code from a Managed Airflow environment.\n\nUse this tool when you want to understand DAG implementation details, for example to\nunderstand why a DAG run has failed, or to debug DAG's behavior. The tool returns the latest\nversion of the source code.\n"
      },
      {
        "name": "get_dag_run",
        "description": "Retrieves details of a specific DAG run from a Managed Airflow environment.\n\nUse this tool when you need to retrieve details of a specific DAG run, for example its\nstate, start time or end time.\n\nThis tool does not return DAG run logs directly. Instead, use the `cloud_logging_filter`\nfield from the response to query Cloud Logging for the logs for this DAG run.\n"
      },
      {
        "name": "list_dag_runs",
        "description": "Lists DAG runs in a Managed Airflow environment.\n\nUse this tool to get a list of DAG runs in the environment, or runs for a specific DAG, for\nexample to determine the overall healthiness of the environment or DAG. The tool returns DAG\nruns in the order of creation date, most recent first.\n\nResults are paginated; use `page_size` to control the number of results per page and\n`page_token` from a previous response to get the next page. If `page_token` is not present\nin the response, there are no more results.\n"
      },
      {
        "name": "get_task_instance",
        "description": "Retrieves details of a specific task instance from a Managed Airflow environment.\n\nUse this tool to retrieve details of a specific task instance, such as its state,\nstart time, end time, or parameters, to understand its status or to debug a failure.\n\nThis tool does not return task instance logs directly. Instead, use the\n`cloud_logging_filter` field from the response to query Cloud Logging for the logs for\nthis task instance.\n"
      },
      {
        "name": "find_last_failed_dag_runs",
        "description": "Finds failed DAG runs in a Managed Airflow environment.\n\nUse this tool to find recent DAG run failures, for example to begin troubleshooting.\n\nIf the user wants to troubleshoot a specific DAG, provide the DAG ID to get the details of\nits last failed run. If the user doesn't know which DAG is failing, or wants to see recent\nfailures across all DAGs, leave the DAG ID empty; in this case, the tool will return the\nlast failed DAG run for every DAG in the environment that has at least one failure.\nIf the response returns more than one DAG run and the user asked for troubleshooting or\nexplaining the"
      },
      {
        "name": "list_failed_task_instances",
        "description": "Lists failed task instances of a specific DAG run in a Managed Airflow environment.\n\nIf a DAG run has failed, use this tool to get the list of task instances of this DAG run\nthat are in the FAILED state and may have caused the DAG run failure.\n\nThis tool does not return task instance logs directly. Instead, for each task instance,\nuse the `cloud_logging_filter` field from the response to query Cloud Logging for\nthe logs for that task instance.\n"
      },
      {
        "name": "trigger_dag",
        "description": "Triggers a DAG run for a specified DAG in a Managed Airflow environment.\n\nUse this tool when you need to manually start a new run of a DAG.\n\nThe tool returns a DAG run object containing the details and state of the newly triggered\nrun. You can use the `get_dag_run` tool to poll for state changes.\n"
      },
      {
        "name": "list_import_errors",
        "description": "Lists Python import errors and parsing failures in a Managed Airflow environment.\n\nUse this tool to check if all DAGs are being parsed correctly in the environment.\n\nAfter uploading a DAG, use this tool alongside `get_dag` to check its parsing status:\n- **Success**: `get_dag` returns DAG details.\n- **Import failed**: `get_dag` returns `NOT_FOUND` and `list_import_errors` returns error\n  details and stack traces referencing the DAG file created after the upload.\n- **Pending parsing**: `get_dag` returns `NOT_FOUND` and `list_import_errors` has no errors\n  referencing the DAG file, created after "
      }
    ],
    "profiled_at": "2026-11-11T23:00:54.280Z"
  }
}