{"version":"2.1.301","anchor":"mcp-task-outcome-refuses-a-project-folder-storage-scope","canonical_anchor":"mcp-task-outcome-refuses-a-project-folder-storage-scope","heading":"MCP task results can no longer be saved to a project-folder scope","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/mcp-task-outcome-refuses-a-project-folder-storage-scope","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### MCP task results can no longer be saved to a project-folder scope\n\nSaving the result of an MCP task now fails with an error when the target is the project folder, which no storage backend can accept\n\n**Unclear.** Which situations lead an MCP task result to be saved to the project folder is not known.\n\n**What**\n\nMCP (Model Context Protocol) lets Claude Code connect to outside tools and services. When Claude Code saves the result of an MCP task, it now refuses if the place to save it is the project folder. It stops with this error: \"mcp task outcome: the project folder is a storage scope and no storage backend can take it\".\n\n**Why**\n\nIf you see this message, the task result was not saved, because none of the available storage backends accepts the project folder as a place to keep it.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}