{"version":"2.1.269","anchor":"dedicated-internal-memory-mcp-server-naming-and-endpoint-rec","canonical_anchor":"dedicated-internal-memory-mcp-server-naming-and-endpoint-rec","heading":"Dedicated internal memory MCP server naming and endpoint recognized","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/dedicated-internal-memory-mcp-server-naming-and-endpoint-rec","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Dedicated internal memory MCP server naming and endpoint recognized\n\nClaude Code now specifically recognizes its built-in 'memory' MCP server by name and URL shape\n\n**Unclear.** The finding doesn't say what specific behavior differs once the memory server is recognized this way.\n\n**What**\n\nClaude 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.\n\n**Why**\n\nTreating 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.\n\n- Area: MCP\n- Names: `mcp__memory__`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}