Agent Protocol: The Open Standard for AI Plugin Packaging
Agentic AIFive competing platforms rarely agree on anything — but they agreed on this.
What Happened
Amazon, Cursor, Microsoft, OpenAI, and Vercel have jointly released Agent Protocol, an open specification for packaging and distributing AI agent plugins across platforms. The standard uses a simple directory structure anchored by a plugin.json manifest file. Version 1.0.0 supports two component types: Agent Skills, which package reusable instructions and workflows, and MCP servers, which connect agents to external tools and data sources.
The specification is being developed openly on GitHub. Notably absent from the founding group: Anthropic, which created both the Model Context Protocol that Agent Protocol wraps, and its own Agent Skills standard. Anthropic recently launched a plugin system for its Cowork platform without joining this effort.
Why It Matters
The problem Agent Protocol targets has been quietly draining developer time since agentic platforms proliferated. Every environment that hosts AI agents has historically required its own folder structure, manifest format, and setup flow. Building a plugin for Cursor means reformatting it for OpenAI’s environment, then reformatting again for a Microsoft or Amazon integration. For teams shipping agentic tooling across multiple platforms, that redundancy compounds directly into shipping friction.
Version 1.0.0 deliberately scopes narrow — it avoids addressing marketplaces, permissions, or runtime environments. What it standardizes is the packaging and discoverability layer: how a plugin is described, structured, and discovered across platforms. That’s precisely where fragmentation has carried the highest per-platform tax.
Anthropic’s absence creates a structural wrinkle worth tracking. The specification wraps MCP servers directly, making Anthropic’s protocol the underlying transport layer even as Anthropic itself sits outside the governance process. The recent formalization of MCP governance through the Linux Foundation adds context here — the transport and packaging layers are now being standardized by overlapping but distinct coalitions.
What This Means for Builders
Developers building plugins for any of the five founding platforms can now structure their work once against the Agent Protocol specification and ship across all five environments without reformatting. The practical floor for participation in the agentic ecosystem drops materially when the packaging overhead is eliminated. Teams considering building agentic integrations today have a direct incentive to target Agent Protocol from the start rather than designing for a single platform and retrofitting later.
The So What
Agent Protocol is a narrow bet with compounding upside if it holds. The founding group’s breadth — spanning the two most widely deployed coding agents (Cursor, Codex), the leading cloud platforms (AWS, Azure), and the dominant model API provider — gives the specification enough gravity to become a de facto default. The durability question is whether the group expands scope carefully or fractures into competing Version 2 proposals. For now, the practical call is clear: build new plugins against this specification and watch whether Anthropic moves to join or counter it.
Source: The Decoder
Content created with AI assistance and reviewed for accuracy.
Join the conversation
Stack Insiders is our free community for readers who want to go deeper — share resources, ask questions, and connect with others across every vertical we cover.
Join Stack Insiders →