Agent Plugins<br>Skip to contentSearch...⌘K

Agent PluginsCompatible ClientsFor Plugin Authors<br>Build an Agent PluginPlugin manifestSkillsMCP serversClient extensionsFor Client Implementers<br>Implement an Agent Plugins clientLoading and discoveryMCP runtimeClient conformance checklistReference<br>Agent Plugins SpecificationJSON Schemas

Agent Plugins<br>A portable package format for reusable components that extend AI agents.<br>Agent Plugins is an open, vendor-neutral standard for packaging reusable components into portable plugins. Its version 1.0.0 specification defines a shared format for Agent Skills and MCP servers that compatible clients can discover and load consistently.

Why Agent Plugins?

AI agent clients have developed their own plugin formats, even when plugins contain the same underlying components. Authors must rearrange or duplicate those components for each client, so a plugin packaged for one client may need adaptation before another can use it.

Agent Plugins defines a small interoperability floor for the parts that can be portable across clients. Shared components can use one predictable structure, while distribution, installation, permissions, user experience, and client-specific capabilities remain under each client's control.

The portable package

An Agent Plugin is a directory with a required manifest and optional components in fixed locations:

code]:grid [&>code]:min-w-max shiki shiki-themes github-light github-dark shiki shiki-themes github-light github-dark" style="--shiki-light:#24292e;--shiki-dark:#e1e4e8;--shiki-light-bg:#fff;--shiki-dark-bg:#24292e" tabindex="0">my-plugin/<br>├── plugin.json<br>├── skills/<br>│ └── summarize/<br>│ ├── SKILL.md<br>│ ├── scripts/<br>│ └── references/<br>├── mcp.json<br>└── com.example.client/<br>└── hooks/

plugin.json identifies the plugin and the Agent Plugins version it targets.

skills/ contains Agent Skills in the format defined by the Agent Skills specification.

mcp.json describes stdio, Streamable HTTP, or legacy HTTP+SSE MCP servers.

Reverse-domain extension namespaces let individual clients add behavior without changing the portable core.

Open development

Agent Plugins is openly licensed and developed in public. Its initial Technical Steering Committee includes Core Maintainers from Amazon, Cursor, Microsoft, OpenAI, and Vercel.

Proposals and technical decisions are public, and participation is open to the broader ecosystem. Ideas for new features and material changes begin in GitHub Discussions, where proposals can establish a concrete portability need and implementer support.

Explore the specification, schemas, governance, and contribution process in the Agent Plugins specification repository.

Choose your path

Build a plugin<br>Create a portable package with skills and MCP servers.

Implement a client<br>Load, validate, and run Agent Plugins safely.

Read the specification<br>Consult the complete normative specification.

Browse the schemas<br>Use the canonical plugin and MCP JSON Schemas.

Compatible Clients

Explore clients that support the portable Agent Plugins format and the components each client can load.

On this page<br>Why Agent Plugins?The portable packageOpen developmentChoose your path

GitHubEdit this page on GitHubScroll to topCopy pageOpen in chat