Unclear The finding doesn't say what specific behavior differs once the memory server is recognized this way.
Claude Code now has dedicated internal constants for a built-in MCP server (a connector that provides tools) named 'memory': a tool name prefix (mcp__memory__), a set of expected read/write tool names, and a pattern that recognizes its dynamic URL, which points at /v2/ccr-sessions/{id}/memory/mcp. This lets the app distinguish its own built-in memory server from MCP servers a user has configured themselves.
Treating the built-in memory server as a known, first-party server (rather than a generic user-configured one) likely allows Claude Code to handle it with special-cased logic, such as different trust or display behavior.
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.
| Contains any other character | JavaScript regular expression, unanchored | `^Notebook` matches any tool whose name starts with `Notebook`; `mcp__memory__.*` matches every tool from the `memory` server |hooks see the edit
The finding doesn't say what specific behavior differs once the memory server is recognized this way.
Anthropic's documentation has since written up mcp__memory__, on Hooks reference.