agent-plugins.org

--- title: Compatible Clients description: Explore clients that support the portable Agent Plugins format and the components each client can load. type: overview --- # Compatible Clients Agent Plugins clients can adopt portable component types incrementally. The clients below document the components and MCP transports they support. <CompatibleClients /> --- title: Agent Plugins description: A portable package format for reusable components that extend AI agents. --- # Agent Plugins 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](https://agentskills.io/specification) and [MCP servers](https://modelcontextprotocol.io/specification) that compatible clients can discover and load consistently. ## Why Agent Plugins? [#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 [#the-portable-package] An Agent Plugin is a directory with a required manifest and optional components in fixed locations: ```text my-plugin/ ├── plugin.json ├── skills/ │ └── summarize/ │ ├── SKILL.md │ ├── scripts/ │ └── references/ ├── mcp.json └── com.example.client/ └── hooks/ ``` * `plugin.json` identifies the plugin and the Agent Plugins version it targets. * `skills/` contains Agent Skills in the format defined by the Agent S