{"version":"2.1.283","anchor":"user-configured-mcp-servers-named-memory-are-refused-when","canonical_anchor":"mcp-mcp-servers-refused-for-a-reserved-name-no-longer-fall","heading":"Your own MCP server named \"memory\" is refused when Claude Code supplies its account memory server","tier":"notice","area":"Account Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/user-configured-mcp-servers-named-memory-are-refused-when","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Your own MCP server named \"memory\" is refused when Claude Code supplies its account memory server\n\nMCP 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\n\n**Unclear.** The exact wording of the refusal in `\/mcp` is not known.\n\n**What**\n\nMCP (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.\n\n- The removed servers are recorded as `reservedNameRefusals` and passed to the `\/mcp` dialog.\n\n- Pending or rejected project approvals for a refused name are dropped.\n\n- `\/mcp` no longer shows \"No MCP servers configured\" when the only thing left to show is such a refusal.\n\n- A warning notification for these refusals has been added, but in this build it has nothing to show, so no warning appears yet.\n\n**Why**\n\nIf 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.\n\n- Area: Account Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}