Skip to main content

Powers and MCP

Kiro Web supports two ways to extend the agent with additional tools and context: Powers and MCP servers.

For general MCP configuration and concepts that apply across all Kiro surfaces, see MCP. For general Powers documentation, see Powers.

Powers are a set of integrations included with Kiro Web that add specialized tools and context to the agent. You can configure which Powers are enabled for your sessions. To manage Powers, including installing them from the catalog, go to Agent Config > Powers & MCP. You can also upload your own powers/ folder from Agent Config > Cloud Config with Configuration Sync.

MCP servers give you full control over custom tool integrations using the Model Context Protocol. You configure MCP servers manually and they are loaded into the sandbox at the start of each task.

MCP servers

Configuration

To add an MCP server:

  1. Go to Agent Config > Powers & MCP
  2. Under MCP server settings, click Add server
  3. Enter the server name, type (HTTP or local), and command or URL

MCP servers are loaded when the sandbox starts and remain available throughout task execution.

Example configuration

json
{ "mcpServers": { "aws-knowledge-mcp-server": { "command": "uvx", "args": [ "fastmcp", "run", "https://knowledge-mcp.global.api.aws" ], "env": {} } } }

Supported servers

Kiro Web supports local (stdio) and remote (HTTP/SSE) MCP servers. Local servers run as processes in the sandbox. Remote servers connect through a URL and can include headers. MCP settings are unavailable with Connections access only network mode. To change the network mode, see Internet access.

Using environment variables and secrets

You can reference environment variables and secrets in your MCP configuration to securely pass credentials and configuration values to MCP servers.

Use the ${key_name} syntax to reference the key names of your environment variables and secrets in the server configuration:

json
{ "mcpServers": { "server-name": { "command": "executable", "args": ["arg1", "arg2"], "env": { "ENV_VAR_KEY": "${my_env_var_key}", "SECRET_KEY": "${my_secret_key}" } } } }

Both environment variables and secrets use the same syntax. The values are resolved when the sandbox starts.

Power authentication (OAuth)

Some Powers connect to third-party services — such as Figma, Stripe, or Supabase — that require you to grant access through an OAuth authorization flow. You complete this once when you install the Power, and the agent uses the connection for all future tasks without prompting you again.

Which Powers require authorization

When you install a Power that needs OAuth, an Authorize button appears next to it in the Powers list. Powers that don't require authorization are ready to use immediately after installation.

Authorizing a Power

  1. Go to Agent Config > Powers & MCP
  2. Find the Power you want to connect and choose Authorize
  3. A new browser tab opens showing the service's consent screen
  4. Review the requested permissions and approve access
  5. You're redirected back to Kiro Web — the Power now shows as connected

After authorization, the agent can use the Power's MCP server in any task. You don't need to re-authorize unless you disconnect or the service revokes access.

Disconnecting a Power

If you no longer want a Power to access a third-party service on your behalf:

  1. Go to Agent Config > Powers & MCP
  2. Find the Power and choose Disconnect

Disconnecting immediately revokes the stored credentials. The Power remains installed but its tools that require the connection will stop working until you authorize again.

Security

  • Tokens are encrypted at rest and never exposed to the sandbox or the agent
  • Access is scoped to the permissions you approved on the consent screen
  • You can disconnect a Power at any time to immediately revoke access
Page updated: October 21, 2026