You'll notice
claude mcp remove now refuses org-managed servers with an explicit message instead of reporting them as not found.
Running claude mcp remove on a server with no configured local scope now checks whether it's actually provided by managed or enterprise settings; if so, it refuses with an explicit message saying the server cannot be removed locally, instead of just reporting it as not found. claude mcp get gained a matching message for the same case.
Names in the bundleclaude mcp removeclaude mcp get
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 remove, on Claude Code changelog.
* Fixed an MCP server re-added under the same name after `claude mcp remove` still showing as needing authentication instead of reconnectingchangelog see the edit
Confirmed since
Anthropic's documentation has since written up claude mcp get, on Connect Claude Code to tools via MCP.
* `claude mcp list` and `claude mcp get` outputmcp see the edit
Added since
A small documentation edit on Connect Claude Code to tools via MCP touched a line naming claude mcp remove after this was published.
* To add or change the secret later, remove the server with `claude mcp remove <name>`, then add it again with `--client-secret` and the same `--scope`mcp see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Connect Claude Code to tools via MCP touched a line naming claude mcp remove after this was published.