Under the hood
Claude Code now specifically recognizes its built-in 'memory' MCP server by name and URL shape
What
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.
Why
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.
Names in the bundlemcp__memory__
Documented inclaude-code/hooks
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding doesn't say what specific behavior differs once the memory server is recognized this way.