{"version":"2.1.319","anchor":"mcp-background-tasks-server-unconfigured-handling-result-r","canonical_anchor":"mcp-background-tasks-server-unconfigured-handling-result-r","heading":"Long-running MCP tasks cope with a removed server and point you to \/mcp","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/mcp-background-tasks-server-unconfigured-handling-result-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Long-running MCP tasks cope with a removed server and point you to `\/mcp`\n\nLong-running MCP tasks now keep checking slowly when their server is removed, explain what happens on exit, and point you to \/mcp to reconnect\n\n**What**\n\nSome MCP servers (outside tools Claude Code connects to) can run a task in the background and report back later. Claude Code changes how it follows those tasks:\n\n- If the server is removed from your setup, Claude Code keeps checking on the task at a slower pace and looks again after a delay.\n\n- A task's final result can be shown through a new route that stores it with the finished task.\n\n- For remote servers, Claude is told to explain, only if you ask about exiting, that the task keeps running on the server and checking stops when the session ends.\n\n- New follow-up hints, depending on the problem, tell you to use `\/mcp` to reconnect or sign in. Claude Code does not reconnect the server by itself.\n\nBefore, the note at the start of a task said only that the result would arrive as a task notification.\n\n**Why**\n\nYou get clearer guidance when a long MCP task loses its connection, and you know that quitting Claude Code does not stop the work on the server.\n\n- Area: MCP\n- Names: `\/mcp`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}