AIToday
Large Language ModelsAI Coding AssistantsOpen-Source AITHE DECODERPublished: Aug 7, 2026, 19:00 JST

Amazon, Microsoft, OpenAI back shared AI agent plugin standard

Amazon, Microsoft, OpenAI back shared AI agent plugin standard

3 Key Points

  1. What happened

    Amazon, Cursor, Microsoft, OpenAI, and Vercel have created Agent Plugins, an open standard that defines a single package format for AI agent extensions. The standard uses a directory with a manifest file called plugin.json and supports two components: Agent Skills (reusable instructions and workflows) and MCP servers (connections to tools and data).

  2. Why it matters

    Until now, each product used its own formats and setup processes, forcing developers to rebuild extensions for every platform. A shared standard lets developers bundle and reuse their work across multiple platforms, removing friction for extension creators.

  3. What to watch

    The spec is being developed openly on GitHub and currently covers only packaging and discoverability—it does not yet address marketplaces, permissions, or runtime environments. Notably, Anthropic, which created the Model Context Protocol and Agent Skills standards, is not part of the effort despite having added its own plugin system to its Cowork tool.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The Agent Plugins initiative addresses a real friction point in the emerging AI agent ecosystem: the fragmentation of extension formats across competing platforms. Each vendor—Amazon, Microsoft, OpenAI, Vercel, and Cursor—has built or is building agent tooling, yet they had no way for developers to write once and deploy everywhere. By agreeing on a shared manifest structure and package format, these five companies are making a bet that reducing developer burden will accelerate ecosystem growth.

The standard is deliberately narrow: it specifies only how to package and discover plugins, deferring harder questions like permissions, marketplaces, and runtime behavior to a later phase or to individual platforms. This pragmatic scoping increases the chances of adoption while leaving room for platforms to differentiate on commercial and security features.

One striking absence is Anthropic, which created both the Model Context Protocol (MCP) and Agent Skills as open standards and recently launched its own agentic tool, Cowork. Despite Anthropic's foundational role in these standards, it did not join the coalition. This gap may reflect either independent strategy or unresolved technical or commercial alignment questions.

FAQ
What does the Agent Plugins standard actually define?
It defines a single package format using a directory with a manifest file called plugin.json. Version 1.0.0 supports two components: Agent Skills (reusable instructions and workflows) and MCP servers (connections to tools and data).
Why was this standard needed?
Until now, every product relied on its own formats, folder structures, and setup processes, forcing developers to rebuild their extensions for each platform separately.
What does the standard not cover?
The standard only covers packaging and discoverability; it does not address marketplaces, permissions, or runtime environments.

Get the latest Large Language Models news every morning

For example, today's edition would include:

  • Agentic AI pushes identity to front of data security, Oracle saysSiliconANGLE AI · 1h ago
  • Momentic launches Mo, an AI agent that tests apps without scriptsSiliconANGLE AI · 1h ago
  • Qiagen grounds drug discovery agents in 25+ years of curated dataSiliconANGLE AI · 1h ago

AI-summarized, only the topics you pick: one digest a day via Email, LINE, or Slack.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleAI agent breach exposes enterprise security gap, not model origin