Loading image...Kiro
  • CLI
  • Powers
  • Autonomous agent
  • Enterprise
  • Pricing
  • Docs
SIGN INDOWNLOADS
Loading image...Kiro
Loading image...Kiro
Product
  • About Kiro
  • CLI
  • Pricing
  • Downloads
For
  • Enterprise
  • Startups
Resources
  • Documentation
  • Blog
  • Changelog
  • FAQs
  • Report a bug
  • Suggest an idea
  • Billing support
Social
Site TermsLicenseResponsible AI PolicyLegalPrivacy PolicyCookie Preferences
  1. Docs
  2. Autonomous agent
  3. Sandbox
  4. MCP

MCP

On this page
  • Configuration
  • Example configuration
  • Supported servers
  • Using environment variables and secrets

The MCP (Model Context Protocol) configuration is loaded into the agent sandbox and available during task execution. This allows the agent to use specialized tools and access external data sources through MCP servers.

Important

MCP servers are third-party tools. Only install servers from trusted sources and review their documentation and licensing. Kiro is not responsible for third-party MCP servers.

Info

MCP servers require Open Internet access to function. Enabling network permissions exposes your environment to security risks. These include prompt injection attacks, extraction of code and secrets, introduction of malware or security flaws, and use of content that may violate licensing terms. Consider these risks carefully before enabling network permissions.

Configuration

MCP servers are configured in your MCP configuration file. The configuration is loaded when the sandbox starts and remains 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

Only local MCP servers are currently supported. Remote MCP servers are not available at this time.

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.

Page updated: December 2, 2025
Environment Variables
Environment Configuration