Kiro MCP โ Connecting External Tools
What is MCP?
Section titled โWhat is MCP?โModel Context Protocol (MCP) is an open standard developed by Anthropic that allows AI systems to connect to external data sources, APIs, and tools. In Kiro, MCP gives the AI agent access to live information beyond whatโs in your codebase โ database schemas, project management tickets, version control history, cloud resources, and more.
Think of MCP servers as plugins that extend what Kiro can see and do:
Kiro AI Agent โ โโโ [Your Codebase] โ always available โโโ [MCP: GitHub] โ reads issues, PRs, repos โโโ [MCP: Jira] โ reads tickets, sprints, epics โโโ [MCP: SQL Server] โ reads live schema, runs queries โโโ [MCP: GitLab] โ reads pipelines, merge requestsWithout MCP, Kiro only knows whatโs in your open files and project. With MCP, it can look up a Jira ticket by ID, check your actual database schema before generating migrations, or read a GitHub issue before writing code to fix it.
MCP vs Built-in Context
Section titled โMCP vs Built-in Contextโ| Without MCP | With MCP | |
|---|---|---|
| Database schema | Must paste it manually | Kiro queries it live |
| Jira ticket details | You describe the ticket | Kiro reads the ticket directly |
| GitHub issue | You summarize it | Kiro fetches full thread |
| AWS resources | You explain the setup | Kiro reads from AWS |
How MCP Works in Kiro
Section titled โHow MCP Works in KiroโKiro uses MCP servers as background processes that it can call during a conversation. When you say โImplement the feature described in PROJ-1234โ, Kiro:
- Recognises the ticket reference
- Calls the Atlassian MCP server to fetch PROJ-1234
- Reads the ticket description, acceptance criteria, and comments
- Uses that context when writing the spec and code
Configuring MCP in Kiro
Section titled โConfiguring MCP in KiroโMCP servers are configured in Kiroโs settings UI or via a .kiro/mcp.json file in your project root.
Via Kiro Settings UI
Section titled โVia Kiro Settings UIโ- Open Kiro โ Settings (gear icon)
- Navigate to MCP Servers
- Click Add MCP Server
- Choose the server type or enter custom config
Via .kiro/mcp.json
Section titled โVia .kiro/mcp.jsonโCreate a file at .kiro/mcp.json in your project root:
{ "mcpServers": { "github": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-github"], "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_TOKEN}" } }, "atlassian": { "command": "npx", "args": ["-y", "@atlassian/mcp-atlassian"], "env": { "JIRA_URL": "https://your-org.atlassian.net", "JIRA_EMAIL": "${JIRA_EMAIL}", "JIRA_API_TOKEN": "${JIRA_API_TOKEN}" } } }}Environment variables prefixed with ${...} are resolved from your shell environment โ keep secrets out of the file and in your environment instead.
MCP Server Lifecycle
Section titled โMCP Server LifecycleโEach MCP server runs as a separate process that Kiro starts and stops automatically:
Kiro starts โ MCP servers launch in backgroundUser makes request โ Kiro calls relevant MCP server(s)Kiro session ends โ MCP servers shut downServers are only contacted when Kiro determines theyโre relevant to the current task. They donโt run continuously or consume resources when idle.
Checking MCP Status
Section titled โChecking MCP StatusโIn Kiro, you can see which MCP servers are connected and healthy:
- Kiro panel โ look for the MCP indicator (plug icon)
- Green = connected and responding
- Red = failed to start (check credentials and server package)
- Grey = not yet needed (will start on first relevant request)
Security Considerations
Section titled โSecurity Considerationsโ- Never commit API tokens or credentials to
.kiro/mcp.jsonโ use environment variable references - Add
.kiro/mcp.jsonto.gitignoreif it contains any org-specific URLs you donโt want shared - MCP servers run locally โ credentials are not sent to Kiroโs cloud servers, only to the target service (Jira, GitHub, etc.)
- Review what permissions each MCP server requests โ some can write as well as read
Available MCP Integrations
Section titled โAvailable MCP IntegrationsโThe following pages cover the most common MCP servers used with Kiro:
- Atlassian MCP โ Jira and Confluence
- GitHub MCP โ Issues, PRs, and repositories
- GitLab MCP โ Merge requests and pipelines
- SQL Server MCP โ Database schema and queries