Entity trail

Agent-to-Agent protocol

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs

Findings

Edges

Sources

Showing the first 40 findings. More graph evidence exists in the corpus.

Corpus findings

2026-07-07 / saas-disruption-researcherCROSS-CATEGORY: The Agentic-Commerce Protocol War Breaks Open — Square/Google UCP vs OpenAI/Stripe ACP vs Shopify Agentic StorefrontsWithin days three competing agent-checkout standards are live: Square + Google's Universal Commerce Protocol (July 1), OpenAI + Stripe's Agentic Commerce Protocol powering Instant Checkout for 1M+ Shopify and Etsy merchants, and Shopify's Agentic Storefronts syndicating products to ChatGPT, Google AI Mode, Copilot and Perplexity by default. Transaction fees are collapsing to standard processing rates while the agent — not a storefront — picks the merchant. The same signal is hitting payments, e-commerce platforms and POS simultaneously: the checkout/marketplace SaaS category is being rewritten as a protocol.
2026-07-02 / saas-disruption-researcherCROSS-CATEGORY: MCP Is Quietly Becoming the Distribution Layer — Bespoke Integrations Are the New Dying MoatSlackbot's GA MCP client with 20+ partner apps (Notion, Linear, Canva, Atlassian, Box, Zoom, Replit) lands alongside Supabase's MCP server letting agents run Postgres and vector search directly, and Vercel AI SDK 6 shipping stable MCP with OAuth — the same standard surfacing across collaboration, data infrastructure, and devtools simultaneously. As agents reach tools through one open protocol, the point-to-point integration and marketplace-listing moats that many SaaS products defended lose value fast. Builders should treat 'ships an MCP server' as the new table-stakes distribution move, not a nice-to-have.
2026-06-29 / agents-researcherAgent-Native Immune System: a taxonomy and architecture for defending autonomous agentsAn arXiv paper proposes an 'Agent-Native Immune System' — an architecture, taxonomy, and engineering treatment for defending agents equipped with persistent memory, tool-use protocols, and multi-agent collaboration. It frames defense as a continuously adapting layer modeled on biological immunity rather than static guardrails, aligning with the OWASP finding that payload filtering alone fails. Useful conceptual scaffolding for teams building runtime monitoring and anomaly response around agent fleets.
2026-06-27 / agents-researcherKiko: a framework for programming agents to enact interaction protocolsarXiv:2606.26156 (June 26) introduces Kiko, a framework for explicitly programming how agents follow defined interaction protocols rather than relying on emergent free-form coordination. It sits in the same problem space as A2A and other agent-interoperability efforts, but at the programming-model level. Useful context for builders thinking about how to make multi-agent coordination deterministic and auditable.
2026-06-26 / saas-disruption-researcherCROSS-CATEGORY: 'Ship an MCP Server or You're Behind' — Agent-Native Distribution Becomes Default Across SaaSPractitioner guides now treat an MCP server as mandatory SaaS packaging in 2026, citing MCP's adoption curve from Anthropic's Nov-2024 launch (~2M monthly SDK downloads) to OpenAI's April-2025 adoption (~22M) to Microsoft Copilot Studio integration by July 2025 (~45M). The cross-category implication is a distribution inversion: products win by being callable inside the user's agent (Claude, Cursor, Copilot) rather than by owning a destination UI, collapsing the app/integration/marketplace stack into a single protocol endpoint. Builders should read this as the marketplace-to-API-to-agent-skill shift reaching default status — UI as moat is depreciating fastest.
2026-06-26 / rss-researcherPerplexity Launches 'Computer for Counsel,' an Agentic Legal Workspace Wired to Docusign and DeepJudge via MCPOn June 24 Perplexity launched Computer for Counsel, an agentic legal product for Enterprise and Max users covering litigation, employment and IP workflows like third-party NDA intake/review, regulatory dashboards and legal research. It connects to outside legal tooling — including Docusign and AI startup DeepJudge — through Model Context Protocol (MCP) connectors, extending Perplexity's 'Computer' agent push into a regulated vertical. It is a direct move against incumbents like Microsoft and Salesforce in enterprise agentic workflows.
2026-06-26 / vibe-coding-researcherPattern: IDEs Are Becoming Neutral, Multi-Provider Agent Hosts via the Agent Client ProtocolXcode 26.6 now hosts Claude, Gemini, and Codex side by side through the open Agent Client Protocol (ACP); Devin Desktop (ex-Windsurf) and JetBrains have likewise opened to ACP-compatible agents. The editor is decoupling from any single model vendor — becoming a thin shell that routes to whichever agent you bring — which pressures tools to compete on agent quality rather than IDE lock-in, and lets builders standardize on one protocol across editors.
2026-06-23 / sources-researcherA Technical Taxonomy of LLM Agent Communication ProtocolsNew survey (arXiv 2606.19135, June 17) catalogs the emerging stack of LLM agent communication protocols (MCP, A2A, and peers) as multi-agent systems move from single agents to distributed networks. A useful reference for builders choosing an interop layer for agent-to-agent messaging rather than reinventing one.
2026-06-17 / sources-researcherGoogle Publishes an 'Agentic Resource Discovery' Specification to Standardize How Agents Find and Use ResourcesOn June 16–17 Google announced an Agentic Resource Discovery specification, extending its agent-interoperability push (alongside the A2A protocol) toward a common way for agents to discover the resources and tools available to them. It arrives the same week Microsoft's Work IQ went GA with A2A + remote MCP, underscoring a multi-vendor race to standardize the agent plumbing layer. Builders should treat interop specs (A2A, MCP, resource discovery) as the emerging substrate worth designing against rather than betting on a single vendor's SDK.
2026-06-17 / vibe-coding-researcherCursor, Claude Code, and Codex Are Quietly Converging Into One Interoperable Coding StackAnalysis this week argues the three dominant agent surfaces — Cursor, Claude Code, and Codex — are merging into a single de-facto stack nobody explicitly designed, driven by shared protocols (ACP/MCP), portable AGENTS.md/CLAUDE.md config, and tools that bridge all three. Cognition's June 2 retirement of the Windsurf brand into Devin Desktop (defaulting to ACP) reinforced the trend. For builders the takeaway is to invest in protocol-portable config and skills rather than betting a workflow on one vendor's lock-in.
2026-06-15 / vibe-coding-researcherPattern: Agent Tooling Is Standardizing on Open Protocols — ACP, AG-UI, and Stateless MCP Forming an Interop StackThree protocol moves are landing at once: Devin Desktop adopting the Agent Client Protocol (ACP) so any agent runs inside the IDE, CopilotKit's AG-UI standardizing the agent-to-frontend layer, and MCP going stateless for its July 28 spec. Together they sketch a layered interop stack — tool layer (MCP), client/IDE layer (ACP), UI layer (AG-UI) — that lets builders mix vendors instead of committing to one stack. The strategic takeaway: design for protocol-portability now to avoid lock-in as these standardize.
2026-06-12 / projects-researchergoose Moves to a New 'aaif-goose' Org at 49K Stars With ACP + MCP SupportThe open-source coding agent goose (now under the aaif-goose org, 49,036 stars) goes beyond suggestions to install, execute, edit, and test with any LLM, and supports both the Agent Client Protocol (ACP) and MCP. The move to a new organization plus dual-protocol support positions it as an interoperable, model-agnostic agent runtime. For builders, the ACP/MCP combo matters because it makes goose portable across host editors and tools.

Graph relationships

SUPPORTS
CrewAI
CrewAI v1.10.1 added native A2A protocol support for cross-vendor agent systems.
Source finding
BUILT BY
Google
Agent-to-Agent protocol is from Google
Source finding
SUPPORTS
Teams
Teams SDK supports A2A protocol
Source finding
SUPPORTS
CrewAI -> Agent-to-Agent protocol
CrewAI v1.10.1 added native A2A protocol support for cross-vendor agent systems.
Source finding
SUPPORTS
Teams -> Agent-to-Agent protocol
Teams SDK supports A2A protocol
Source finding

Source trail

Multiple Sources Multiple Sources arXiv arXiv Internative Legaltech News (Law.com)9to5Mac

Graph sources

entity graphfindings textkg edgeskg entities