{"version":"2.1.295","anchor":"mcp-tool-server-registers-extra-capabilities-when-serving-in","canonical_anchor":"mcp-tool-server-registers-extra-capabilities-when-serving-in","heading":"claude mcp serve declares extra capabilities in its remote mode","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/mcp-tool-server-registers-extra-capabilities-when-serving-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### `claude mcp serve` declares extra capabilities in its remote mode\n\nRun in its remote mode, the MCP server started by `claude mcp serve` now declares more capabilities and accepts session details with each tool call\n\n**Unclear.** It is not clear how the remote mode is turned on or whether a user can reach it today.\n\n**What**\n\n`claude mcp serve` lets Claude Code act as an MCP server, meaning other programs can connect to it and use its tools. When it runs in its remote mode, the server now tells those programs about more capabilities. It used to say only that its list of tools can change. Now it also declares:\n\n- support for tool output\n\n- that it handles safety prompts and that it applies session rules, in some cases\n\n- which version of its interface it uses\n\nTool calls can also now carry session rules, a read-only setting, a model, and session details such as a remote session ID and effort level.\n\n**Why**\n\nThis is groundwork for connecting to Claude Code's tools through a remote session.\n\n- Area: MCP\n- Names: `claude mcp serve`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}