CMA as an MCP server

You can expose Managed Agents as MCP tools by installing the CMA server repository, configuring environment variables, and registering the server with Claude Desktop using the stdio transport for local chat-driven workflows.

Yes, the MCP server supports both stdio for Claude Desktop and Streamable HTTP for claude.ai web Connector, using the identical tool definitions for Managed Agents Sessions API endpoints across both transport modes.

To enforce relay mode and return the backend agent's reply verbatim, you must apply the relay-mode instruction pattern using list_agents, create_session, send_message, and wait_for_idle to prevent the frontend model from answering directly.

The MCP server maps Managed Agents Sessions API endpoints for agents, sessions, events, and archiving into individual MCP tools, enabling interactive operations like creating sessions, streaming tool execution, and returning agent replies.

You need to install the repository and configure environment variables for your Managed Agents environment, but no external dependencies are required beyond the chosen client transport and the Managed Agents API access.

If agent replies are missing, verify you are using the correct relay-mode instruction pattern with wait_for_idle and that environment variables for the Managed Agents environment are properly configured for your chosen transport mode.