{"version":"2.1.299","anchor":"stray-memory-server-mcp-entries-refused-at-connect","canonical_anchor":"stray-memory-server-mcp-entries-refused-at-connect","heading":"MCP servers that reach the account memory server unofficially are refused","tier":"notice","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/stray-memory-server-mcp-entries-refused-at-connect","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### MCP servers that reach the account memory server unofficially are refused\n\nAn MCP server that can reach the account memory server but is not the cloud service's own entry is now refused at connect\n\n**Unclear.** It is not clear what the second check is that lets such a server connect anyway.\n\n**What**\n\nMCP (Model Context Protocol) servers give Claude Code extra tools. When an MCP server can reach your account's memory server but is not the entry the cloud service provides for it, Claude Code now refuses it when connecting, unless a second check lets it through. Its tools are then not available, and Claude Code logs a warning.\n\n**Why**\n\nIf you configured your own MCP server that points at the memory server, its tools may stop being available. Check the warning in the logs if tools go missing.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: yes"}