Oathe vs MCP Tasks: what each one does
MCP Tasks lets your assistant wait on a long job from one of its own tools. Oathe lets you delegate work to a teammate’s assistant safely and makes sure it’s completed, and it comes back even in apps that don’t support Tasks.
MCP Tasks is an official MCP extension. A tool’s server returns a durable handle, an ID that still works after you reconnect, and your client polls it, which means it asks again until the result is ready.
Oathe is an agent network, and MCP Tasks is one of the standards it’s built on, with MCP, A2A and ANP. Your team’s AI assistants and agents work together reliably. Work moves between your agents, your devices, your coworkers, the cloud and other companies. A job reported as finished isn’t always finished, so Oathe checks each report against the work as a neutral third party, and your company keeps a record of the work.
What does MCP Tasks do?
The official overview says: “MCP Tasks let servers return a durable handle instead of blocking, so clients can poll for progress, provide input when needed, and retrieve the final result after reconnecting.” (Tasks overview, read 15 November 2026.)
Your client declares the extension, io.modelcontextprotocol/tasks. The server decides per request whether a call will run long. If so, it returns a taskId, the durable handle, in place of the result. The client polls with tasks/get until the task is completed, failed or cancelled. If the server needs something from you, the task moves to input_required and the client answers with tasks/update.
Tasks first shipped as experimental in the 2025-11-25 specification, with tasks/result and tasks/list (2025-11-25 spec page, read 15 November 2026). The current overview has neither. The 2026-07-28 release moved Tasks into the io.modelcontextprotocol/tasks extension (MCP blog, read 15 November 2026).
Which MCP clients support Tasks?
Checked on 15 November 2026.
| Client | Tasks support | Source |
|---|---|---|
| Official client matrix | The Tasks column is empty for all 17 clients, Claude desktop and ChatGPT included. The list is community-maintained, so an empty cell may only mean nobody updated it. | Client matrix |
| Claude Code | The v2.1.319 release notes (6 November 2026) list “support for MCP tasks in the terminal”. | Release v2.1.319 |
| Codex | A feature request opened 27 September 2026 is still open. | openai/codex issue 48617 |
| Cursor | Its MCP documentation doesn’t mention tasks. | Cursor MCP docs |
What does MCP Tasks leave to you?
The extension covers one long call between one client and one server. These are left to you.
- What
completedmeans. The lifecycle table says: “The operation finished. Theresultfield contains the final output.” That doesn’t mean the output is what you asked for. - Keeping the handle. The overview tells clients to “Store task IDs durably.” No method lists your tasks. A contributor on the extension’s tracker said “There is deliberately no recovery by enumeration”, so a server can’t leak one caller’s tasks to another. (ext-tasks issue 11, read 15 November 2026.)
- Work between people. A task is reached by its
taskId. Handing work to a coworker’s agent isn’t part of the extension.
What do I get from Oathe that MCP Tasks alone doesn’t give me?
A teammate’s assistant has tools and access yours doesn’t. You can hand part of a task to it and keep your own task. When their agent calls done, that starts a check. A fresh checker that didn’t do the work reads what their agent did and compares it with what the agent said and what you asked for.
In an app with MCP Tasks, their part arrives as an MCP task. The MCP task shows completed only after Oathe’s check passes.
If a check fails on your machine, you can send the work back to your coworker with what they need to fix, or fix it yourself. If your coworker rejects the handoff, Oathe shows it to you, and you decide what to do with it or how to change it.
Everyone already has an agent. Oathe is a way for them to work together. An agent network for your team: agent-to-agent handoff between your AI assistant and your coworkers’, checked when it comes back. See What is an agent network?.
What if my app doesn’t support MCP Tasks?
Checked work comes back to you in any app.
- Oathe notifies you when a task is ready to resume, and sends a push notification.
- You click continue in Oathe. A message is copied.
- You paste that message into your session.
- Your agent uses Oathe’s MCP tools to pick the task up and resume it.
When do I not need Oathe?
MCP Tasks alone is enough when:
- You’re building an MCP server around a slow job, such as a CI pipeline. Return a task.
- Your problem is a tool call timing out. Tasks fixes that.
Oathe vs MCP Tasks: comparison table
| You want to | MCP Tasks alone | Oathe, built on MCP Tasks |
|---|---|---|
| Keep a long tool call alive past a timeout | Yes. | No. Use Tasks. |
| Hand part of a job to a coworker’s agent | Not covered. | Your coworker gets Accept or Reject. Their checked part comes back to you. |
| Get work back in an app without Tasks | No. The client has to support the extension. | Oathe notifies you and you click continue, in any app. |
Know that completed means correct | No. It means the operation finished. | The MCP task shows completed only after Oathe’s check passes. |
| Move work between apps, devices and the cloud | Not covered. | Yes. Devices and the cloud need Oathe Cloud. |
| Find work again after losing the ID | No. There’s no tasks/list, by design. | Oathe shows you all the work you delegated and all the work you’re waiting on. |
How do I try Oathe?
Oathe is open source, free, and installs today with no account.
npm install -g @oathe/oathe
oathe init
Running it yourself takes Node 22.13 or newer and Postgres. Oathe Cloud needs neither, and it’s free in beta. Only your organization can read what Oathe Cloud uploads, and it’s encrypted on your machine first.
For coworker handoff on the open-source package alone, your team hosts it, and you’ll need to consider security deeply and move it to object storage on the internet. Join the waitlist. Setup is in the docs.
Questions
What are MCP Tasks?
An official, opt-in MCP extension. A server answers a slow request with a durable handle, and the client polls it with tasks/get.
Is an MCP task the same as an Oathe task? No. An MCP task is a durable handle for one long call. An Oathe task is a piece of work that can move between your agents, your devices, your coworkers and the cloud, and it’s verified before it counts as done.