Does Cloud Composer have an MCP server?
Cloud Composer maintains an official MCP server.
Google is renaming Cloud Composer to Managed Service for Apache Airflow; the MCP endpoint is regional.
- Access
- Built into the product
- Endpoint
- composer.<region>.rep.googleapis.com/mcp — per-region endpoint
- Category
- Data Platforms
The receipts
Ships inside Cloud Composer's own product rather than as a standalone server. Documented at docs.cloud.google.com.
Connect it
Ships inside the vendor's own app or CLI rather than as a standalone download.
Add it from the terminal, then restart your session:
claude mcp add cloudcomposer -- npx -y <package-from-readme>Swap in the exact package and flags from the package page — most servers need an API key passed as an environment variable.
Add --scope user to make it available in every project.
Open Settings → Developer → Edit Config and add the server to claude_desktop_config.json:
{
"mcpServers": {
"cloudcomposer": {
"command": "npx",
"args": [
"-y",
"<package-from-readme>"
],
"env": {
"API_KEY": "…"
}
}
}
}Restart Claude Desktop after saving.
Add to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for
every project:
{
"mcpServers": {
"cloudcomposer": {
"command": "npx",
"args": [
"-y",
"<package-from-readme>"
],
"env": {
"API_KEY": "…"
}
}
}
}A green dot in Settings → MCP means it connected.
Add to .vscode/mcp.json:
{
"servers": {
"cloudcomposer": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"<package-from-readme>"
]
}
}
}Then pick the server from the tools menu in Copilot's agent mode.
Questions
Does Cloud Composer have an official MCP server?
Yes. Cloud Composer maintains an official MCP server.
How do I connect Cloud Composer to Claude?
Run the server locally and register it in Claude's MCP config. In Claude Code that's a single "claude mcp add" command; in Claude Desktop you add it to claude_desktop_config.json.
How is this verdict verified?
Published to the MCP Registry as com.googleapis.composer/mcp, but the listed composer.googleapis.com/mcp returns 404; Google's docs give the regional endpoint composer.REGION.rep.googleapis.com/mcp, which answers MCP initialize (checked us-central1 and europe-west1). GitHub metadata is refreshed every six hours.
How we know
Published to the MCP Registry as com.googleapis.composer/mcp, but the listed composer.googleapis.com/mcp returns 404; Google's docs give the regional endpoint composer.REGION.rep.googleapis.com/mcp, which answers MCP initialize (checked us-central1 and europe-west1).
- GitHub data refreshed on 2026-10-08, and again every six hours.
- Vendor docs checked by hand on 2026-09-29.
Spotted something out of date? Tell us — corrections ship same-day.