---
schema_version: "newruntime-agent-readable-v0.2"
type: "trend_pattern"
stable_id: "pattern:agent-protocols-become-interoperability-layer"
slug: "agent-protocols-become-interoperability-layer"
title: "Agent protocols become the interoperability layer"
description: "MCP, A2A, ACP, extension systems, and agent-facing APIs are turning tool discovery and cross-agent communication into an explicit interoperability layer."
retrieval_nugget: "MCP, A2A, ACP, extension systems, and agent-facing APIs are turning tool discovery and cross-agent communication into an explicit interoperability layer. 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 is medium."
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."
status: "published"
confidence: "medium"
first_seen: "2025-09-28"
last_verified: "2026-07-24"
record_date: "2026-07-24"
date_kind: "last_verified"
supporting_signals: ["tg-466","tg-696","tg-814","tg-977","tg-987","tg-1287","tg-1518"]
related_posts: []
counter_evidence: ["Plain HTTP APIs, CLIs, and provider-specific SDKs can be smaller, safer, and easier to operate than a general agent protocol for narrow integrations.","Protocol support does not guarantee semantic compatibility: overlapping tools, inconsistent schemas, weak permissions, and context overhead can still make agents unreliable."]
revision_trigger: "Revise the thesis if MCP, A2A, ACP, and similar contracts remain isolated ecosystems or add more operational cost than direct APIs across real multi-tool and cross-agent workflows."
topics: ["agent-protocols","mcp","a2a","interoperability"]
source_urls: ["https://microsoft.com/en-us/research/blog/tool-space-interference-in-the-mcp-era-designing-for-agent-compatibility-at-scale","https://anthropic.com/engineering/code-execution-with-mcp","https://blog.mozilla.ai/mcpd-proxy-centralized-tool-access-for-ai-agents-in-vs-code-cursor-and-beyond","https://cloud.google.com/blog/products/ai-machine-learning/announcing-official-mcp-support-for-google-services","https://anthropic.com/news/donating-the-model-context-protocol-and-establishing-of-the-agentic-ai-foundation","https://github.blog/changelog/2026-01-28-acp-support-in-copilot-cli-is-now-in-public-preview","https://modelcontextprotocol.io/docs/getting-started/intro"]
routes: {"html":"https://newruntime.com/patterns/agent-protocols-become-interoperability-layer/","markdown":"https://newruntime.com/patterns/agent-protocols-become-interoperability-layer.md","json":"https://newruntime.com/patterns/agent-protocols-become-interoperability-layer.json"}
source_format: "markdown"
---

# Agent protocols become the interoperability layer

## Retrieval answer

MCP, A2A, ACP, extension systems, and agent-facing APIs are turning tool discovery and cross-agent communication into an explicit interoperability layer. 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 is medium.

## 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.