Lab 6: MCP Mini (Optional)

MCP as a universal adapter

← Back to overview

Status: Optional Mode: Chat + MCP Duration: approx. 10-15 minutes Shows: extend Kiro's reach with an external tool

Please read first: This lab is optional and can be skipped entirely.

The lab requires internet and the tool uvx from the Python package manager uv. In many training environments uv cannot be installed (missing permissions, locked-down network, no internet). That is perfectly fine.

If you cannot install uvx, then skip this lab. The trainer will show it as a short demo if needed. You won't miss anything fundamental: the principle of MCP becomes clear in the demo too.

Goal

Connect an external MCP server (the AWS documentation) and ask a question that Kiro answers via this tool. This makes visible how MCP "docks on" additional capabilities.

Check the prerequisite

In the terminal:

uvx --version
  • A version appears → continue with Step 1.
  • Error "not found" → install uv (see uv installation guide) or treat the lab as a demo.

Step 1 – Configure the MCP server

Create the workspace configuration .kiro/settings/mcp.json:

{
  "mcpServers": {
    "aws-docs": {
      "command": "uvx",
      "args": ["awslabs.aws-documentation-mcp-server@latest"],
      "env": {
        "FASTMCP_LOG_LEVEL": "ERROR"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Alternatively globally under ~/.kiro/settings/mcp.json. On first start uvx downloads the server automatically — there is no "uvx install" action.

Step 2 – Connect the server

  • Kiro detects the changed mcp.json automatically (hot-reload on save).
  • If needed: in the Kiro panel (ghost icon) → MCP Servers → reconnect the server, without restarting Kiro.
  • The server should appear as "connected" and show its tools.

Step 3 – Ask a question that uses the tool

Search the AWS documentation for how to create an S3 bucket with the AWS CLI,
and summarize the steps briefly.
  • Observe: Kiro automatically picks the matching MCP tool (doc search) and uses its result.
  • On first use Kiro may ask for permission for the tool (confirm).

Expected result

Kiro answers the question with information from the AWS documentation that it fetched via the MCP server — a tool that was not part of Kiro before.

Key takeaways

  • MCP is a universal adapter (like USB-C): the same interface for many tools.
  • Local MCP servers (files, internal DBs/APIs) keep data in the network; remote servers (docs, cloud) need internet.
  • Security rule: sensitive/internal data only via local servers; auto-approve only for trusted, read-only tools (leave autoApprove empty deliberately and confirm individually).
  • Powers go one step further: they bundle MCP tools + steering + skills and load on-demand (one-click install) — ideal to avoid context overload.

Want more? Kiro can do much more than write code. On the Creative Ideas with Kiro page we show examples: combine data from several sources, cut news down to the essentials, or automation via AWS services like EventBridge and Bedrock.