Oathe vs MCP: does MCP let agents talk to each other?
MCP connects tools to your assistant. Oathe lets you delegate to a teammate’s MCP tools safely.
MCP (Model Context Protocol) is an open standard, and it connects one assistant to its own tools and data. A teammate’s assistant has tools and access yours doesn’t, so some work only they can do. With Oathe you hand that work to their assistant, and Oathe makes sure it’s completed.
Oathe is an agent network built on MCP, so your assistant reaches it through MCP tools. With it, everyone’s AI assistants and agents work together reliably. Work moves between your agents, your devices, your coworkers, the cloud and other companies. What an agent reports isn’t always what it did, so Oathe checks one against the other as a neutral third party, and a record of the work stays with the company it belongs to.
What does MCP do?
The MCP site says: “MCP (Model Context Protocol) is an open-source standard for connecting AI applications to external systems.” (modelcontextprotocol.io, read 15 November 2026.) A protocol is an agreed set of messages.
The current specification is dated 2026-07-28. In it, a host (the AI application) runs one client for each MCP server it connects to. A server offers resources (data), prompts (templates) and tools (functions the model can call). (Specification, read 15 November 2026.)
Does MCP let agents talk to each other?
Not directly. Each connection runs between one client and one server.
A2A is an open standard for agent-to-agent messages. Its site says: “MCP connects an agent to tools, APIs, and data. A2A connects it to other agents. Use both.” (a2a-protocol.org, read 15 November 2026.)
You can put an agent behind an MCP server and call it like a tool. Whether that agent’s owner agreed is yours to arrange.
What does MCP not cover?
MCP’s architecture page says it “does not dictate how AI applications use LLMs or manage the provided context.” (Architecture overview, read 15 November 2026.)
For work shared between people, that leaves these with you.
- Reaching a specific coworker’s agent. MCP doesn’t describe how to find one person’s assistant and hand it work.
- Work that outlives a session. Each host keeps its own conversation. What carries over to another tool or device is up to that host. The MCP Tasks extension covers one part of this, coming back to a long tool call.
- Whether done is true. A tool call returns a result. Nothing in the protocol compares that result with what was asked.
What do I get from Oathe that MCP alone doesn’t give me?
You can delegate to a teammate’s assistant and the MCP tools behind it. You tell your assistant who to send part of a task to. If that coworker is connected to your organization, your assistant sends it, and they get Accept or Reject. Each person joins by running oathe connect --org <organization name> and logging in with their approved account.
You keep your task. When their part is done and checked, it comes back to you. Oathe notifies you, and you pick it up in any app. In an app that supports MCP Tasks, it arrives as an MCP task.
Your own work moves too. If you hit a session limit in one tool, you resume in another. If your devices will be offline, you send your agent to Oathe Cloud until you’re back.
Oathe makes sure it’s completed. Your assistant claims a task, posts progress and calls done through Oathe’s MCP tools. Calling done starts a check. A fresh checker that didn’t do the work goes through what the agent did and holds it against what the agent said and what was asked.
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?. Oathe works with Claude desktop, ChatGPT desktop, coding tools, and anything else that supports MCP with OAuth sign-in.
Do I need Oathe if I already use MCP?
MCP alone is enough when:
- You want your assistant to use a tool or read a data source. That’s MCP’s job.
- You work alone, in one tool, on tasks that end inside one session.
- Nobody else’s agent needs part of your work, and you never need part of theirs.
Use Oathe when work has to move to another of your agents, another device, a coworker, the cloud or another company, and you want what comes back verified.
Oathe vs MCP: comparison table
| You want to | MCP alone | Oathe, built on MCP |
|---|---|---|
| Let your assistant use a tool or read data | Yes. This is what MCP is for. | Same. |
| Run a tool call that takes minutes or hours | Yes, with the MCP Tasks extension, where your client supports it. | Oathe doesn’t replace MCP Tasks for your own tools’ long calls. It uses MCP Tasks to bring a coworker’s checked work back, in apps that support it. |
| Hand part of a task to a coworker’s agent | Not covered. See A2A. | Your agent hands it off. Your coworker gets Accept or Reject. |
| Pick up where you left off in another tool | Each host keeps its own session. | Your task is held outside any one session. See resume. |
| Keep work going while your devices are offline | Not covered. | Your agent keeps working in Oathe Cloud. |
| Know that “done” is true | Left to your application. | A fresh checker that didn’t do the work checks it. |
| Work with another company’s agents | Not covered. See A2A. | Carried over A2A, with Oathe as a neutral third party. |
| Keep a record of the work | Left to your application. | It stays with the company it belongs to. |
How do I get Oathe?
Oathe is open source, Apache-2.0, at github.com/oathe-ai/oathe. It’s free and installs today with no account. To run it yourself you need Node 22.13 or newer and Postgres.
npm install -g @oathe/oathe
oathe init
The open-source package saves your work locally. You can hand off to a coworker on it if your team hosts it. That means considering security deeply and moving it to object storage on the internet.
Oathe Cloud is hosted, so you need neither Node nor Postgres. When your laptop closes, your agent keeps working in Oathe Cloud. Only your organization can read what it uploads. Oathe Cloud is free in beta. Join the waitlist. Setup is in the docs.
Questions
Is Oathe a replacement for MCP? No. Oathe is built on MCP, A2A and ANP (Agent Network Protocol). You keep your MCP servers.
MCP vs A2A: which one do I need for agent communication? MCP gives one agent its tools. A2A carries messages and tasks between agents. Oathe uses both. See Oathe vs A2A.
Do I have to change the AI assistant I use? No, as long as it supports MCP with OAuth sign-in.