otty / dotfiles

All tools/Kiro

Kiro

kiro

An agentic IDE that helps you go from prototype to production with spec-driven development.

Detected by kiro-cli | macOS, Linux, Windows |kiro.dev

Sync it kiro.toml

Sync rules

What travels, what stays, what never leaves

Kiro in your home directory Every rule on this page, by file

mcpServers.*.env.*mcpServers.*.headers.*

Lifted into your secret store; the rest of the file syncs.

· steering/ Sync

Only what the catalog names. A directory that syncs brings everything inside it except what is listed as excluded here.

apps/kiro.tomlThe file this page is generated from

id = "kiro"

name = "Kiro"

homepage = "https://kiro.dev"

description = "An agentic IDE that helps you go from prototype to production with spec-driven development."

# kiro.dev serves the same mark as its SVG favicon.

icon = "theSVG:kiro"

# kiro-cli is the command the docs have you run: https://kiro.dev/docs/cli/

# walks through `kiro-cli login` and `kiro-cli chat`. The IDE build shares the

# same ~/.kiro directory — the MCP page below lists "IDE", "CLI" and "Web" as

# three surfaces over one user-level config — but its own launcher name is not

# documented, so only the CLI is named here.

detect = ["kiro-cli"]

# https://kiro.dev/docs/mcp/configuration/ names two scopes for the MCP server

# list and says what each one means: "Workspace Level: .kiro/settings/mcp.json"

# and "User Level: ~/.kiro/settings/mcp.json — Applies globally across all

# workspaces". The troubleshooting section at the bottom of the same page reads

# them back with `cat ~/.kiro/settings/mcp.json`.

# https://kiro.dev/docs/steering/ is the same pair for steering documents:

# per-project .kiro/steering/ and a global ~/.kiro/steering/ that applies to

# every project.

# ~/.kiro is a literal dotfile directory in the home directory; the docs give

# no XDG or %APPDATA% spelling for it.

paths = [

"~/.kiro/settings/mcp.json",

"~/.kiro/steering/",

]

exclude = []

# No whole-file credential documented under ~/.kiro: the sign-in is an account

# session rather than a file the docs place there.

secret = []

# The MCP page's property tables are where the credentials are. For a local

# server: "env Object No Environment variables for the server process", and the

# examples set API keys there directly; the page's own "Environment variables"

# section says "Many MCP servers require environment variables for

# authentication" and offers ${VARIABLE_NAME} as the way to avoid writing one

# in. For a remote server the table adds "headers Object No Headers to pass to

# the MCP server during connection" — where a bearer token goes. Both are

# lifted out; a ${VAR} reference costs nothing to carry through a secret store,

# while a pasted key would otherwise sync in the clear.

[[secret_paths]]

file = "~/.kiro/settings/mcp.json"

match = { key_path = ["mcpServers.*.env.*", "mcpServers.*.headers.*"] }

Use it with your dotfile manager

Same data, in the shape your tool already reads

Opens Otty and adds this tool to what it syncs

Opens otty://sync/add/kiro. Otty ships with this catalog, so the link only has to name the tool — nothing is downloaded.

Every one of these is generated from the same rules as this page.