August 2026 Summaries

Speakeasy has added support for the Agent Plugins 1.0 standard, an open format backed by organizations including OpenAI, AWS, Microsoft, GitHub, Cursor, and Vercel that combines agent skills and MCP server definitions into a portable plugin package. Compatible Speakeasy plugins now publish once for use across supporting agents such as Cursor and Codex while preserving existing marketplace identities and legacy installation manifests for older versions. The standard uses a minimal manifest, standardized skills and MCP directories, and agent-specific extensions where needed, while leaving distribution, permissions, and credential management to individual agents. Speakeasy validates packages against a fixed version of the specification and prevents partial exports when a plugin contains unsupported configurations. Portable packages exclude credentials entirely, relying on agent-managed OAuth; plugins requiring embedded secrets, custom credential headers, or non-OAuth private MCP servers remain on provider-native packaging. Claude Code, OpenCode, and observability hooks continue to use native formats for now, while users can automatically receive the new format on their next compatible publish or download a standards-compliant ZIP for other supported agents.

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.