{"version":"2.1.311","anchor":"mcp-roots-can-come-from-a-session-directory","canonical_anchor":"mcp-roots-can-come-from-a-session-directory","heading":"MCP servers can be told a session's own directory as their root","tier":"notice","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/mcp-roots-can-come-from-a-session-directory","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### MCP servers can be told a session's own directory as their root\n\nThe folder list Claude Code gives MCP servers now uses a session's directory when one is set, and the working directory otherwise\n\n**Unclear.** When a session has its own directory, and so when the roots differ from the working directory, is not stated.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. Claude Code tells each one which folders it may work in, a list called its roots. That list now starts from the current session's own directory when the session has one. When there is no such directory, it falls back to the working directory, which is the folder Claude Code was started in. Before, it always used the working directory.\n\n**Why**\n\nWhere more than one session is running, an MCP server may now be told a different folder than before. If a server seems to be looking in an unexpected place, the session's directory is the place to check.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}