Oleksandr Kuzmenko, EditorPublished 4 min readAI-assisted · editor-reviewed
TL;DR
- Agent Plugins 1.0.0 standardizes directory layouts using a manifest named plugin.json.
- The standard unifies both Model Context Protocol tools and Agent Skills into a single distribution package.
- Major partners include Amazon, Cursor, Microsoft, OpenAI, and Vercel, establishing wide platform support.
Key facts
- Standard Version
- 1.0.0
- Manifest File
- plugin.json
- Supported Core Specs
- Agent Skills, Model Context Protocol (MCP)
- Founding Coalition
- Amazon, Cursor, Microsoft, OpenAI, Vercel
Source: Key facts — Standard Version
Source: Key facts. Standard Version: 1.0.0. Each figure is copied from the story.
- Standard Version1.0.0
Cross-Platform Packaging with plugin.json
The Agent Plugins specification defines a unified directory structure containing a central manifest named plugin.json. This format eliminates the need to maintain distinct packaging for different agentic IDEs and execution runtimes.
Core Supported Components
Version 1.0.0 focuses on two foundational components:
- Agent Skills: Bundling prompt instructions, workflows, and task definitions.
- Model Context Protocol (MCP) Servers: Standardizing external tool execution, API calls, and context retrieval.
Scope and Industry Adoption
Developed openly on GitHub, the standard strictly governs packaging and discoverability rather than runtime permissions or marketplace rules. Supported by Amazon, Cursor, Microsoft, OpenAI, and Vercel, it streamlines deployment across major AI coding and agent ecosystems.
Try it in 2 minutes
{
"name": "my-agent-plugin",
"version": "1.0.0",
"description": "Unified cross-platform plugin configuration",
"skills": ["./skills/code-review"],
"mcpServers": {
"database": {
"command": "node",
"args": ["./mcp/db-server.js"]
}
}
}When to use
- When building MCP servers or custom Agent Skills meant to run across multiple AI tools
- When standardizing extension deployment for engineering teams using Cursor and Vercel agents
When NOT to use
- When targeting desktop environments that strictly require proprietary extension formats like Anthropic Cowork
- When configuring runtime security models or enterprise access controls, which are out of scope for this spec
What to do today
- Consolidate local MCP server definitions and custom skill files into a unified directory structure.
- Create a plugin.json manifest to prepare custom agent workflows for cross-platform distribution.
Step names are taken from What to do today.
Step names are taken from What to do today. Consolidate local MCP server definitions and custom skill files into a unified directory structure.. Create a plugin.json manifest to prepare custom agent workflows for cross-platform distribution.
- Consolidate local MCP server definitions and custom skill files into a unified directory structure.
- Create a plugin.json manifest to prepare custom agent workflows for cross-platform distribution.