Skip to content

MCP Servers

Model Context Protocol (MCP) is an open protocol that standardises how applications provide context to LLMs. With MCP, Kiro can connect to various data sources and tools through MCP servers, extending its capabilities beyond built-in features. This allows Kiro to interact with databases, APIs, file systems, and other services in a standardised way.

AWS provides 50+ MCP servers for interacting with AWS services. Find the full catalog at awslabs.github.io/mcp.

AWS MCP Servers website showing available MCP server options

Essential for any AWS development:

ServerPurpose
AWS DocumentationGet latest AWS docs and API references
AWS KnowledgeDocumentation, code samples, official content
  1. Add MCP server configuration

    To define MCP servers, add them as you normally would in any MCP client. The configuration follows the standard MCP format.

    MCP server configuration in Kiro

  2. Example configuration

    Here’s an example MCP server configuration for AWS Documentation:

    {
    "mcpServers": {
    "aws-docs": {
    "command": "uvx",
    "args": ["awslabs.aws-documentation-mcp-server@latest"],
    "env": {
    "AWS_PROFILE": "default"
    }
    }
    }
    }
  3. Restart Kiro

    After adding configuration, restart Kiro to load the new MCP servers.

For common use cases, consider using Kiro Powers instead:

FeatureMCP ServersPowers
SetupManual JSON configOne-click install
IncludesTools onlyTools + Steering + Hooks
FlexibilityFull controlPre-configured
Best forCustom setupsCommon workflows

With the AWS Pricing MCP Server configured, you can estimate costs before deploying:

"Estimate the monthly cost for running 3 t3.medium EC2 instances
with 100GB EBS storage each in ap-southeast-2"

Kiro will query current AWS pricing and provide a detailed cost breakdown.

With Steering Docs, Agent Hooks, Powers, and MCP Servers configured, Kiro is now equipped with the tools and knowledge it needs. Let’s start executing the build tasks.