Agent Interoperability Protocols
Open protocols like MCP are becoming the connection layer between AI systems, tools and companies.
Traction · 2026-W34
Why it's moving
- MCP has moved from an Anthropic project to a de-facto industry standard, with adoption by OpenAI, Google, Microsoft and thousands of community servers.
- A fresh MCP specification revision (2026-07-28) landed this summer, addressing enterprise needs like authentication and server discovery.
- MCP SDK downloads on npm and PyPI show steep, sustained growth — a hard adoption signal rather than press coverage.
- Google's A2A protocol moved to the Linux Foundation, and payment-focused protocols (AP2) drew in banks and card networks — evidence of breadth beyond one vendor.
- Enterprise platforms now ship MCP support as a checklist feature, pulling the standard into procurement conversations.
What changed this week
- Combined weekly downloads of the MCP SDKs held at 137.5M (npm 51.1M, PyPI 86.4M), up 1.3% across the two-week window — growth has flattened at a high absolute level.
- Four arXiv submissions in the last 30 days matched the theme's protocol terms, the lowest research volume of any AI theme tracked here.
- 16 Hacker News stories at a median of 38 points: steady practitioner discussion rather than a spike.
Why you should care
Agent systems become more useful when they can safely connect to tools, data and other agents — protocols make that possible across vendors. Whether your systems speak these protocols will decide if your AI investments compose or fragment. Adoption is measurable and steep. Worth learning now.
What is it?
A family of open standards that let AI agents connect to tools, data and each other. The Model Context Protocol (MCP) standardises how agents access tools and context; Agent2Agent (A2A) covers agent-to-agent communication; and payment protocols such as AP2 define how agents transact on a user's behalf. Together they are becoming the 'plumbing layer' that makes agent systems composable across vendors.
What should you do?
For managers
What this could change
These protocols determine whether your AI investments compose or fragment. If your systems expose capabilities through open standards like MCP, any agent platform can use them — reducing vendor lock-in and integration cost. Expect software vendors to advertise MCP support the way they once advertised REST APIs. Governance matters early: an agent that can reach internal tools is a security surface, so identity, permissions and audit for agent access deserve attention now, before ad-hoc integrations spread.
Bring to your next engineering conversation
Ask which of your systems expose MCP endpoints, and put identity and audit for agent access on the security roadmap.
For developers
What to learn and build
Learn MCP first — it is the most adopted and the concepts transfer. Understand the primitives (tools, resources, prompts), the client–server architecture, and the security model (OAuth-based authorisation, consent, sandboxing). Build one MCP server that exposes a real internal system; that single exercise teaches most of what matters. Then skim A2A and AP2 to understand where multi-agent and transactional flows are heading. Watch the spec revisions — this space changes quarterly.
This week's move
Build one MCP server against a real internal system; the concepts transfer directly to A2A and payment protocols.
Learning path
No prior knowledge assumed — understand what it is and try it once.
Every resource is editorially reviewed and link-checked before publication. Dated items are at most six months old; “maintained” marks continuously-updated docs and repositories.
- 1Understand the conceptModel Context Protocol — official introductionmodelcontextprotocol.io · maintained · 15 min
- 2Watch a practical videoMCP vs API: Why traditional APIs are failing AI agentsYouTube · July 2026 · 12 min
- 3Build something realConnect your first MCP server to Claude Desktop (user quickstart)modelcontextprotocol.io · maintained · 30 min
- 4Follow the ecosystemMCP Blog →npm →
Why this scores 75
How is this calculated? →Repository usage, package downloads, stars, forks, contributors and enterprise implementations.
How quickly adoption indicators are changing (4- and 8-week growth).
Whether the trend appears across several independent sources — developers, open source, research, cloud providers, enterprises and media.
Potential relevance for organisations: productivity, infrastructure, security, cost and strategy.
Whether understanding the technology is likely to remain useful beyond the immediate news cycle.
Measured this week · 2026-W34
- GitHub stars (tracked repos)
- 128,450+735
- Package downloads / week
- 137,530,242+1,765,072
- Source types reporting
- 4
Collected automatically from GitHub and package registries; deltas compare against the previous week's collection.
Signals detected
The evidence behind this theme's score. Every entry links to its source.
5 sources across 4 categories
MCP Blog →npm →GitHub →Linux Foundation / Google →AP2 Protocol →- MCP Blog2026-07-28 spec revision
New MCP specification revision focused on enterprise readiness: auth, discovery and protocol hardening.
foundationSpecification release
- npmSteep sustained growth
The official MCP TypeScript SDK shows continued strong week-over-week download growth.
packageWeekly downloads
- GitHubThousands of community MCP servers
Reference server collection and community registries keep expanding across categories.
open-sourceEcosystem size
- Linux Foundation / GoogleA2A under neutral governance
Agent2Agent protocol developed under Linux Foundation governance with 100+ supporting companies.
foundationGovernance
- AP2 ProtocolPayments/card networks engaged
Agent Payments Protocol documentation and partner ecosystem for agent-initiated transactions.
vendorIndustry participation
Traction over time
Measured history has not started yet
The first measured week has been recorded. A trend line appears once there are two weekly collections to compare.
Editorial baseline (illustrative, not measured)
An editor's estimate of how this theme developed before Tech Signal began measuring it, kept for context. It is deliberately not joined to the measured series above, and it never feeds a score.
| Month | Traction Score |
|---|---|
| Mar | 31 |
| Apr | 38 |
| May | 45 |
| Jun | 56 |
| Jul | 73 |
| Aug | 75 |
Related themes
Agent Interoperability Protocols connects to:
Software teams are delegating whole coding tasks to agents, not just autocompleting lines.
Past the hype, retrieval quality — not model choice — is what limits AI answers on your own data.
Serving engines decide whether AI features are profitable — same GPUs, several times the throughput.
Models small enough to run on laptops and phones now handle real production tasks.
How this theme developed
August 2026
- SDKs and enterprise gateways begin adopting the 2026-07-28 MCP specification revision.
- Agent payment standards attract broader financial-industry participation.
July 2026
- MCP publishes a major specification revision targeting enterprise deployment.
- Enterprise MCP registries and gateway products mature into a distinct tooling category.
June 2026
- Theme entered the weekly top list: MCP adoption crossed from AI-tooling niche into mainstream enterprise platforms.
- A2A ecosystem grows under Linux Foundation governance.