Evidence-linked trend hypothesis
Agent protocols become the interoperability layer
MCP, A2A, ACP, extension systems, and agent-facing APIs are turning tool discovery and cross-agent communication into an explicit interoperability layer.
Current thesis
The durable integration surface for agentic software is becoming a small family of protocols that separate models and harnesses from tools, services, interfaces, and other agents. Confidence: medium. Supported by 96 normalized raw signals. This New Runtime record is an evidence-linked retrieval unit.
Source ledger
Publishable sources attached to this record.
| # | Source | Role | Public status |
|---|---|---|---|
| 1 | microsoft.comsource | primary receipt | source_urls |
| 2 | anthropic.comsource | supporting receipt | source_urls |
| 3 | blog.mozilla.aiarticle | supporting receipt | source_urls |
| 4 | cloud.google.comsource | supporting receipt | source_urls |
| 5 | anthropic.comsource | supporting receipt | source_urls |
Showing 5 of 9; the complete set is exposed in the JSON route.
Current state, as of Oct 9, 2026
Where this stands now
strengthening Managed MCP services, multi‑account gateways, open‑source MCP servers, and growing adoption of A2A/ACP confirm that a small family of protocols now forms the durable integration surface for agentic software.
Recent projects such as Mem0's Gateway and AgentCore's MCP provide scoped keys, multi‑account architectures, and marketplace‑style plugin catalogs, turning protocol specifications into operated integration surfaces. Open‑source infrastructure like ACI.dev offers a Unified Model‑Context‑Protocol (MCP) server that delivers intent‑aware, multi‑tenant tool access for hundreds of services. Comparative archives list MCP, ANP, agents.json and other emerging standards, showing a converging ecosystem around a thin, versioned interoperability layer.
For builders, this means preserving direct APIs as the source of truth while exposing a thin protocol layer that handles discovery metadata, scoped authorization, idempotency, and observable failures. Adoption decisions should prioritize portability and reliability of completed work rather than sheer tool count.
What changed since the original text
- September 2026 update reports governed MCP connectors, a multi‑account AgentCore Gateway design, and a marketplace for plugins, moving protocols from demos to operated surfaces. 1
- ACI.dev released an open‑source MCP server providing multi‑tenant auth, granular permissions, and dynamic tool discovery for 600+ tools. 2
- Archive comparison documents multiple active protocols (MCP, ANP, agents.json, LMOS) and notes rapid community interest. 3
Open questions
- Will a single dominant protocol emerge or will multiple specialized protocols coexist?
- How will governance and standardization be coordinated across competing cloud providers and open‑source projects?
- What mechanisms will ensure backward compatibility as protocols evolve?
Watch next: A major cloud provider announcing native support for a unified agent protocol would shift the balance toward a single interoperable standard.
- Weekly update: New protocols and gateways solidify a thin interoperability layer for agents update, Sep 21, 2026
- ACI.dev is the open-source infrastructure layer for AI-agent tool-use. It gives your agents intent-aware access to 600+ tools with… archive, May 30, 2001
- Comparison of Agent Communication Protocols archive, Mar 8, 2001
Rewritten automatically by the New Runtime knowledge desk from this record's weekly updates, releases and archive. The original text below is kept as written (Sep 28, 2025); where the two disagree, this section is newer.
Weekly knowledge desk
Weekly updates
1 reviewed update to this pattern, newest first. Every update is checked against its evidence before it changes the record.
New protocols and gateways solidify a thin interoperability layer for agents
Recent signals show several concrete projects creating dedicated protocols that separate model harnesses from tools and services. Mem0's Gateway and AgentCore's MCP provide scoped keys and multi‑account architectures that enforce tool boundaries, while Anthropic’s roadmap highlights MCP as an interoperability substrate. External sources confirm the emergence of open standards such as A2A that act as transport‑level wrappers for remote agents. Together these independent developments reinforce the claim that a small family of protocols is becoming the durable integration surface for agentic software.
Record state: confidence high.
- Mem0 launches Gateway to give agents scoped keys for tools signal, Sep 24, 2026
- Build a multi-account AI agent with AgentCore Gateway and MCP post, Sep 26, 2026
- Build a multi-account AI agent with AgentCore Gateway and MCP signal, Sep 26, 2026
- The New MCP Roadmap external, Sep 28, 2026
- Overview - A2A Protocol external, Sep 28, 2026
- A2A agent service | Microsoft Learn external, Sep 28, 2026
What is changing
Agent integrations are moving away from one bespoke connector per model or application. MCP exposes tools and resources. A2A describes communication between agents. ACP connects coding agents to compatible clients. Extension systems and agent-facing APIs are converging on the same separation: a harness should be able to discover and invoke capabilities without owning every integration.
This is not only a standards story. Managed MCP services, protocol proxies, tool-search mechanisms, and protocol-aware interfaces show the operational layer forming around the specifications.
What the archive adds
- Microsoft Research documents tool-space interference, evidence that protocol compatibility must include selection quality rather than only schema access.
- Anthropic’s code-execution pattern and Mozilla’s MCP proxy move protocol calls into smaller, inspectable execution surfaces.
- Google Cloud’s managed MCP servers and the transfer of MCP to a neutral foundation indicate that interoperability is becoming ecosystem infrastructure.
- A2A and ACP widen the thesis from tool invocation to cross-agent and client-agent compatibility.
Operational consequence
Teams should preserve direct APIs as the source of truth while exposing a thin, versioned protocol layer with discovery metadata, scoped authorization, idempotency rules, and observable failures. Protocol adoption should be judged by portability and completed-work reliability, not by the number of registered tools.
September 2026 update
What changed
Governed MCP connectors, a multi-account AgentCore Gateway design, and a marketplace for plugins/connectors move protocol support from demo adapters toward operated integration surfaces.
What the protocol must carry
Discovery alone is insufficient. A useful contract names capability, input/output schema, scope, identity, idempotency, error state, audit record, and version. Keep the direct API as the source of truth; expose the protocol as a bounded adapter.
Boundary
The evidence shows proliferation and governance mechanisms, not universal convergence on one protocol. Treat interoperability as a family of contracts, and test completed-work reliability rather than counting integrations.