Claude Code MCP Tasks Enter Public Beta
Claude Code's MCP Tasks public beta lets compatible MCP servers run long jobs while the CLI continues working. It requires Claude Code v2.1.304 or later and a task-capable server and qualifying session. The desktop app and VS Code extension do not support Tasks. Existing MCP Elicitation can handle input requests from a task.
MCP Tasks are in public beta in the Claude Code CLI. A task-capable MCP server can accept a long-running job, let Claude continue working, and return the result when the job finishes. The feature requires Claude Code v2.1.304 or later, and each call must also meet the documented server and session conditions. (Claude Code MCP documentation)
What MCP Tasks change
An MCP Task is a long job that the server runs itself, such as a report export or build. Instead of waiting for the entire job, Claude Code's tool call returns when the server accepts it, so Claude can continue unless you ask it to wait. Claude Code tracks the task with the server, and the result is returned to Claude when the job ends. (Claude Code MCP documentation)
Remote-server tasks can keep running after Claude Code exits. A stdio server's process stops when Claude Code exits, so do not assume that its task will outlive the process unless that server's documentation says so. (Claude Code MCP documentation)
Availability and requirements
The public beta requires Claude Code v2.1.304 or later. The docs identify terminal CLI sessions, Agent SDK sessions, and GitHub Actions runs as supported session types on that version, while stating that the desktop app and VS Code extension do not have MCP Tasks. The listed session types do not make every call eligible. (Claude Code MCP documentation)
Each task call also requires a server that supports MCP Tasks and a supported connection on protocol revision 2026-07-28, feature-flag fetching, an enabled session, and a call from the main conversation rather than a subagent. The docs exclude third-party-provider sessions such as Amazon Bedrock and sessions with telemetry or flag fetching turned off. (Claude Code MCP documentation)
Non-interactive Agent SDK and claude -p runs using --input-format stream-json need CLAUDE_AUTO_BACKGROUND_TASKS=1, with CLAUDE_CODE_DISABLE_MCP_TASK_BACKGROUND not set to 1 and CLAUDE_CODE_MCP_AUTO_BACKGROUND_MS not set to 0. Keep the stream-json input open while a task runs; a one-shot claude -p command does not get MCP Tasks. (Claude Code MCP documentation)
How Elicitation fits in
An MCP task can request input through Elicitation, which presents a dialog in an interactive terminal session. If a task asks for input in a non-interactive session, Claude Code asks the server to cancel the task rather than prompting the user. The Elicitation hook can be used to respond automatically without showing a dialog. (Claude Code MCP documentation)
MCP Elicitation itself predates the MCP Tasks beta. The Claude Code changelog lists Elicitation support in v2.1.76, released March 14, 2026, allowing MCP servers to request structured input through an interactive dialog. (Claude Code changelog)
Sources
Read next
Related coverage- Claude
Claude Managed Agents Add Self-Hosted Sandboxes (Public Beta) and MCP Tunnels (Research Preview)
Anthropic says Claude Managed Agents can now run tool execution in a sandbox you control (public beta) and connect to private MCP servers via MCP tunnels (research preview). The update targets enterprise security requirements by keeping execution and private services within an organization's perimeter.
- Claude
MCP 2026-07-28 Moves to a Stateless Core as Claude Rolls Out Support
Anthropic says the MCP 2026-07-28 specification moves the Model Context Protocol from a bidirectional stateful design to a request/response model, adds versioned extensions for MCP Apps and Tasks, and aligns authorization with production OAuth 2.0 and OIDC deployments.
- Claude Code
Claude Code Sessions Can Now Message Each Other
Claude Code lets independent sessions discover and message one another. As of September 2026, a session can start a conversation with a session on the same machine, on another of your machines, or on Claude Code on the web; same-machine messaging works on macOS, Linux, WSL 2, and native Windows and on every provider. Messaging is on with nothing to enable, and incoming messages can be accepted, held, or refused per session.
- Claude
Claude Computer Use Runs in the Background in Cowork and Claude Code
Anthropic added computer use to Claude Cowork and Claude Code in the Claude Desktop app. Claude can click, type, open apps, and use dev tools while you keep working on macOS, with Windows support also documented. The beta is limited to Pro and Max plans and still requires the desktop app to be open and the computer awake.
Frequently Asked Questions
What are MCP Tasks in Claude Code?
MCP Tasks let a compatible MCP server run a long job and return control to Claude Code after the server accepts it. Claude can continue working and receive the task result later.
Which Claude Code sessions support MCP Tasks?
The public beta requires Claude Code v2.1.304 or later. The documentation names terminal CLI, Agent SDK, and GitHub Actions sessions, but a call also needs a task-capable server, the required protocol revision and feature flags, and an eligible session. The desktop app and VS Code extension do not support MCP Tasks.
Is MCP Elicitation new with the MCP Tasks beta?
No. The Claude Code changelog lists MCP Elicitation support in v2.1.76, released March 14, 2026. A task can use Elicitation to request input in an interactive terminal session.
Get an email when Claude Code changes its plans, prices or limits
We check every change against Claude Code's own pages before we send. You also get the weekly AI Catchup; one click unsubscribes.