Introducing Agent Plugins 1.0.0

Agent Plugins 1.0.0 is now available. Vercel introduced it as an open, vendor-neutral standard for packaging Agent Skills and MCP servers into portable plugins. Compatible agent clients can discover and load those plugins without each vendor inventing a private packaging scheme.

Technically, Agent Plugins defines a common format built around a root plugin.json manifest and fixed locations for portable components. Skills and MCP servers travel together in that layout so a client that understands the standard can find what to load. Installation, distribution, policy, user experience, and client-specific capabilities stay under each client’s control; the standard standardizes packaging and discovery, not the full product surface.

For engineers and builders, that split matters. You can ship a skill or an MCP server once in a portable plugin and expect any compatible client to discover and load it, instead of rewriting packaging for every host. You still meet each client on its own terms for install paths, policy gates, and UX, so multi-client work is packaging-first rather than full product fork.

The competitive context is a fragmented agent stack: Skills, MCP servers, and host-specific loaders have not shared one packaging contract. A vendor-neutral 1.0.0 from Vercel aims at interoperability without forcing a single store or runtime. Clients that keep distribution and policy local can adopt the format without giving up control of how plugins reach users or what they may do.

Practical takeaway: treat Agent Plugins as the packaging and discovery layer for Skills and MCP servers when you need portability across compatible clients. Watch which clients actually implement discovery and load of plugin.json-based packages, and how each maps the shared format onto its own install, policy, and UX rules—that is where portability will either hold or fragment again.