{"version":"2.1.300","anchor":"account-memory-coordinator-caller-metadata","canonical_anchor":"account-memory-coordinator-caller-metadata","heading":"MCP servers can ask for a coordinator's access to account memory","tier":"use","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/account-memory-coordinator-caller-metadata","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### MCP servers can ask for a coordinator's access to account memory\n\nAn MCP server can now declare a coordinator as its caller, and memory tool access is then granted at none, some or all levels\n\n**Unclear.** How this is switched on, and whether readers can reach it, is not known.\n\n**What**\n\nAn MCP server, an add-on program that gives Claude extra tools, can now declare an experimental capability naming a \"coordinator\" as its caller. Claude Code then grants memory tool access at one of three levels: none, some or all. Requests also carry a note identifying the memory caller.\n\n**Why**\n\nThis looks like groundwork for a coordinator mode that uses memory.\n\n- Area: MCP\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}