Your own MCP server named "memory" is refused when Claude Code supplies its account memory server
MCP servers whose name clashes with Claude Code's own "memory" server are dropped and recorded as reserved-name refusals, and /mcp no longer looks empty
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Account MemoryArea: what it touches
ImprovementsKind: in v2.1.283,
ImprovementsSection of the release
Unclear The exact wording of the refusal in /mcp is not known.
What
MCP (Model Context Protocol) servers are outside programs that give Claude extra tools. When Claude Code's own config includes a "memory" MCP server for account memory, any other server with that name is now removed from your server list. Names are compared after normalising them.
The removed servers are recorded as reservedNameRefusals and passed to the /mcp dialog.
Pending or rejected project approvals for a refused name are dropped.
/mcp no longer shows "No MCP servers configured" when the only thing left to show is such a refusal.
A warning notification for these refusals has been added, but in this build it has nothing to show, so no warning appears yet.
Why
If you have your own MCP server called "memory", it will disappear in sessions that have account memory. /mcp no longer claims you have no servers configured when this is the reason the list is short.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe exact wording of the refusal in `/mcp` is not known.
Anthropic's release notes agreeFixed MCP sign-in for a server with no valid URL failing with an opaque SDK error; /mcp no longer offers Authenticate for such servers
