Agentic AI
Major AI Platforms Converge on Shared Plugin Standard for Portable Agent Extensions
OpenAI, AWS, Microsoft, GitHub, and Cursor have jointly adopted Agent Plugins 1.0.0, a vendor-neutral format that lets developers build AI agent extensions once and deploy them across multiple platforms—though security concerns remain.
The New Stack
Five major technology companies have aligned behind a new open standard that promises to simplify how developers build and distribute extensions for AI agents. Agent Plugins 1.0.0 represents the first coordinated effort by OpenAI, AWS, Cursor, GitHub, and Microsoft to establish a common format for packaging reusable AI agent capabilities.
The move was led by Vercel, an agentic infrastructure platform that proposed the standard and released the full technical specifications this week. Unlike previous approaches where each platform required its own packaging format, Agent Plugins creates a single, portable standard that combines Agent Skills (modular AI capabilities designed for reuse) and MCP servers (tools that connect agents to external services) into a distributable package.
Why one standard matters for developers#
Currently, developers face fragmentation when building agent extensions. To work across ChatGPT, VS Code, GitHub Copilot, and Cursor, they must package the same functionality in multiple proprietary formats tailored to each platform's requirements. Agent Plugins solves this by defining a minimal, universal contract: a plugin.json manifest file paired with standardized component locations.
Jonathan Hefner, a member of Vercel's technical staff, notes that the standard "leaves installation, distribution, policy, user experience, and client-specific capabilities to each client"—meaning vendors retain autonomy over how they deploy and manage plugins, but all agree on the structural format.
Real-world use cases driving adoption#
In practice, AI agents need to connect to live systems. Developers use plugins to bridge agents with:
- Enterprise tools: GitHub, Jira, Slack, Figma
- Data sources: Real-time analytics, databases, schema metadata
- APIs and services: Payment processors like Stripe or Adyen, weather and mapping services
- Hardware and local environments: USB interfaces, microservices, edge deployments
The standard is explicitly vendor-neutral, with open governance, public contribution processes, and transparent technical decisions that no single company can override.
