From “Kiro is an AI IDE” to “I can configure its MCP runtime.”
Kiro is the agent host. MCP is the bridge that gives the agent external tools, prompts, and resources. Configure servers in mcp.json, control permissions, and govern them in enterprise with a registry.
The one sentence
MCP is the standardized bridge to external capabilities.
Configuration tells Kiro how to start or connect to each server.
01 · What is MCP?
Source: kiro.dev/docs/mcp
What you can do
- Access specialized knowledge bases and docs
- Integrate external services and APIs
- Add domain-specific tools
- Use server-provided prompt/resource templates
Surfaces that support MCP
| Surface | Local | Remote |
|---|---|---|
| IDE | ✓ | ✓ |
| CLI | ✓ | ✓ |
| Web | ✓ | ✓ |
| Mobile | — | — |
Core roles
- Kiro — MCP client / agent host
- MCP server — process that exposes capability
- Transport — local stdio or remote HTTP/SSE
- Tool — callable action with schema
- Resource / Prompt — retrievable context or template
02 · Configuration — write this from memory
Sources: Configuration · CLI Configuration · MCP overview
Workspace (project-specific):
.kiro/settings/mcp.jsonUser (global):
~/.kiro/settings/mcp.json
{
"mcpServers": {
"fetch": {
"command": "uvx",
"args": ["mcp-server-fetch"],
"env": {
"SOME_KEY": "${SOME_KEY}"
},
"disabled": false,
"autoApprove": ["tool_name"],
"disabledTools": ["dangerous_tool"]
}
}
}
{
"mcpServers": {
"api-server": {
"url": "https://api.example.com/mcp",
"headers": {
"Authorization": "Bearer ${API_TOKEN}"
},
"disabled": false
}
}
}
Remote servers can also use OAuth. See agent configuration docs for oauth / oauthScopes.
{
"mcpServers": {
"fetch": {
"command": "uvx",
"args": ["mcp-server-fetch"]
},
"git": {
"command": "uvx",
"args": ["mcp-server-git"],
"env": {
"GIT_CONFIG_GLOBAL": "/dev/null"
}
},
"aws-docs": {
"command": "npx",
"args": ["-y", "@aws/aws-documentation-mcp-server"]
}
}
}
{
"name": "myagent",
"description": "My special agent",
"mcpServers": {
"fetch": {
"command": "fetch3.1",
"args": []
}
},
"includeMcpJson": false
}
includeMcpJson controls whether the agent also loads workspace + user mcp.json servers.
# Add a server (CLI) kiro-cli mcp add \ --name "awslabs.aws-documentation-mcp-server" \ --scope global \ --command "uvx" \ --args "awslabs.aws-documentation-mcp-server@latest" \ --env "FASTMCP_LOG_LEVEL=ERROR"
Property cheat sheet
| Property | What it does |
|---|---|
command | Executable Kiro launches for a local (stdio) server |
args | Arguments passed to that command |
env | Environment variables. Use ${VAR} for secrets |
url | Remote MCP endpoint (HTTP/SSE) |
headers | HTTP headers for remote servers |
disabled | Turn the server off without deleting it |
autoApprove | Tools that skip the approval prompt (use sparingly) |
disabledTools | Hide/block specific tools from the agent |
timeout | Request timeout in ms (supported in several surfaces) |
Loading priority
1. Agent config (
mcpServers in agent JSON)2. Workspace (
.kiro/settings/mcp.json)3. User / global (
~/.kiro/settings/mcp.json)
Python / Node / uvx / Docker as required by the server
Choose workspace or user scope
Kiro reconnects on config changes
Check MCP panel or
/mcp / /toolsUse autoApprove only for trusted, low-risk tools
03 · Server directory
Source: kiro.dev/docs/mcp/servers
Browse available MCP servers and click “Add to Kiro”. Install links use the
kiro:// URL scheme.Key points from the docs:
- MCP servers are third-party tools. Only install from trusted sources.
- Review each server’s documentation and licensing.
- Kiro is not responsible for third-party MCP servers.
- After adding, servers appear in the MCP panel with connection status.
04 · Tools, prompts, and resources
Source: kiro.dev/docs/mcp/usage · Tools overview
Tools
Callable actions the model can invoke. A good tool has:
- Precise name
- Clear description
- Narrow input schema
- Predictable output
Example: get_vulnerabilities(project, severity) is better than a catch-all tool.
How to use them
- Direct questions — ask in natural language
- # mentions — reference server prompts/resources
- /tools — list tools and token usage (CLI)
- MCP panel — see servers, status, and tools (IDE)
Controlling tools
autoApprove— skip prompts for listed toolsdisabledTools— hide dangerous tools- Agent
tools/allowedTools— restrict what an agent can see or run without prompt - Permissions layer for broader policy
05 · Tool search
Source: kiro.dev/docs/mcp/tool-search
When to enable
- 5+ MCP servers configured
- Context window overflow errors
/toolsshows MCP tools consuming > 50,000 tokens
# Enable (CLI) kiro-cli settings toolSearch.enabled true # Optional: force activation kiro-cli settings toolSearch.minPct 0 kiro-cli settings toolSearch.minTokens 0
Defaults
| Setting | Default |
|---|---|
toolSearch.enabled | false |
toolSearch.minPct | 5 |
toolSearch.minTokens | 50000 |
Activates when either threshold is exceeded (OR logic).
tool_search parameters: tool_id (exact server_name::tool_name) or query (keywords), optional max_results (default 5). Read-only; no permission prompt.
06 · Examples (from official docs)
Source: kiro.dev/docs/mcp/examples
{
"mcpServers": {
"aws-docs": {
"command": "uvx",
"args": ["awslabs.aws-documentation-mcp-server@latest"],
"env": {
"FASTMCP_LOG_LEVEL": "ERROR"
},
"disabled": false,
"autoApprove": []
}
}
}
Tools include search, read, and recommend documentation.
{
"mcpServers": {
"github": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"-e", "GITHUB_PERSONAL_ACCESS_TOKEN",
"ghcr.io/github/github-mcp-server"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_TOKEN}"
},
"disabled": false,
"autoApprove": []
}
}
}
Prefer environment variables over hard-coded tokens.
{
"mcpServers": {
"fetch": {
"command": "uvx",
"args": ["mcp-server-fetch"],
"disabled": false
}
}
}
07 · Best practices & security
Source: kiro.dev/docs/mcp/security
Secrets
- Never commit tokens
- Use
${VAR}references - Rotate credentials
chmod 600on mcp.json
Least privilege
- Minimal token scopes
- Disable destructive tools
- Prefer workspace config for project servers
autoApprove
- Only for trusted, low-risk tools
- Never for write/delete operations by default
disabledTools
{
"disabledTools": [
"delete_repository",
"force_push"
]
}
08 · Registry (enterprise)
Source: kiro.dev/docs/mcp/registry
Users can add any MCP server.
Admin configures allowed servers. Users select from the registry list. Servers not in the registry are hidden and not started — even ones you define in mcp.json.
Overrides still work
{
"mcpServers": {
"github": {
"type": "registry",
"env": {
"GITHUB_TOKEN": "${GITHUB_TOKEN}"
},
"timeout": 60000
}
}
}
Override fields for local servers: env, timeout. For remote: headers, timeout.
09 · Interview-ready answers
Q1. What is MCP?
Q2. Is Kiro an MCP server?
Q3. Why do we need mcp.json?
Q4. Workspace vs user MCP config?
.kiro/settings/mcp.json) is project-specific. User (~/.kiro/settings/mcp.json) is global. Prefer workspace for project-specific servers.Q5. What does command do?
Q6. What does autoApprove do?
Q7. What does disabledTools do?
Q8. What is Tool Search?
Q9. Loading priority?
Q10. When should you avoid MCP?
Q11. What is the enterprise MCP registry?
Q12. Security warning for local servers?
10 · Flashcards
Expert ladder
- Explain client vs server
- Write a local mcp.json
- Write a remote mcp.json
- Explain loading priority
- Use autoApprove / disabledTools safely
- Enable and explain Tool Search
- Explain enterprise registry behavior
11 · 60-second explanation
.kiro/settings/mcp.json (workspace) or ~/.kiro/settings/mcp.json (user). Local servers use command + args + env; remote servers use url + headers. I keep secrets in environment variables, use autoApprove only for low-risk tools, and disabledTools for anything destructive. When many servers are present I enable Tool Search so schemas load on demand. In enterprise, the MCP registry acts as a central allow-list.”
No comments:
Post a Comment