Install powers from curated partners, the community, or your team's private tooling. Kiro supports both the Agent Plugins format (plugin.json) and the legacy format (POWER.md) — the installation experience is the same regardless of format.
Browse powers from our official registry including Datadog, Dynatrace, Figma, Neon, Netlify, Postman, Supabase, Stripe, Strands SDK, and AWS Aurora.
You can now Try the power to run through the power onboarding. Any time you ask a question related to that power, the Kiro agent will automatically activate and use it.
When you install a power that includes Model Context Protocol (MCP) integrations, Kiro automatically namespaces server names to avoid conflicts and manages the MCP servers for you.
~/.kiro/settings/mcp.json file. They activate and deactivate with the power.~/.kiro/settings/mcp.json configuration file under the Powers section.Each power must have a valid plugin.json or POWER.md file at its package root. A single repository can contain multiple powers, each in its own directory.
For powers you create or manage in private repositories, clone the repository locally and install from the local path.
Example structure (Agent Plugins format):
my-custom-power/ ├── plugin.json # Required manifest ├── mcp.json # Optional MCP server configuration └── skills/ # Optional Agent Skills └── setup/ └── SKILL.md
To update a power to the latest version:
The power refreshes from the remote repository and applies the latest version.
Install powers