Are MCP and A2A settling into the stable plumbing between agents and tools, and who runs them in production?
If agent-to-tool (MCP) and agent-to-agent (A2A) links become neutral, versioned standards, builders can wire agents across vendors once instead of writing custom glue for every pairing, and buyers can switch platforms with less lock-in.
Newest first. Each claim is our summary of the linked primary source, with a short quote from it.
Microsoft says Agent-to-Agent (A2A) support in Microsoft Foundry is generally available, in its September 2026 Foundry update.
Tool Search and Agent-to-Agent (A2A) are GA.
What it does not show: A monthly roundup; it does not detail which A2A versions or features the GA covers or name customers.
Sierra published a draft of Personal Agent Protocol ("Poppy"), developed with Meta: a well-known discovery file, OAuth sign-in and one session token that lets a personal agent work with a company within access the customer approved.
Poppy is built on the principle that customers decide what access to give their personal agents, and companies set parameters for what those agents can do.
What it does not show: A draft for comment; the reference implementation is still to come, and the 35 added design partners join the design process, not production use. Payments are left to extensions.
The A2A project says A2A was accepted as a Growth Stage project at the Agentic AI Foundation, the Linux Foundation fund that already hosts MCP.
The Agent2Agent (A2A) protocol has officially been accepted as a Growth Stage project at the Agentic AI Foundation (AAIF).
What it does not show: Its adoption figures (over 150 organizations, production use) are the project's own and name no specific production deployments.
AWS says its AgentCore Gateway can advertise MCP 2026-07-28 alongside 2025-11-25, so clients on the older version are unaffected while new clients opt in.
Adding 2026-07-28 to a gateway that also advertises 2025-11-25 does not change anything for clients that request the older version.
What it does not show: Vendor post about its own gateway; no named customer running the new version is cited.
MCP's maintainers published spec version 2026-07-28, which turns MCP into a stateless request/response protocol by removing the handshake and sessions, a breaking change.
The highlight of this release is a stateless protocol core - MCP is transforming from a bidirectional stateful protocol into a request/response stateless protocol.
What it does not show: Spec and Tier 1 SDK release; it does not show how many deployed clients and servers have moved to the new version.
The A2A project released v1.0 of its agent-to-agent spec, describing it as a maturity release that clarifies ambiguous areas and addresses enterprise deployment needs.
The v1.0 release emphasizes maturity rather than reinvention: the core ideas remain intact, while rough edges have been removed, ambiguous areas clarified, and enterprise deployment requirements addressed more directly.
What it does not show: The project's own post; v1.0 includes breaking changes to the interaction protocol, per the same post.
MCP's maintainers announced that Anthropic is donating MCP to the new Agentic AI Foundation, a directed fund under the Linux Foundation, as a founding project.
Anthropic is donating MCP to the Agentic AI Foundation, a directed fund under the Linux Foundation.
What it does not show: A governance move; the post says maintainers keep technical direction, so it does not by itself change the protocol.
Signals we are watching for. Our own reading of where the thread could go: not predictions, and not sourced claims.
Across six models and three environments, researchers report matched interfaces gave different scores and costs. Their DART repair raised scores by up to 9.0 points and cut MCP token cost by up to 27.1k tokens per task.
Why it matters: MCP versus CLI isn't a neutral choice. Test both on your own tasks before standardizing on one.
From Drop #049 · Tue, Oct 27 · MorningAcross 14 evaluation dimensions, the authors find CLI more efficient for single-user, local workflows, while MCP covers needs CLI cannot: fine-grained access control, credential isolation, structured audit and multi-tenant governance.
Why it matters: The authors argue progressive disclosure brings MCP's token use close to CLI's, so production teams need not trade governance for context budget.
From Drop #042 · Fri, Oct 23 · EveningThe Linux Foundation says AAIF added Agent Skills from Anthropic, Open Responses from OpenAI, OpenEnv from Hugging Face and OpenSandbox from Alibaba, joining MCP and A2A. It says AAIF now has 305 members.
Why it matters: Skills, a cross-provider API spec, RL environments and sandboxes now sit under neutral governance, so builders can adopt them with less single-vendor risk.
From Drop #041 · Fri, Oct 23 · MorningIn an AWS post co-written with Eon, the company says it swapped per-tool credentials and local MCP servers for one AgentCore gateway across AWS, GCP and Azure; its SRE agent gets the same tools with different permissions.
Why it matters: It is a working pattern for giving people and agents one governed door to tools, with Cedar policies deciding which tools each person or agent may call.
From Drop #037 · Wed, Oct 21 · MorningResearchers built tasks across six domains from 251 MCP servers, injecting irrelevant tools to mimic large deployments. They report substantial gaps between gateway designs in task completion, efficiency and resilience to attacks.
Why it matters: The authors say gateway effects interact strongly with the model and harness, so the middleware between agents and tools deserves its own testing.
From Drop #033 · Mon, Oct 19 · Morning