feat(managed_agents): CMA Sessions API as an MCP server (stdio + HTTP)

[rlancemartin]

A thin MCP server wrapping the Managed Agents Sessions API, so Claude Desktop or claude.ai web can start and chat with an org's hosted CMA agents via tool calls. DIY bridge until "publish agent to claude.ai" is first-class.

User ─▶ Claude (Desktop or claude.ai) ─▶ MCP: send_message + wait_for_idle ─▶ CMA session
  ▲                                                                              │
  └──────────────────────── agent's reply ◀─── stream-to-idle ◀──────────────────┘

managed_agents/cma-mcp/

9 tools (shared src/tools.ts) — 8 are 1:1 endpoint wrappers; wait_for_idle is the one SSE→request/response shim. Two entrypoints:

Entrypoint	Transport	Client	LOC
src/server.ts	stdio	Claude Desktop / Claude Code	~10
src/server-http.ts	Streamable HTTP + bearer auth	claude.ai web custom Connector	~40

Dockerfile for Fly/Railway/Render. Authoring (agents.create), destructive ops, and secrets deliberately not exposed; rationale in skill.md.

Tested

• Claude Desktop (stdio): create_session → send_message → wait_for_idle loop proven end-to-end against a live agent.
• HTTP transport: smoke-tested via ngrok — 401 unauth'd, tools/list returns 9 with bearer token.

[github-actions]

Full Github Actions output

[github-actions]

/model-check findings

Reviewed model references in the changed files:

• managed_agents/cma-mcp/CLAUDE.md
• managed_agents/cma-mcp/README.md
• managed_agents/cma-mcp/skill.md

No Claude model IDs are referenced in any of the three files (no claude-opus-*, claude-sonnet-*, claude-haiku-*, or anthropic.claude-* strings). Nothing to flag against the current public models list.

The files describe the MCP server's structure, setup paths, and tool wrappers — model selection is delegated to the CMA-side agent configuration (created via the ant CLI or Console), not pinned here, which is the right call for a transport-layer wrapper.

One note (not a blocker)

README.md line 50 specifies @anthropic-ai/sdk ≥ 0.95.1 — that's an SDK version, not a model ID, so it's outside /model-check's scope. Worth confirming separately that this minimum supports the CMA Sessions API surface the server uses.

✅ No action required for model usage.