an open-source alternative to the dots, bots and muses of the world, run an office of claude code/codex like agents on your laptop, sandboxes or anywhere, uses your existing subscriptions
HTML agent-harnessagent-orchestrationagentsai-agentsautonomous-agentsclaude-codecodexcoding-agentsdesktop-appdeveloper-toolselectrongemini-cliharnessharness-engineeringlocal-firstmemorymulti-agentopencodeorchestrationtypescript
blog: when-do-agents-need-an-agent-protocol (73 → 74)
Chaitanya Giric2699c735fb7
diff --git a/blog/src/posts/when-do-agents-need-an-agent-protocol.md b/blog/src/posts/when-do-agents-need-an-agent-protocol.mdnew file mode 100644index 00000000..610562e5--- /dev/null+++ b/blog/src/posts/when-do-agents-need-an-agent-protocol.md@@ -0,0 +1,136 @@+---+title: "When Do AI Agents Actually Need an Agent Protocol?"+description: "When do AI agents need a protocol like MCP or A2A? Agents you own coordinate fine with file mailboxes; protocols earn their keep across boundaries."+date: 2026-06-04+category: concepts+categoryLabel: Concepts+type: Technical+primaryKeyword: "ai agent protocols"+secondaryKeywords: ["agent2agent a2a", "model context protocol", "do agents need a2a"]+tags: ["Concepts", "Multi-Agent", "Internals", "Interoperability"]+author:+ name: Chaitanya Giri+ initials: CG+faq:+ - q: "Do all multi-agent systems need an agent protocol like A2A?"+ a: "No. Agent protocols standardize collaboration across boundaries — different vendors, frameworks, or organizations. If your agents are co-located, built on one framework, and owned by you, simpler in-house coordination like file mailboxes is usually faster, fully auditable, and protocol-free. You reach for a standard protocol when you cross a boundary."+ - q: "What's the difference between MCP and A2A?"+ a: "MCP (Model Context Protocol) standardizes how an agent connects to external tools and data. A2A (Agent2Agent) standardizes how separate agents discover one another and collaborate. Both are open standards now under the Linux Foundation. MCP is about reach to tools; A2A is about reach to other agents."+ - q: "When is an agent protocol worth the complexity?"+ a: "When you cross a trust, vendor, or framework boundary: exposing your agent for others to call, consuming a third party's agent, or coordinating agents built on different stacks over a network you don't fully control. Inside one owned, co-located hive, the protocol is usually overhead you don't need yet."+---++<div class="callout tldr"><span class="ic">TL;DR</span><p>Open <strong>agent protocols</strong> — MCP+(agent-to-tools) and A2A (agent-to-agent), both now under the Linux Foundation — are powerful, but not+every multi-agent system needs them. The dividing line is a <strong>boundary</strong>: agents you own,+on one framework, on one machine can coordinate with simple <strong>file mailboxes</strong> — faster,+fully auditable, zero protocol overhead. You reach for a standard protocol when you <em>cross</em> a+boundary: another org's agents, another vendor's framework, a network you don't control. Use the+boundary test before adding the complexity.</p></div>++2025 and 2026 gave the agent world real plumbing: open protocols for how agents talk to tools and to+each other, with vendor-neutral governance behind them. That's genuinely good news. It also prompts a+fair question for anyone building a multi-agent system: *do I need to adopt these?* The honest answer is+often "not yet" — and knowing when you do is worth more than adopting on reflex. Here's the dividing+line.++## What an agent protocol actually buys you++Two open standards do most of the work, and they solve different problems:++- **MCP (the Model Context Protocol)** standardizes how an agent reaches **tools and data**. Anthropic+ introduced it and [donated it to the Agentic AI Foundation under the Linux+ Foundation](https://www.anthropic.com/news/donating-the-model-context-protocol-and-establishing-of-the-agentic-ai-foundation)+ in December 2025.+- **A2A (Agent2Agent)** standardizes how separate **agents** discover each other and collaborate across+ frameworks and vendors. Google created it and [donated it to the Linux+ Foundation](https://www.linuxfoundation.org/press/linux-foundation-launches-the-agent2agent-protocol-project-to-enable-secure-intelligent-communication-between-ai-agents),+ which launched the project in mid-2025.++Notice the shared word in both pitches: **across**. The value a protocol adds is interoperability across+something — across tool vendors, across agent frameworks, across organizations. That's the lens for+deciding whether you need one.++## When you don't need one: the co-located hive++If your agents are **yours** — same framework, same machine, one team's control — a standardized agent+protocol is usually solving a problem you don't have. Inside [a local-first+hive](/blog/local-first-ai-agent-orchestration/), agents coordinate through+[file-based mailboxes](/blog/atomic-file-mailboxes-for-agents/): each writes a message to its outbox, a+router delivers it to the recipient's inbox, and the whole exchange is durable and auditable because+it's just files. There's no discovery problem (you know every agent), no cross-vendor envelope to+negotiate, no network in the middle.++For that setup, the in-house approach actually *wins* on the things that matter: it's lower latency+(local file operations, no protocol handshakes), simpler to debug (read the files), and fully under your+audit. Adopting A2A to let two agents in the same process "discover" each other would be ceremony around+a problem you've already solved. This is the same reason [coordinating co-located+agents](/blog/coordinating-ai-coding-agents/) rarely starts with a protocol — it starts with a shared+directory.++## When you do need one: crossing a boundary++The calculus flips the moment your agents stop being a closed, owned set. A protocol earns its keep when+you cross a **boundary**:++- **A vendor or framework boundary** — your agent needs to collaborate with an agent built on a+ different stack. A2A gives them a shared language instead of a bespoke integration per pair.+- **An organizational boundary** — you want to expose an agent for other teams or companies to call, or+ consume someone else's agent. Discovery and a standard envelope stop mattering when there's only one+ of you; they're essential when there are many.+- **A tool boundary** — your agent needs capabilities you didn't build. That's MCP's job, and it's worth+ adopting early because tools are exactly where you *want* to reach outside your own code. (In a hive,+ you can [bring MCP servers and skills in](/blog/mcp-and-skills-in-a-hive/) without exposing anything+ else.)++The pattern: protocols are for reach beyond what you own. Inside what you own, simpler coordination is+both sufficient and better.++## The boundary test++Here's the heuristic, in one question: **are the agents on the same side of a trust-and-framework+boundary?**++- **Same side** (you built them, same stack, you can see them all) → in-house coordination — file+ mailboxes, a shared log, direct calls — is enough. Don't add a protocol yet.+- **Different sides** (other vendors, other orgs, a network you don't control) → adopt the standard.+ A2A for agent-to-agent reach, MCP for tool reach.++A concrete example makes the line obvious. A hive of agents reviewing *your own* codebase never needs+A2A — they share a directory and a router, and discovery is meaningless when you already know every+agent. But the moment you want that hive to hand a task to a partner company's compliance agent, or to+call a vendor's specialized research agent, you've crossed an organizational boundary — and a shared+protocol is what spares you a brittle, bespoke integration for every partner you add.++Most teams' first multi-agent system lives entirely on the "same side." Reach for the protocol when, and+only when, you actually cross over — and notice the two boundaries can differ: you might want MCP for+tools long before you ever need A2A for agents.++## Build so you can speak them later++None of this is an argument against the protocols — it's an argument against adopting them prematurely.+The healthy position is to keep your coordination simple while it's internal, and design so you *can*+speak the open standards when a boundary appears. That's the same "open protocols, local control plane"+idea behind [local-first vs cloud agent SDKs](/blog/local-first-vs-cloud-agent-sdks/): keep the core+local and simple, reach outward through standards when there's a real outside to reach. Adopting a+protocol should be a response to a boundary, not a default.++## FAQ++**Do all multi-agent systems need a protocol like A2A?** No — co-located agents you own can coordinate+with file mailboxes. Protocols matter when you cross a vendor, framework, or organizational boundary.++**MCP vs A2A?** MCP connects an agent to tools and data; A2A lets separate agents discover and+collaborate. Both are open standards under the Linux Foundation.++**When is the protocol worth it?** When you expose your agent to others, consume a third party's agent,+or coordinate across different stacks and networks — i.e., when you cross a boundary.++---++Munder Difflin takes the "same side" path: a [local hive whose agents coordinate through file+mailboxes](https://munderdiffl.in/#how), simple and auditable, free to speak open protocols outward when+a boundary appears. [Download Munder Difflin](https://munderdiffl.in/#install) to run a coordinated team+of agents without protocol ceremony; it's free and open source.++*Sources: [Anthropic — donating MCP to the Agentic AI Foundation](https://www.anthropic.com/news/donating-the-model-context-protocol-and-establishing-of-the-agentic-ai-foundation); [Linux Foundation — Agent2Agent protocol project](https://www.linuxfoundation.org/press/linux-foundation-launches-the-agent2agent-protocol-project-to-enable-secure-intelligent-communication-between-ai-agents).*diff --git a/docs/blog/building-a-terminal-ui-xterm-node-pty/index.html b/docs/blog/building-a-terminal-ui-xterm-node-pty/index.htmlindex 670c283c..f2cec0c4 100644--- a/docs/blog/building-a-terminal-ui-xterm-node-pty/index.html+++ b/docs/blog/building-a-terminal-ui-xterm-node-pty/index.html@@ -338,7 +338,7 @@ to watch many real terminals at once; it’s free and open source.</p><footer class="post-foot wrap"><div class="prevnext"><a class="pn prev" href="/blog/building-an-ai-office-floor/"><span class="k">← Older</span><span class="t">Building an AI "Office Floor": Avatars, Pathfinding, Envelopes</span></a>- <a class="pn next" href="/blog/whats-new-in-agentic-ai-june-2026/"><span class="k">Newer →</span><span class="t">What's New in Agentic AI: A June 2026 Field Guide</span></a>+ <a class="pn next" href="/blog/when-do-agents-need-an-agent-protocol/"><span class="k">Newer →</span><span class="t">When Do AI Agents Actually Need an Agent Protocol?</span></a></div><section class="related"><h2>Related in Internals</h2>diff --git a/docs/blog/feed.xml b/docs/blog/feed.xmlindex 14d1d265..f58558af 100644--- a/docs/blog/feed.xml+++ b/docs/blog/feed.xml@@ -319,6 +319,14 @@<updated>2026-06-04T00:00:00.000Z</updated><category term="Guides" /><summary>A grounded June 2026 roundup of agentic AI: Claude Opus 4.8, the MCP and A2A protocol layer, usage-based agent billing, and agent governance.</summary></entry>+ <entry>+ <title>When Do AI Agents Actually Need an Agent Protocol?</title>+ <link href="https://munderdiffl.in/blog/when-do-agents-need-an-agent-protocol/" />+ <id>https://munderdiffl.in/blog/when-do-agents-need-an-agent-protocol/</id>+ <published>2026-06-04T00:00:00.000Z</published>+ <updated>2026-06-04T00:00:00.000Z</updated><category term="Concepts" />+ <summary>When do AI agents need a protocol like MCP or A2A? Agents you own coordinate fine with file mailboxes; protocols earn their keep across boundaries.</summary>+ </entry><entry><title>Building a Terminal UI with xterm.js and node-pty</title><link href="https://munderdiffl.in/blog/building-a-terminal-ui-xterm-node-pty/" />@@ -479,12 +487,4 @@<updated>2026-06-02T00:00:00.000Z</updated><category term="Use Cases" /><summary>The control, privacy, and cost case for keeping your AI agents and their memory on your own machine — and what cloud orchestration quietly costs.</summary></entry>- <entry>- <title>Why We Built Munder Difflin</title>- <link href="https://munderdiffl.in/blog/why-we-built-munder-difflin/" />- <id>https://munderdiffl.in/blog/why-we-built-munder-difflin/</id>- <published>2026-06-02T00:00:00.000Z</published>- <updated>2026-06-02T00:00:00.000Z</updated><category term="Story" />- <summary>The origin story of Munder Difflin — how the pain of juggling Claude Code terminals led to a coordinated, memory-backed hive of agents you can watch.</summary>- </entry></feed>diff --git a/docs/blog/index.html b/docs/blog/index.htmlindex dbd5c855..449dfd37 100644--- a/docs/blog/index.html+++ b/docs/blog/index.html@@ -85,13 +85,13 @@building a self-coordinating hive of agents with a GOD orchestrator you talk to.</p><div class="filters" role="navigation" aria-label="Topics">- <a class="chip" aria-current="page">All<span class="ct">73</span></a>+ <a class="chip" aria-current="page">All<span class="ct">74</span></a><a class="chip" href="/blog/topics/guides/">guides<span class="ct">19</span></a><a class="chip" href="/blog/topics/internals/">internals<span class="ct">14</span></a>- <a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">12</span></a>+ <a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">13</span></a><a class="chip" href="/blog/topics/comparisons/">comparisons<span class="ct">10</span></a>@@ -815,6 +815,24 @@</div></div></article>+<article class="card">+ <a class="thumb t-concepts" href="/blog/when-do-agents-need-an-agent-protocol/" aria-hidden="true" tabindex="-1">+ <span>CONCEPTS</span>+ </a>+ <div class="body">+ <div class="meta">+ <time datetime="2026-06-04">Jun 4, 2026</time>+ <span class="dot" aria-hidden="true"></span>+ <span>5 min</span>+ </div>+ <h3><a href="/blog/when-do-agents-need-an-agent-protocol/">When Do AI Agents Actually Need an Agent Protocol?</a></h3>+ <p class="dek">When do AI agents need a protocol like MCP or A2A? Agents you own coordinate fine with file mailboxes; protocols earn their keep across boundaries.</p>+ <div class="foot">+ <span class="tag kind">Concepts</span>+ <a class="more" href="/blog/when-do-agents-need-an-agent-protocol/" aria-label="Read: When Do AI Agents Actually Need an Agent Protocol?">Read →</a>+ </div>+ </div>+</article><article class="card"><a class="thumb t-internals" href="/blog/building-a-terminal-ui-xterm-node-pty/" aria-hidden="true" tabindex="-1"><span>INTERNALS</span>diff --git a/docs/blog/tags/concepts/index.html b/docs/blog/tags/concepts/index.htmlindex 13005b9d..b3d58c8e 100644--- a/docs/blog/tags/concepts/index.html+++ b/docs/blog/tags/concepts/index.html@@ -58,7 +58,7 @@<header class="page-head wrap"><p class="eyebrow">Tag</p><h1>#Concepts</h1>- <p class="lead">9 posts tagged <strong>Concepts</strong>.</p>+ <p class="lead">10 posts tagged <strong>Concepts</strong>.</p></header><section class="wrap"><div class="post-grid">@@ -152,6 +152,24 @@</div></div></article>+<article class="card">+ <a class="thumb t-concepts" href="/blog/when-do-agents-need-an-agent-protocol/" aria-hidden="true" tabindex="-1">+ <span>CONCEPTS</span>+ </a>+ <div class="body">+ <div class="meta">+ <time datetime="2026-06-04">Jun 4, 2026</time>+ <span class="dot" aria-hidden="true"></span>+ <span>5 min</span>+ </div>+ <h3><a href="/blog/when-do-agents-need-an-agent-protocol/">When Do AI Agents Actually Need an Agent Protocol?</a></h3>+ <p class="dek">When do AI agents need a protocol like MCP or A2A? Agents you own coordinate fine with file mailboxes; protocols earn their keep across boundaries.</p>+ <div class="foot">+ <span class="tag kind">Concepts</span>+ <a class="more" href="/blog/when-do-agents-need-an-agent-protocol/" aria-label="Read: When Do AI Agents Actually Need an Agent Protocol?">Read →</a>+ </div>+ </div>+</article><article class="card"><a class="thumb t-concepts" href="/blog/ai-agent-glossary/" aria-hidden="true" tabindex="-1"><span>CONCEPTS</span>diff --git a/docs/blog/tags/internals/index.html b/docs/blog/tags/internals/index.htmlindex c81386fe..c89b63b3 100644--- a/docs/blog/tags/internals/index.html+++ b/docs/blog/tags/internals/index.html@@ -58,7 +58,7 @@<header class="page-head wrap"><p class="eyebrow">Tag</p><h1>#Internals</h1>- <p class="lead">19 posts tagged <strong>Internals</strong>.</p>+ <p class="lead">20 posts tagged <strong>Internals</strong>.</p></header><section class="wrap"><div class="post-grid">@@ -224,6 +224,24 @@</div></div></article>+<article class="card">+ <a class="thumb t-concepts" href="/blog/when-do-agents-need-an-agent-protocol/" aria-hidden="true" tabindex="-1">+ <span>CONCEPTS</span>+ </a>+ <div class="body">+ <div class="meta">+ <time datetime="2026-06-04">Jun 4, 2026</time>+ <span class="dot" aria-hidden="true"></span>+ <span>5 min</span>+ </div>+ <h3><a href="/blog/when-do-agents-need-an-agent-protocol/">When Do AI Agents Actually Need an Agent Protocol?</a></h3>+ <p class="dek">When do AI agents need a protocol like MCP or A2A? Agents you own coordinate fine with file mailboxes; protocols earn their keep across boundaries.</p>+ <div class="foot">+ <span class="tag kind">Concepts</span>+ <a class="more" href="/blog/when-do-agents-need-an-agent-protocol/" aria-label="Read: When Do AI Agents Actually Need an Agent Protocol?">Read →</a>+ </div>+ </div>+</article><article class="card"><a class="thumb t-internals" href="/blog/building-a-terminal-ui-xterm-node-pty/" aria-hidden="true" tabindex="-1"><span>INTERNALS</span>diff --git a/docs/blog/tags/interoperability/index.html b/docs/blog/tags/interoperability/index.htmlnew file mode 100644index 00000000..dc3039c3--- /dev/null+++ b/docs/blog/tags/interoperability/index.html@@ -0,0 +1,124 @@+<!doctype html>+<html lang="en">+<head>+<meta charset="UTF-8" />+<meta name="viewport" content="width=device-width, initial-scale=1.0" />+<title>Interoperability — Munder Difflin Blog</title>+<meta name="description" content="Munder Difflin blog posts tagged Interoperability." />+<link rel="canonical" href="https://munderdiffl.in/blog/tags/interoperability/" />++<link rel="icon" type="image/png" href="https://munderdiffl.in/logo.png" />+<link rel="apple-touch-icon" href="https://munderdiffl.in/logo.png" />+<meta name="theme-color" content="#F5F2E8" />++<!-- Open Graph -->+<meta property="og:site_name" content="Munder Difflin Blog" />+<meta property="og:type" content="website" />+<meta property="og:title" content="Interoperability — Munder Difflin Blog" />+<meta property="og:description" content="Munder Difflin blog posts tagged Interoperability." />+<meta property="og:url" content="https://munderdiffl.in/blog/tags/interoperability/" />+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />+<meta property="og:locale" content="en_US" />+++<!-- Twitter -->+<meta name="twitter:card" content="summary_large_image" />+<meta name="twitter:title" content="Interoperability — Munder Difflin Blog" />+<meta name="twitter:description" content="Munder Difflin blog posts tagged Interoperability." />+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />++<link rel="alternate" type="application/atom+xml" title="Munder Difflin Blog" href="https://munderdiffl.in/blog/feed.xml" />+<link rel="preconnect" href="https://fonts.googleapis.com" />+<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />+<link href="https://fonts.googleapis.com/css2?family=Geist:wght@400;500;600&family=JetBrains+Mono:wght@400;500;600;700&display=swap" rel="stylesheet" />+<link rel="stylesheet" href="/blog/assets/blog.css" />++</head>+<body>+<a class="skip-link" href="#main">Skip to content</a>+<nav id="nav">+ <a class="brand" href="/blog/" aria-label="Munder Difflin Blog home">+ <span class="brand-mark">MD</span>+ <span class="brand-word">MUNDER DIFFLIN<span class="sep">/</span><span class="blog">BLOG</span></span>+ </a>+ <span class="spacer"></span>+ <div class="links">+ <a href="/blog/">Latest</a>+ <a href="/blog/topics/">Topics</a>+ <a href="/blog/about/">About</a>+ <a href="https://munderdiffl.in">↗ Product</a>+ </div>+ <div class="nav-actions">+ <a class="btn sm" href="https://munderdiffl.in/blog/feed.xml" aria-label="RSS feed">⤵ RSS</a>+ <a class="btn sm primary" href="https://munderdiffl.in/#install">⤓ Download</a>+ </div>+</nav>++<main id="main">+<header class="page-head wrap">+ <p class="eyebrow">Tag</p>+ <h1>#Interoperability</h1>+ <p class="lead">1 post tagged <strong>Interoperability</strong>.</p>+</header>+<section class="wrap">+ <div class="post-grid">+ <article class="card">+ <a class="thumb t-concepts" href="/blog/when-do-agents-need-an-agent-protocol/" aria-hidden="true" tabindex="-1">+ <span>CONCEPTS</span>+ </a>+ <div class="body">+ <div class="meta">+ <time datetime="2026-06-04">Jun 4, 2026</time>+ <span class="dot" aria-hidden="true"></span>+ <span>5 min</span>+ </div>+ <h3><a href="/blog/when-do-agents-need-an-agent-protocol/">When Do AI Agents Actually Need an Agent Protocol?</a></h3>+ <p class="dek">When do AI agents need a protocol like MCP or A2A? Agents you own coordinate fine with file mailboxes; protocols earn their keep across boundaries.</p>+ <div class="foot">+ <span class="tag kind">Concepts</span>+ <a class="more" href="/blog/when-do-agents-need-an-agent-protocol/" aria-label="Read: When Do AI Agents Actually Need an Agent Protocol?">Read →</a>+ </div>+ </div>+</article>++ </div>+</section>+++</main>+<footer>+ <div class="wrap">+ <div class="foot-top">+ <a class="foot-brand brand" href="/blog/">+ <span class="brand-mark">MD</span>+ <span class="brand-word">MUNDER DIFFLIN<span class="sep">/</span><span class="blog">BLOG</span></span>+ </a>+ <div class="foot-links">+ <a href="/blog/">Latest</a>+ <a href="/blog/topics/">Topics</a>+ <a href="/blog/about/">About</a>+ <a href="https://munderdiffl.in/blog/feed.xml">RSS</a>+ <a href="https://github.com/chaitanyagiri/munder-difflin">GitHub</a>+ <a href="https://munderdiffl.in">munderdiffl.in ↗</a>+ </div>+ </div>+ <div class="foot-meta">+ © 2026 Munder Difflin · Local-first · MIT-licensed ·+ Built on <a href="https://munderdiffl.in">Electron, React, Pixi.js, xterm.js & node-pty</a>.+ Run an office of agents while you sleep.+ </div>+ </div>+</footer>++<script>+ // sticky-nav border on scroll+ (function () {+ var nav = document.getElementById('nav');+ if (!nav) return;+ var onScroll = function () { nav.classList.toggle('scrolled', window.scrollY > 8); };+ onScroll(); window.addEventListener('scroll', onScroll, { passive: true });+ })();+</script>++</body>+</html>diff --git a/docs/blog/tags/multi-agent/index.html b/docs/blog/tags/multi-agent/index.htmlindex 7c00bb4a..c3969f74 100644--- a/docs/blog/tags/multi-agent/index.html+++ b/docs/blog/tags/multi-agent/index.html@@ -58,7 +58,7 @@<header class="page-head wrap"><p class="eyebrow">Tag</p><h1>#Multi-Agent</h1>- <p class="lead">49 posts tagged <strong>Multi-Agent</strong>.</p>+ <p class="lead">50 posts tagged <strong>Multi-Agent</strong>.</p></header><section class="wrap"><div class="post-grid">@@ -512,6 +512,24 @@</div></div></article>+<article class="card">+ <a class="thumb t-concepts" href="/blog/when-do-agents-need-an-agent-protocol/" aria-hidden="true" tabindex="-1">+ <span>CONCEPTS</span>+ </a>+ <div class="body">+ <div class="meta">+ <time datetime="2026-06-04">Jun 4, 2026</time>+ <span class="dot" aria-hidden="true"></span>+ <span>5 min</span>+ </div>+ <h3><a href="/blog/when-do-agents-need-an-agent-protocol/">When Do AI Agents Actually Need an Agent Protocol?</a></h3>+ <p class="dek">When do AI agents need a protocol like MCP or A2A? Agents you own coordinate fine with file mailboxes; protocols earn their keep across boundaries.</p>+ <div class="foot">+ <span class="tag kind">Concepts</span>+ <a class="more" href="/blog/when-do-agents-need-an-agent-protocol/" aria-label="Read: When Do AI Agents Actually Need an Agent Protocol?">Read →</a>+ </div>+ </div>+</article><article class="card"><a class="thumb t-comparisons" href="/blog/claude-squad-alternative/" aria-hidden="true" tabindex="-1"><span>COMPARISONS</span>diff --git a/docs/blog/topics/comparisons/index.html b/docs/blog/topics/comparisons/index.htmlindex bdadab1b..9ded279a 100644--- a/docs/blog/topics/comparisons/index.html+++ b/docs/blog/topics/comparisons/index.html@@ -72,7 +72,7 @@<a class="chip" href="/blog/topics/internals/">internals<span class="ct">14</span></a>- <a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">12</span></a>+ <a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">13</span></a><a class="chip" href="/blog/topics/comparisons/" aria-current="page">comparisons<span class="ct">10</span></a>diff --git a/docs/blog/topics/concepts/index.html b/docs/blog/topics/concepts/index.htmlindex 4030672c..dc8c0833 100644--- a/docs/blog/topics/concepts/index.html+++ b/docs/blog/topics/concepts/index.html@@ -63,7 +63,7 @@</nav><p class="eyebrow">Topic</p><h1>concepts</h1>- <p class="lead">12 posts in this cluster.</p>+ <p class="lead">13 posts in this cluster.</p><div class="filters" role="navigation" aria-label="Topics"><a class="chip" href="/blog/">All</a>@@ -72,7 +72,7 @@<a class="chip" href="/blog/topics/internals/">internals<span class="ct">14</span></a>- <a class="chip" href="/blog/topics/concepts/" aria-current="page">concepts<span class="ct">12</span></a>+ <a class="chip" href="/blog/topics/concepts/" aria-current="page">concepts<span class="ct">13</span></a><a class="chip" href="/blog/topics/comparisons/">comparisons<span class="ct">10</span></a>@@ -233,6 +233,24 @@</div></div></article>+<article class="card">+ <a class="thumb t-concepts" href="/blog/when-do-agents-need-an-agent-protocol/" aria-hidden="true" tabindex="-1">+ <span>CONCEPTS</span>+ </a>+ <div class="body">+ <div class="meta">+ <time datetime="2026-06-04">Jun 4, 2026</time>+ <span class="dot" aria-hidden="true"></span>+ <span>5 min</span>+ </div>+ <h3><a href="/blog/when-do-agents-need-an-agent-protocol/">When Do AI Agents Actually Need an Agent Protocol?</a></h3>+ <p class="dek">When do AI agents need a protocol like MCP or A2A? Agents you own coordinate fine with file mailboxes; protocols earn their keep across boundaries.</p>+ <div class="foot">+ <span class="tag kind">Concepts</span>+ <a class="more" href="/blog/when-do-agents-need-an-agent-protocol/" aria-label="Read: When Do AI Agents Actually Need an Agent Protocol?">Read →</a>+ </div>+ </div>+</article><article class="card"><a class="thumb t-concepts" href="/blog/ai-agent-glossary/" aria-hidden="true" tabindex="-1"><span>CONCEPTS</span>diff --git a/docs/blog/topics/guides/index.html b/docs/blog/topics/guides/index.htmlindex b6ab35dc..d9525b5a 100644--- a/docs/blog/topics/guides/index.html+++ b/docs/blog/topics/guides/index.html@@ -72,7 +72,7 @@<a class="chip" href="/blog/topics/internals/">internals<span class="ct">14</span></a>- <a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">12</span></a>+ <a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">13</span></a><a class="chip" href="/blog/topics/comparisons/">comparisons<span class="ct">10</span></a>diff --git a/docs/blog/topics/index.html b/docs/blog/topics/index.htmlindex 2176bc5d..0f6dbf41 100644--- a/docs/blog/topics/index.html+++ b/docs/blog/topics/index.html@@ -88,7 +88,7 @@<span class="thumb t-concepts" aria-hidden="true">CONCEPTS</span><div class="body"><h3 style="color:var(--ink)">concepts</h3>- <p class="dek">12 posts.</p>+ <p class="dek">13 posts.</p><div class="foot"><span class="more">View topic →</span></div></div></a>@@ -144,19 +144,19 @@<div class="filters" style="padding-top:36px"><span class="eyebrow" style="align-self:center">Tags</span>- <a class="chip" href="/blog/tags/multi-agent/">Multi-Agent<span class="ct">49</span></a>+ <a class="chip" href="/blog/tags/multi-agent/">Multi-Agent<span class="ct">50</span></a><a class="chip" href="/blog/tags/claude-code/">Claude Code<span class="ct">36</span></a>- <a class="chip" href="/blog/tags/internals/">Internals<span class="ct">19</span></a>+ <a class="chip" href="/blog/tags/internals/">Internals<span class="ct">20</span></a><a class="chip" href="/blog/tags/orchestration/">Orchestration<span class="ct">12</span></a><a class="chip" href="/blog/tags/guides/">Guides<span class="ct">11</span></a>- <a class="chip" href="/blog/tags/comparisons/">Comparisons<span class="ct">10</span></a>+ <a class="chip" href="/blog/tags/concepts/">Concepts<span class="ct">10</span></a>- <a class="chip" href="/blog/tags/concepts/">Concepts<span class="ct">9</span></a>+ <a class="chip" href="/blog/tags/comparisons/">Comparisons<span class="ct">10</span></a><a class="chip" href="/blog/tags/tools/">Tools<span class="ct">8</span></a>@@ -288,6 +288,8 @@<a class="chip" href="/blog/tags/protocols/">Protocols<span class="ct">1</span></a>+ <a class="chip" href="/blog/tags/interoperability/">Interoperability<span class="ct">1</span></a>+<a class="chip" href="/blog/tags/geo/">GEO<span class="ct">1</span></a><a class="chip" href="/blog/tags/tutorial/">Tutorial<span class="ct">1</span></a>diff --git a/docs/blog/topics/internals/index.html b/docs/blog/topics/internals/index.htmlindex d2d4b973..dea0a760 100644--- a/docs/blog/topics/internals/index.html+++ b/docs/blog/topics/internals/index.html@@ -72,7 +72,7 @@<a class="chip" href="/blog/topics/internals/" aria-current="page">internals<span class="ct">14</span></a>- <a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">12</span></a>+ <a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">13</span></a><a class="chip" href="/blog/topics/comparisons/">comparisons<span class="ct">10</span></a>diff --git a/docs/blog/topics/memory/index.html b/docs/blog/topics/memory/index.htmlindex 9b34d2ca..deeec8f0 100644--- a/docs/blog/topics/memory/index.html+++ b/docs/blog/topics/memory/index.html@@ -72,7 +72,7 @@<a class="chip" href="/blog/topics/internals/">internals<span class="ct">14</span></a>- <a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">12</span></a>+ <a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">13</span></a><a class="chip" href="/blog/topics/comparisons/">comparisons<span class="ct">10</span></a>diff --git a/docs/blog/topics/orchestration/index.html b/docs/blog/topics/orchestration/index.htmlindex 6e481fef..463399b7 100644--- a/docs/blog/topics/orchestration/index.html+++ b/docs/blog/topics/orchestration/index.html@@ -72,7 +72,7 @@<a class="chip" href="/blog/topics/internals/">internals<span class="ct">14</span></a>- <a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">12</span></a>+ <a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">13</span></a><a class="chip" href="/blog/topics/comparisons/">comparisons<span class="ct">10</span></a>diff --git a/docs/blog/topics/story/index.html b/docs/blog/topics/story/index.htmlindex 64d0b4ba..cc0df7d8 100644--- a/docs/blog/topics/story/index.html+++ b/docs/blog/topics/story/index.html@@ -72,7 +72,7 @@<a class="chip" href="/blog/topics/internals/">internals<span class="ct">14</span></a>- <a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">12</span></a>+ <a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">13</span></a><a class="chip" href="/blog/topics/comparisons/">comparisons<span class="ct">10</span></a>diff --git a/docs/blog/topics/use-cases/index.html b/docs/blog/topics/use-cases/index.htmlindex fc10a589..246e12bd 100644--- a/docs/blog/topics/use-cases/index.html+++ b/docs/blog/topics/use-cases/index.html@@ -72,7 +72,7 @@<a class="chip" href="/blog/topics/internals/">internals<span class="ct">14</span></a>- <a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">12</span></a>+ <a class="chip" href="/blog/topics/concepts/">concepts<span class="ct">13</span></a><a class="chip" href="/blog/topics/comparisons/">comparisons<span class="ct">10</span></a>diff --git a/docs/blog/whats-new-in-agentic-ai-june-2026/index.html b/docs/blog/whats-new-in-agentic-ai-june-2026/index.htmlindex fc45155b..e42da0c2 100644--- a/docs/blog/whats-new-in-agentic-ai-june-2026/index.html+++ b/docs/blog/whats-new-in-agentic-ai-june-2026/index.html@@ -319,7 +319,7 @@ hive run; it’s free and open source.</p></div><footer class="post-foot wrap"><div class="prevnext">- <a class="pn prev" href="/blog/building-a-terminal-ui-xterm-node-pty/"><span class="k">← Older</span><span class="t">Building a Terminal UI with xterm.js and node-pty</span></a>+ <a class="pn prev" href="/blog/when-do-agents-need-an-agent-protocol/"><span class="k">← Older</span><span class="t">When Do AI Agents Actually Need an Agent Protocol?</span></a><a class="pn next" href="/blog/what-is-aeo-for-dev-tools/"><span class="k">Newer →</span><span class="t">AEO for Dev Tools: Getting Cited by ChatGPT and Claude</span></a></div><section class="related">diff --git a/docs/blog/when-do-agents-need-an-agent-protocol/index.html b/docs/blog/when-do-agents-need-an-agent-protocol/index.htmlnew file mode 100644index 00000000..c2e7ba88--- /dev/null+++ b/docs/blog/when-do-agents-need-an-agent-protocol/index.html@@ -0,0 +1,376 @@+<!doctype html>+<html lang="en">+<head>+<meta charset="UTF-8" />+<meta name="viewport" content="width=device-width, initial-scale=1.0" />+<title>When Do AI Agents Actually Need an Agent Protocol? — Munder Difflin Blog</title>+<meta name="description" content="When do AI agents need a protocol like MCP or A2A? Agents you own coordinate fine with file mailboxes; protocols earn their keep across boundaries." />+<link rel="canonical" href="https://munderdiffl.in/blog/when-do-agents-need-an-agent-protocol/" />++<link rel="icon" type="image/png" href="https://munderdiffl.in/logo.png" />+<link rel="apple-touch-icon" href="https://munderdiffl.in/logo.png" />+<meta name="theme-color" content="#F5F2E8" />++<!-- Open Graph -->+<meta property="og:site_name" content="Munder Difflin Blog" />+<meta property="og:type" content="article" />+<meta property="og:title" content="When Do AI Agents Actually Need an Agent Protocol? — Munder Difflin Blog" />+<meta property="og:description" content="When do AI agents need a protocol like MCP or A2A? Agents you own coordinate fine with file mailboxes; protocols earn their keep across boundaries." />+<meta property="og:url" content="https://munderdiffl.in/blog/when-do-agents-need-an-agent-protocol/" />+<meta property="og:image" content="https://munderdiffl.in/media/og.png" />+<meta property="og:locale" content="en_US" />+<meta property="article:published_time" content="2026-06-04T00:00:00.000Z" />+<meta property="article:author" content="Chaitanya Giri" />+<meta property="article:tag" content="Concepts" />+<meta property="article:tag" content="Multi-Agent" />+<meta property="article:tag" content="Internals" />+<meta property="article:tag" content="Interoperability" />+++<!-- Twitter -->+<meta name="twitter:card" content="summary_large_image" />+<meta name="twitter:title" content="When Do AI Agents Actually Need an Agent Protocol? — Munder Difflin Blog" />+<meta name="twitter:description" content="When do AI agents need a protocol like MCP or A2A? Agents you own coordinate fine with file mailboxes; protocols earn their keep across boundaries." />+<meta name="twitter:image" content="https://munderdiffl.in/media/og.png" />++<link rel="alternate" type="application/atom+xml" title="Munder Difflin Blog" href="https://munderdiffl.in/blog/feed.xml" />+<link rel="preconnect" href="https://fonts.googleapis.com" />+<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />+<link href="https://fonts.googleapis.com/css2?family=Geist:wght@400;500;600&family=JetBrains+Mono:wght@400;500;600;700&display=swap" rel="stylesheet" />+<link rel="stylesheet" href="/blog/assets/blog.css" />++<script type="application/ld+json">+{+ "@context": "https://schema.org",+ "@type": "BlogPosting",+ "headline": "When Do AI Agents Actually Need an Agent Protocol?",+ "description": "When do AI agents need a protocol like MCP or A2A? Agents you own coordinate fine with file mailboxes; protocols earn their keep across boundaries.",+ "image": ["https://munderdiffl.in/media/og.png"],+ "datePublished": "2026-06-04T00:00:00.000Z",+ "dateModified": "2026-06-04T00:00:00.000Z",+ "author": { "@type": "Person", "name": "Chaitanya Giri" },+ "publisher": {+ "@type": "Organization",+ "name": "Munder Difflin",+ "logo": { "@type": "ImageObject", "url": "https://munderdiffl.in/logo.png" }+ },+ "mainEntityOfPage": { "@type": "WebPage", "@id": "https://munderdiffl.in/blog/when-do-agents-need-an-agent-protocol/" },+ "keywords": "ai agent protocols, agent2agent a2a, model context protocol, do agents need a2a",+ "articleSection": "Concepts",+ "inLanguage": "en-US",+ "url": "https://munderdiffl.in/blog/when-do-agents-need-an-agent-protocol/"+}+</script>+<script type="application/ld+json">+{+ "@context": "https://schema.org",+ "@type": "BreadcrumbList",+ "itemListElement": [+ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://munderdiffl.in/" },+ { "@type": "ListItem", "position": 2, "name": "Blog", "item": "https://munderdiffl.in/blog/" },+ { "@type": "ListItem", "position": 3, "name": "When Do AI Agents Actually Need an Agent Protocol?", "item": "https://munderdiffl.in/blog/when-do-agents-need-an-agent-protocol/" }+ ]+}+</script>++<script type="application/ld+json">+{+ "@context": "https://schema.org",+ "@type": "FAQPage",+ "mainEntity": [+ { "@type": "Question", "name": "Do all multi-agent systems need an agent protocol like A2A?", "acceptedAnswer": { "@type": "Answer", "text": "No. Agent protocols standardize collaboration across boundaries — different vendors, frameworks, or organizations. If your agents are co-located, built on one framework, and owned by you, simpler in-house coordination like file mailboxes is usually faster, fully auditable, and protocol-free. You reach for a standard protocol when you cross a boundary." } },+ { "@type": "Question", "name": "What's the difference between MCP and A2A?", "acceptedAnswer": { "@type": "Answer", "text": "MCP (Model Context Protocol) standardizes how an agent connects to external tools and data. A2A (Agent2Agent) standardizes how separate agents discover one another and collaborate. Both are open standards now under the Linux Foundation. MCP is about reach to tools; A2A is about reach to other agents." } },+ { "@type": "Question", "name": "When is an agent protocol worth the complexity?", "acceptedAnswer": { "@type": "Answer", "text": "When you cross a trust, vendor, or framework boundary: exposing your agent for others to call, consuming a third party's agent, or coordinating agents built on different stacks over a network you don't fully control. Inside one owned, co-located hive, the protocol is usually overhead you don't need yet." } }++ ]+}+</script>+++</head>+<body>+<a class="skip-link" href="#main">Skip to content</a>+<nav id="nav">+ <a class="brand" href="/blog/" aria-label="Munder Difflin Blog home">+ <span class="brand-mark">MD</span>+ <span class="brand-word">MUNDER DIFFLIN<span class="sep">/</span><span class="blog">BLOG</span></span>+ </a>+ <span class="spacer"></span>+ <div class="links">+ <a href="/blog/">Latest</a>+ <a href="/blog/topics/">Topics</a>+ <a href="/blog/about/">About</a>+ <a href="https://munderdiffl.in">↗ Product</a>+ </div>+ <div class="nav-actions">+ <a class="btn sm" href="https://munderdiffl.in/blog/feed.xml" aria-label="RSS feed">⤵ RSS</a>+ <a class="btn sm primary" href="https://munderdiffl.in/#install">⤓ Download</a>+ </div>+</nav>++<main id="main">++<article>+ <header class="post-head wrap">+ <nav class="crumbs" aria-label="Breadcrumb">+ <a href="/blog/">Blog</a>+ <span>/</span>+ <a href="/blog/topics/concepts/">Concepts</a>+ </nav>+ <h1>When Do AI Agents Actually Need an Agent Protocol?</h1>+ <p class="dek">When do AI agents need a protocol like MCP or A2A? Agents you own coordinate fine with file mailboxes; protocols earn their keep across boundaries.</p>+ <div class="byline">+ <span class="av" aria-hidden="true">CG</span>+ <strong>Chaitanya Giri</strong>+ <span class="dot" aria-hidden="true">·</span>+ <time datetime="2026-06-04">Jun 4, 2026</time>+ <span class="dot" aria-hidden="true">·</span>+ <span>5 min read</span>+ <span class="tag kind">Concepts</span>+ </div>+ </header>++ <div class="post-wrap wrap">+ <div class="prose">+ <div class="callout tldr"><span class="ic">TL;DR</span><p>Open <strong>agent protocols</strong> — MCP+(agent-to-tools) and A2A (agent-to-agent), both now under the Linux Foundation — are powerful, but not+every multi-agent system needs them. The dividing line is a <strong>boundary</strong>: agents you own,+on one framework, on one machine can coordinate with simple <strong>file mailboxes</strong> — faster,+fully auditable, zero protocol overhead. You reach for a standard protocol when you <em>cross</em> a+boundary: another org's agents, another vendor's framework, a network you don't control. Use the+boundary test before adding the complexity.</p></div>+<p>2025 and 2026 gave the agent world real plumbing: open protocols for how agents talk to tools and to+each other, with vendor-neutral governance behind them. That’s genuinely good news. It also prompts a+fair question for anyone building a multi-agent system: <em>do I need to adopt these?</em> The honest answer is+often “not yet” — and knowing when you do is worth more than adopting on reflex. Here’s the dividing+line.</p>+<h2 id="what-an-agent-protocol-actually-buys-you" tabindex="-1">What an agent protocol actually buys you <a class="anchor" href="#what-an-agent-protocol-actually-buys-you" aria-hidden="true">#</a></h2>+<p>Two open standards do most of the work, and they solve different problems:</p>+<ul>+<li><strong>MCP (the Model Context Protocol)</strong> standardizes how an agent reaches <strong>tools and data</strong>. Anthropic+introduced it and <a href="https://www.anthropic.com/news/donating-the-model-context-protocol-and-establishing-of-the-agentic-ai-foundation">donated it to the Agentic AI Foundation under the Linux+Foundation</a>+in December 2025.</li>+<li><strong>A2A (Agent2Agent)</strong> standardizes how separate <strong>agents</strong> discover each other and collaborate across+frameworks and vendors. Google created it and <a href="https://www.linuxfoundation.org/press/linux-foundation-launches-the-agent2agent-protocol-project-to-enable-secure-intelligent-communication-between-ai-agents">donated it to the Linux+Foundation</a>,+which launched the project in mid-2025.</li>+</ul>+<p>Notice the shared word in both pitches: <strong>across</strong>. The value a protocol adds is interoperability across+something — across tool vendors, across agent frameworks, across organizations. That’s the lens for+deciding whether you need one.</p>+<h2 id="when-you-dont-need-one-the-co-located-hive" tabindex="-1">When you don’t need one: the co-located hive <a class="anchor" href="#when-you-dont-need-one-the-co-located-hive" aria-hidden="true">#</a></h2>+<p>If your agents are <strong>yours</strong> — same framework, same machine, one team’s control — a standardized agent+protocol is usually solving a problem you don’t have. Inside <a href="/blog/local-first-ai-agent-orchestration/">a local-first+hive</a>, agents coordinate through+<a href="/blog/atomic-file-mailboxes-for-agents/">file-based mailboxes</a>: each writes a message to its outbox, a+router delivers it to the recipient’s inbox, and the whole exchange is durable and auditable because+it’s just files. There’s no discovery problem (you know every agent), no cross-vendor envelope to+negotiate, no network in the middle.</p>+<p>For that setup, the in-house approach actually <em>wins</em> on the things that matter: it’s lower latency+(local file operations, no protocol handshakes), simpler to debug (read the files), and fully under your+audit. Adopting A2A to let two agents in the same process “discover” each other would be ceremony around+a problem you’ve already solved. This is the same reason <a href="/blog/coordinating-ai-coding-agents/">coordinating co-located+agents</a> rarely starts with a protocol — it starts with a shared+directory.</p>+<h2 id="when-you-do-need-one-crossing-a-boundary" tabindex="-1">When you do need one: crossing a boundary <a class="anchor" href="#when-you-do-need-one-crossing-a-boundary" aria-hidden="true">#</a></h2>+<p>The calculus flips the moment your agents stop being a closed, owned set. A protocol earns its keep when+you cross a <strong>boundary</strong>:</p>+<ul>+<li><strong>A vendor or framework boundary</strong> — your agent needs to collaborate with an agent built on a+different stack. A2A gives them a shared language instead of a bespoke integration per pair.</li>+<li><strong>An organizational boundary</strong> — you want to expose an agent for other teams or companies to call, or+consume someone else’s agent. Discovery and a standard envelope stop mattering when there’s only one+of you; they’re essential when there are many.</li>+<li><strong>A tool boundary</strong> — your agent needs capabilities you didn’t build. That’s MCP’s job, and it’s worth+adopting early because tools are exactly where you <em>want</em> to reach outside your own code. (In a hive,+you can <a href="/blog/mcp-and-skills-in-a-hive/">bring MCP servers and skills in</a> without exposing anything+else.)</li>+</ul>+<p>The pattern: protocols are for reach beyond what you own. Inside what you own, simpler coordination is+both sufficient and better.</p>+<h2 id="the-boundary-test" tabindex="-1">The boundary test <a class="anchor" href="#the-boundary-test" aria-hidden="true">#</a></h2>+<p>Here’s the heuristic, in one question: <strong>are the agents on the same side of a trust-and-framework+boundary?</strong></p>+<ul>+<li><strong>Same side</strong> (you built them, same stack, you can see them all) → in-house coordination — file+mailboxes, a shared log, direct calls — is enough. Don’t add a protocol yet.</li>+<li><strong>Different sides</strong> (other vendors, other orgs, a network you don’t control) → adopt the standard.+A2A for agent-to-agent reach, MCP for tool reach.</li>+</ul>+<p>A concrete example makes the line obvious. A hive of agents reviewing <em>your own</em> codebase never needs+A2A — they share a directory and a router, and discovery is meaningless when you already know every+agent. But the moment you want that hive to hand a task to a partner company’s compliance agent, or to+call a vendor’s specialized research agent, you’ve crossed an organizational boundary — and a shared+protocol is what spares you a brittle, bespoke integration for every partner you add.</p>+<p>Most teams’ first multi-agent system lives entirely on the “same side.” Reach for the protocol when, and+only when, you actually cross over — and notice the two boundaries can differ: you might want MCP for+tools long before you ever need A2A for agents.</p>+<h2 id="build-so-you-can-speak-them-later" tabindex="-1">Build so you can speak them later <a class="anchor" href="#build-so-you-can-speak-them-later" aria-hidden="true">#</a></h2>+<p>None of this is an argument against the protocols — it’s an argument against adopting them prematurely.+The healthy position is to keep your coordination simple while it’s internal, and design so you <em>can</em>+speak the open standards when a boundary appears. That’s the same “open protocols, local control plane”+idea behind <a href="/blog/local-first-vs-cloud-agent-sdks/">local-first vs cloud agent SDKs</a>: keep the core+local and simple, reach outward through standards when there’s a real outside to reach. Adopting a+protocol should be a response to a boundary, not a default.</p>+<h2 id="faq" tabindex="-1">FAQ <a class="anchor" href="#faq" aria-hidden="true">#</a></h2>+<p><strong>Do all multi-agent systems need a protocol like A2A?</strong> No — co-located agents you own can coordinate+with file mailboxes. Protocols matter when you cross a vendor, framework, or organizational boundary.</p>+<p><strong>MCP vs A2A?</strong> MCP connects an agent to tools and data; A2A lets separate agents discover and+collaborate. Both are open standards under the Linux Foundation.</p>+<p><strong>When is the protocol worth it?</strong> When you expose your agent to others, consume a third party’s agent,+or coordinate across different stacks and networks — i.e., when you cross a boundary.</p>+<hr>+<p>Munder Difflin takes the “same side” path: a <a href="https://munderdiffl.in/#how">local hive whose agents coordinate through file+mailboxes</a>, simple and auditable, free to speak open protocols outward when+a boundary appears. <a href="https://munderdiffl.in/#install">Download Munder Difflin</a> to run a coordinated team+of agents without protocol ceremony; it’s free and open source.</p>+<p><em>Sources: <a href="https://www.anthropic.com/news/donating-the-model-context-protocol-and-establishing-of-the-agentic-ai-foundation">Anthropic — donating MCP to the Agentic AI Foundation</a>; <a href="https://www.linuxfoundation.org/press/linux-foundation-launches-the-agent2agent-protocol-project-to-enable-secure-intelligent-communication-between-ai-agents">Linux Foundation — Agent2Agent protocol project</a>.</em></p>++++ <section class="faq" aria-label="Frequently asked questions">+ <h2 id="faq">FAQ</h2>++ <div class="qa">+ <p class="q">Do all multi-agent systems need an agent protocol like A2A?</p>+ <p class="a">No. Agent protocols standardize collaboration across boundaries — different vendors, frameworks, or organizations. If your agents are co-located, built on one framework, and owned by you, simpler in-house coordination like file mailboxes is usually faster, fully auditable, and protocol-free. You reach for a standard protocol when you cross a boundary.</p>+ </div>++ <div class="qa">+ <p class="q">What's the difference between MCP and A2A?</p>+ <p class="a">MCP (Model Context Protocol) standardizes how an agent connects to external tools and data. A2A (Agent2Agent) standardizes how separate agents discover one another and collaborate. Both are open standards now under the Linux Foundation. MCP is about reach to tools; A2A is about reach to other agents.</p>+ </div>++ <div class="qa">+ <p class="q">When is an agent protocol worth the complexity?</p>+ <p class="a">When you cross a trust, vendor, or framework boundary: exposing your agent for others to call, consuming a third party's agent, or coordinating agents built on different stacks over a network you don't fully control. Inside one owned, co-located hive, the protocol is usually overhead you don't need yet.</p>+ </div>++ </section>++++ <hr />+ <div class="share">+ <span class="lbl">Tags</span>+ <a class="tag" href="/blog/tags/concepts/">Concepts</a><a class="tag" href="/blog/tags/multi-agent/">Multi-Agent</a><a class="tag" href="/blog/tags/internals/">Internals</a><a class="tag" href="/blog/tags/interoperability/">Interoperability</a>+ </div>++ </div>+++ <aside class="toc-rail" aria-label="Table of contents">+ <div class="tt">On this page</div>+ <ol>+ <li class="lvl-2"><a href="#what-an-agent-protocol-actually-buys-you">What an agent protocol actually buys you</a></li><li class="lvl-2"><a href="#when-you-dont-need-one-the-co-located-hive">When you don’t need one: the co-located hive</a></li><li class="lvl-2"><a href="#when-you-do-need-one-crossing-a-boundary">When you do need one: crossing a boundary</a></li><li class="lvl-2"><a href="#the-boundary-test">The boundary test</a></li><li class="lvl-2"><a href="#build-so-you-can-speak-them-later">Build so you can speak them later</a></li><li class="lvl-2"><a href="#faq">FAQ</a></li>+ </ol>+ </aside>++ </div>++ <footer class="post-foot wrap"><div class="prevnext">+ <a class="pn prev" href="/blog/building-a-terminal-ui-xterm-node-pty/"><span class="k">← Older</span><span class="t">Building a Terminal UI with xterm.js and node-pty</span></a>+ <a class="pn next" href="/blog/whats-new-in-agentic-ai-june-2026/"><span class="k">Newer →</span><span class="t">What's New in Agentic AI: A June 2026 Field Guide</span></a>+ </div>+ <section class="related">+ <h2>Related in Concepts</h2>+ <div class="post-grid">+ <article class="card">+ <a class="thumb t-concepts" href="/blog/generative-engine-optimization-techniques/" aria-hidden="true" tabindex="-1">+ <span>CONCEPTS</span>+ </a>+ <div class="body">+ <div class="meta">+ <time datetime="2026-06-05">Jun 5, 2026</time>+ <span class="dot" aria-hidden="true"></span>+ <span>4 min</span>+ </div>+ <h3><a href="/blog/generative-engine-optimization-techniques/">Generative Engine Optimization: The Techniques the Research Backs</a></h3>+ <p class="dek">What the first peer-reviewed GEO study found works to get content cited by AI — statistics, source citations, quotes — and why keyword stuffing backfires.</p>+ <div class="foot">+ <span class="tag kind">Concepts</span>+ <a class="more" href="/blog/generative-engine-optimization-techniques/" aria-label="Read: Generative Engine Optimization: The Techniques the Research Backs">Read →</a>+ </div>+ </div>+</article>+<article class="card">+ <a class="thumb t-concepts" href="/blog/agents-rule-of-two/" aria-hidden="true" tabindex="-1">+ <span>CONCEPTS</span>+ </a>+ <div class="body">+ <div class="meta">+ <time datetime="2026-06-04">Jun 4, 2026</time>+ <span class="dot" aria-hidden="true"></span>+ <span>5 min</span>+ </div>+ <h3><a href="/blog/agents-rule-of-two/">The Agents Rule of Two: A Simple Safety Rule for Coding Agents</a></h3>+ <p class="dek">Meta's Agents Rule of Two for coding agents: don't let one session combine untrusted input, private data, and external reach at once — or supervise.</p>+ <div class="foot">+ <span class="tag kind">Concepts</span>+ <a class="more" href="/blog/agents-rule-of-two/" aria-label="Read: The Agents Rule of Two: A Simple Safety Rule for Coding Agents">Read →</a>+ </div>+ </div>+</article>+<article class="card">+ <a class="thumb t-concepts" href="/blog/can-claude-code-agents-talk-to-each-other/" aria-hidden="true" tabindex="-1">+ <span>CONCEPTS</span>+ </a>+ <div class="body">+ <div class="meta">+ <time datetime="2026-06-04">Jun 4, 2026</time>+ <span class="dot" aria-hidden="true"></span>+ <span>6 min</span>+ </div>+ <h3><a href="/blog/can-claude-code-agents-talk-to-each-other/">Can Claude Code Agents Talk to Each Other?</a></h3>+ <p class="dek">Can Claude Code agents talk to each other? By default they report to their launcher — but a small coordination layer lets them message peer-to-peer.</p>+ <div class="foot">+ <span class="tag kind">Concepts</span>+ <a class="more" href="/blog/can-claude-code-agents-talk-to-each-other/" aria-label="Read: Can Claude Code Agents Talk to Each Other?">Read →</a>+ </div>+ </div>+</article>++ </div>+ </section>++ </footer>+</article>++</main>+<footer>+ <div class="wrap">+ <div class="foot-top">+ <a class="foot-brand brand" href="/blog/">+ <span class="brand-mark">MD</span>+ <span class="brand-word">MUNDER DIFFLIN<span class="sep">/</span><span class="blog">BLOG</span></span>+ </a>+ <div class="foot-links">+ <a href="/blog/">Latest</a>+ <a href="/blog/topics/">Topics</a>+ <a href="/blog/about/">About</a>+ <a href="https://munderdiffl.in/blog/feed.xml">RSS</a>+ <a href="https://github.com/chaitanyagiri/munder-difflin">GitHub</a>+ <a href="https://munderdiffl.in">munderdiffl.in ↗</a>+ </div>+ </div>+ <div class="foot-meta">+ © 2026 Munder Difflin · Local-first · MIT-licensed ·+ Built on <a href="https://munderdiffl.in">Electron, React, Pixi.js, xterm.js & node-pty</a>.+ Run an office of agents while you sleep.+ </div>+ </div>+</footer>++<script>+ // sticky-nav border on scroll+ (function () {+ var nav = document.getElementById('nav');+ if (!nav) return;+ var onScroll = function () { nav.classList.toggle('scrolled', window.scrollY > 8); };+ onScroll(); window.addEventListener('scroll', onScroll, { passive: true });+ })();+</script>++</body>+</html>diff --git a/docs/sitemap.xml b/docs/sitemap.xmlindex e1e5f286..9bb83a5a 100644--- a/docs/sitemap.xml+++ b/docs/sitemap.xml@@ -251,6 +251,12 @@<changefreq>monthly</changefreq><priority>0.8</priority></url>+ <url>+ <loc>https://munderdiffl.in/blog/when-do-agents-need-an-agent-protocol/</loc>+ <lastmod>2026-06-04</lastmod>+ <changefreq>monthly</changefreq>+ <priority>0.8</priority>+ </url><url><loc>https://munderdiffl.in/blog/building-a-terminal-ui-xterm-node-pty/</loc><lastmod>2026-06-03</lastmod>@@ -468,8 +474,8 @@<url><loc>https://munderdiffl.in/blog/tags/internals/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url><url><loc>https://munderdiffl.in/blog/tags/orchestration/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url><url><loc>https://munderdiffl.in/blog/tags/guides/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>- <url><loc>https://munderdiffl.in/blog/tags/comparisons/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url><url><loc>https://munderdiffl.in/blog/tags/concepts/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>+ <url><loc>https://munderdiffl.in/blog/tags/comparisons/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url><url><loc>https://munderdiffl.in/blog/tags/tools/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url><url><loc>https://munderdiffl.in/blog/tags/getting-started/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url><url><loc>https://munderdiffl.in/blog/tags/memory/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>@@ -535,6 +541,7 @@<url><loc>https://munderdiffl.in/blog/tags/devrel/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url><url><loc>https://munderdiffl.in/blog/tags/industry/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url><url><loc>https://munderdiffl.in/blog/tags/protocols/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url>+ <url><loc>https://munderdiffl.in/blog/tags/interoperability/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url><url><loc>https://munderdiffl.in/blog/tags/geo/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url><url><loc>https://munderdiffl.in/blog/tags/tutorial/</loc><changefreq>weekly</changefreq><priority>0.3</priority></url></urlset>