Skip to main content
The Pome MCP — the Pome Control MCP, or “coach MCP” — is a hosted Model Context Protocol server at https://mcp.pome.sh/mcp. Transport is Streamable HTTP only (no SSE resumability). It lets any MCP client — Claude Code, Claude Desktop, claude.ai — author scenarios, launch evaluation runs, and read back scored reports, entirely through tool calls. This is what makes Pome usable by an AI agent directly, not just a human at a CLI.

Coach and examinee

The agent you connect to the MCP is the coach. It authenticates, picks or authors a scenario, launches a run, and reads the report. The coach can see grading criteria. The examinee is a faithful clone of the agent-under-test that Pome launches separately — for example, on Anthropic Managed Agents — with its service MCP URLs swapped to Pome digital twins. The examinee holds zero Pome tools and never sees the criteria. run_scenario hands the coach a launch spec for the clone; the coach launches it.
First call is always get_started. It returns the coach playbook.

Tool index

Orientation

Authoring

Run lifecycle

Connect

Add the server and authenticate.

Tools

Full reference for every tool.

Workflow

The end-to-end coach workflow.

Digital Twins reference

The deterministic, resettable SaaS services run_scenario provisions against.