{"version":"2.1.283","anchor":"user-mcp-servers-named-memory-are-dropped-when-the-cli-own","canonical_anchor":"user-mcp-servers-named-memory-are-dropped-when-the-cli-own","heading":"Your own MCP server named \"memory\" is dropped when Claude Code supplies one","tier":"notice","area":"Account Memory","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/user-mcp-servers-named-memory-are-dropped-when-the-cli-own","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Your own MCP server named \"memory\" is dropped when Claude Code supplies one\n\nIf Claude Code's own \"memory\" server is configured, any other MCP server whose name works out to \"memory\" is removed from the server list\n\n**Unclear.** It is not clear what adds Claude Code's own memory server, whether that is switched on for everyone, or whether you are told when yours is dropped.\n\n**What**\n\nMCP servers are connections that give Claude extra tools, and each has a name. When the list of configured servers includes a server named \"memory\" that belongs to Claude Code itself, any other configured server whose name works out to \"memory\" is now removed from the list.\n\n**Why**\n\nIf you set up your own MCP server called \"memory\", it may disappear without warning when Claude Code's own server is present. Renaming yours avoids the clash.\n\n- Area: Account Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}