Why we're building on the Agent Plugins standard
Blog post from Speakeasy
Speakeasy is adopting the newly released Agent Plugins 1.0 standard as the portable foundation for distributing AI agent skills and MCP server configurations across different clients such as Cursor, Codex, and future compatible tools. The company argues that fragmented, client-specific packaging creates costly duplication, version drift, and limited tool choice for enterprise teams, while the standard defines a minimal common package containing a manifest, skills, and MCP definitions without attempting to standardize marketplaces, installation, permissions, or credentials. Speakeasy plans to compete in the layers above the package format, including registries, policy-based distribution, versioning, governance, compliance, and usage analytics, while allowing customers to export open-standard packages without vendor lock-in. It emphasizes that credentials are excluded from packages and handled through client-side OAuth, and that curated plugins remain valuable in enterprises because they provide role-specific, approved tools and access rather than relying on ungoverned discovery. Because the specification is new and incomplete, Speakeasy is pinning support to a specific revision, retaining provider-native functionality for unsupported features such as hooks or certain private credential models, and including legacy manifests for older clients.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Agent Plugins | 8 | 60 | 5 | 4 | - |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.