# Introducing Agent Plugins

DevFeed: [Introducing Agent Plugins](<https://devfeed.tech/articles/introducing-agent-plugins-759.md>)

Original publisher: [Read original article](<https://vercel.com/blog/introducing-agent-plugins>)

Author: Jonathan Hefner

Published: 2026-08-06T00:00:00Z

Content type: article

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [Model Context Protocol (MCP)](<https://devfeed.tech/topics/model-context-protocol-mcp.md>), [MCP Server](<https://devfeed.tech/topics/mcp-server.md>), [JSON](<https://devfeed.tech/topics/json.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Extension](<https://devfeed.tech/topics/extension.md>)

Tags: [agent-skills](<https://devfeed.tech/tags/agent-skills.md>), [json](<https://devfeed.tech/tags/json.md>), [manifest](<https://devfeed.tech/tags/manifest.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [plugins](<https://devfeed.tech/tags/plugins.md>), [validation](<https://devfeed.tech/tags/validation.md>)

## AI overview

Agent Plugins 1.0.0 is an open, vendor-neutral standard for packaging Agent Skills and MCP servers into distributable plugins. It defines a directory structure with a plugin.json manifest and fixed component locations, while leaving installation, distribution, policy, user experience, and client-specific capabilities to individual clients.

## Source excerpt

Today, Agent Plugins 1.0.0 is publicly available. Agent Plugins is an open, vendor-neutral standard for plugins that extend AI agents. Agent Skills provide reusable instructions and resources for AI agents. MCP servers connect agents to tools and services. Both can be reused across clients, but clients often package and discover them differently. Agent Plugins gives compatible clients a common format: a directory with a plugin.json manifest and fixed locations for its components. The format is intentionally small and easy to implement, and it leaves installation, distribution, policy, user experience, and client-specific capabilities to each client. One package for the portable parts Extension authors often adapt the same component to several client formats. Even though the underlying Skill or MCP server is identical, clients often expect different top-level metadata, discovery paths, or MCP configuration. Agent Plugins gives those shared components one predictable, structured home: A minimal JSON manifest (plugin.json) identifies the specification version and names the plugin: Those two fields are the minimum requirement for the manifest, and the rest of the contract is represented in the file structure of the directory itself. A reusable component should not need to be repackaged for every client, so the format specifies only what a client needs to discover and load what is inside. Every compatible client checks for plugin.json at the plugin root. Clients that support Skills discover them under skills/. Clients that support MCP servers read their configuration from mcp.json. A client can support either component type or both. After the client validates the manifest, components are validated independently, so one invalid component does not disable unrelated ones. For plugin authors, that means fewer client-specific conventions for the same component. For client implementers, the specification defines a small, deterministic contract for discovery, validation, and lo