Kiro — MCP Configs

File format

JSON

Discovery path

.kiro/settings/mcp.json

Syllago install method

JSON merge

Symlink support

No

Config file

.kiro/settings/mcp.json

Transports

stdio, sse

Features

How each feature converts to syllago's canonical format. See format conversion for what these statuses mean.

Fields

Native frontmatter or config fields this provider exposes. The first column is the provider's own field name; the canonical key column links to syllago's cross-provider equivalent.

Config key	Conversion	Canonical key	Summary
autoApprove	Embedded Conversion type: Embedded No canonical equivalent — appended as prose in a conversion notes block so nothing is silently lost. Learn more →	—	Per-server 'autoApprove' field accepting a tool-name array or '*' wildcard to skip user confirmation.
disabled	Embedded Conversion type: Embedded No canonical equivalent — appended as prose in a conversion notes block so nothing is silently lost. Learn more →	—	Per-server 'disabled: true' flag deactivating a server without removing its configuration. Allows temporarily disabling a server while preserving its definition.
disabledTools	Embedded Conversion type: Embedded No canonical equivalent — appended as prose in a conversion notes block so nothing is silently lost. Learn more →	—	Per-server 'disabledTools' array suppressing specific tools without disabling the entire server.
url	Embedded Conversion type: Embedded No canonical equivalent — appended as prose in a conversion notes block so nothing is silently lost. Learn more →	—	Remote MCP servers configured with 'url' (HTTPS or localhost HTTP endpoint) and optional 'headers' map for authentication. Configuration applies automatically upon saving.

Other features

Behaviors, conventions, and capabilities that aren't tied to a single named field — things like path-based activation, discovery rules, and lifecycle behavior.

Feature	Conversion	Summary
auto_approve	Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more →	kiro_mcp_auto_approve: Kiro supports per-server or per-tool auto-approval configuration to suppress confirmation prompts
env_var_expansion	Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more →	kiro_mcp_env_var_expansion: Environment variables referenced dynamically using ${VARIABLE_NAME} syntax within MCP config values; recommended pattern for secrets instead of hardcoded values
tool_filtering	Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more →	kiro_mcp_disabled_tools: Kiro supports per-server tool disable configuration to control which MCP tools are available to the agent
transport_types	Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more →	Kiro supports stdio (local process via command + args) and remote (HTTPS endpoint or localhost HTTP via url + optional headers) server types
Environment variable expansion in MCP config values	Embedded Conversion type: Embedded No canonical equivalent — appended as prose in a conversion notes block so nothing is silently lost. Learn more →	MCP config values support ${VARIABLE_NAME} syntax to reference environment variables at runtime. Recommended for API keys and secrets to avoid storing sensitive values directly in config files.

Sources

Source
https://kiro.dev/docs/mcp/configuration/