Major Players Unite: The Definitive Developer Appeal
The industry titans are making a strong push for developers to consolidate their agentic capabilities and tools into a unified format. Why? To distribute these superpowers across various platforms whenever the need arises. Just like when you’re shown the door, right? The objective is to achieve write once, run everywhere. Vercel initiated the process with the Agent Plugins specification, partnering with Amazon, Cursor, Microsoft, and OpenAI. The Linux Foundation’s Agentic AI Foundation (AAIF) swiftly joined in, operating as its own independent entity.
Delivering AI Impact: Agent Plugins 1.0
Agent Plugins 1.0 consolidates an AI agent’s capabilities and tools into a single organized directory structure. Constructed on the AAIF-managed MCP protocol, it leverages the open Agent Skills standard established by Anthropic in 2025. The Agent Skills contain the task blueprints, and MCP interfaces with external databases, APIs, shell scripts, and more. Together, they aim to make intelligent technology modular—write-once-run-anywhere, ideally. However, clients and platforms must still navigate the user interface, security, and marketplaces for these plugins. VS Code, Cursor, GitHub Copilot, ChatGPT, Codex, and Kiro have already embraced the standard.
File-System-As-Configuration: The Emerging Plug-In Wizard
Consider Next.js for Agent Plugins—utilizing the host machine’s directory structure to define components. The specification requires a top-level directory for each plugin, accompanied by a mini manifest and schema. The manifest provides the name, version, and schema in JSON format. Skills reside in the skills sub-directory, while the MCP server configuration is structured as an mcp.json file. Plugin developers can add extra elements into the namespace directory. This approach keeps everything organized without encompassing every quirky client experiment out there, per AAIF. Associating skills with MCP configuration allows for transfer to any compatible agent client.
Streamlining the Focus: Tightening the Plugin Scope
Developers are experimenting with various hooks, rules, and extensions at an intense pace. However, the guardians of the specification declared a halt, keeping things “narrow” for the 1.0 release, in accordance with AAIF. Future iterations may incorporate the finest elements, but no guarantees, folks. Developers can incorporate extensions into the namespace and hope for portability. Going forward, it will be managed under open governance, with a technical oversight committee at the helm, welcoming public input. Leading experts from Amazon, Cursor, Microsoft, OpenAI, and Vercel form the core team. The specification is accessible under the Creative Commons Attribution 4.0 International License (CC-BY-4.0).
Additional Initiatives: Taming the Tech Frontier
There are further efforts to control this chaotic agent development landscape. Google contributed its Agent2Agent (A2A) protocol to AAIF. It is also developing the Agentic Resource Discovery specification for locating tools on the web. AAIF has a related project, Skills Over MCP, which consolidates skills into the MCP server. It’s akin to delivering “the manual alongside the product,” observes AAIF Vice President Angie Jones. Should MCPs showcase skills, or should each skill set have its own MCP? Let’s watch who prevails!
Conclusion: The Grand AI Plugin Clash!
It’s an epic clash in the tech realm. The major players are adopting a diplomatic approach, attempting to establish a universal plugin specification. The aim? Global peace—er, I mean, technological harmony. Who knows if it will succeed, but watching their efforts is quite entertaining. As they say in Newcastle, if you can’t lend a hand, take a seat and enjoy the spectacle!
