AWS supports Agent Plugins: the new open standard for portable AI agents

AWS announced official support for Agent Plugins, an open standard created to make AI agent extensions portable across platforms. The goal is to allow a plugin developed for an agent to work in another environment without major rewrites. The decision, published on the company’s open source blog (read the original announcement), places interoperability at the heart of AWS’ strategy for the AI ecosystem.

What is the Agent Plugins pattern?

Agent Plugins is an open specification for packaging and connecting extensions — tools, connectors and skills — to AI agents in a standardized manner. Instead of each provider creating their own plugin format, the default establishes a common contract for developers to write once and use on multiple agents. AWS joins this effort with the commitment to contribute to the evolution of the specification.

Why does AWS support the Agent Plugins standard?

The movement reinforces the position already defended by AWS in relation to other open standards, such as MCP (Model Context Protocol), ACP (Agent Client Protocol) and x402. By supporting multiple specifications, the company reduces the risk that its customers will be trapped in an agent-owner ecosystem. In practice, Agent Plugins support is an extra part in this interoperability umbrella.

Agent Plugins Impact for Brazilian Devs

For developers in Brazil, the immediate gain is less rework. Instead of adapting the same extension to AWS, Azure, Google or other platform, just follow the open format and plug where necessary. This also makes room for smaller teams to create plugins that meet multiple markets, without needing tailor-made integrations for each supplier.

Agent Plugins vs MCP: understand the relationship

MCP focuses on connecting models to tools and context; ACP works in communication between agents and customers; x402 deals with payments and digital rights. Agent Plugins complements the set by standardizing the packaging of the extension itself. For those who follow the industry, reading is clear: the industry is converging to a common layer instead of exclusive APIs. This concern with technological dependencies also appears in the discussion about Sovereign IA: The Myth of Control and Reality of Dependencies.

Frequently Asked Questions about Agent Plugins

What exactly is Agent Plugins?

It is an open standard for AI agent extensions, allowing plugins to be ported across different platforms without relying on a single provider.

Does Agent Plugins replace MCP?

Nope. AWS reinforces that Agent Plugins adds to standards such as MCP, ACP and x402 — together they cover different layers of interoperability of agents and tools.

Will AWS abandon proprietary APIs?

The ad does not indicate abandonment of its own APIs, but rather support an open standard that coexists with AWS solutions. The guideline is to expand the client's portability and freedom of choice.