Unclear Whether ReadCalls is available to every client of claude mcp serve or held behind a setting is not stated.
What
claude mcp serve runs Claude Code as an MCP server, so another program can connect to it and use its tools. A tool call is one use of a tool, such as running a command. Two things are new:
- A tool named ReadCalls reports on tool calls that are running, finished or running in the background, and can be narrowed to a single call by its
tool_use_id. - An experimental capability,
anthropic/uploadsUnderSessionRules, and arepo_rulesargument let the connecting program add its own deny and ask rules, which decide what is blocked and what needs approval.
Why
A program connected to claude mcp serve can now check on the state of calls and attach its own permission rules.
Names in the bundleclaude mcp serve
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up claude mcp serve, on Connect Claude Code to tools via MCP.
A `backgroundOutputPath` field in a Bash or PowerShell result from `claude mcp serve` means the call left its command running [in the background](/docs/en/tools-reference#background-commands). A command runs in the background when your cli…mcp see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Whether ReadCalls is available to every client of `claude mcp serve` or held behind a setting is not stated.
Anthropic's documentation agrees
Anthropic's documentation has since written up claude mcp serve, on Connect Claude Code to tools via MCP.
Anthropic's release notes agree
Fixed classifier_category missing from OpenTelemetry tool_decision events for most auto mode classifier blocks, and new tool_decision…