Kiro

coord login finds Kiro on its own and registers Coordigent in ~/.kiro/settings/mcp.json. A steering file Kiro loads for every agent comes with the repo files.

Set it up

$ coord login

$ coord connect

Kiro is read from its session files only in repos connected on this machine, so its agents in a repo that isn't connected here are not recorded, even when a teammate connected the same repo.

coord login (and coord connect, which does the same) detects Kiro when ~/.kiro exists, or kiro-cli or kiro-cli-chat is on your PATH, and registers it at user level. Kiro has no user-level hook file; the Coordigent daemon watches what Kiro agents do instead.

To also write Kiro's files into a repo, for a team that commits them, run coord connect --repo-files inside it. That writes them when the repo already has a .kiro/ directory, or when you say yes to its one question about the other agent apps on this machine. To name Kiro without the question:

$ coord connect --repo-files --clients kiro

Reconnect the MCP server in Kiro, or start a new agent, to pick up the tools.

What gets written

On this machine

One entry in ~/.kiro/settings/mcp.json, named coordigent:

{
  "mcpServers": {
    "coordigent": {
      "command": "/Users/you/.tower/bin/coord-mcp",
      "args": [],
      "env": {},
      "disabled": false,
      "autoApprove": [
        "coordigent.session.list",
        "coordigent.directory.search",
        "coordigent.directory.get",
        "coordigent.status"
      ]
    }
  }
}

Other servers in the file stay. autoApprove lists only tools that read, so Kiro never sends a message or reads your inbox without asking you. An existing coordigent entry is kept, unless its command points at a binary that no longer exists. If you switched it off in Kiro, coord doctor says so, and coord install kiro --user writes it again with disabled: false. An old tower entry that runs tower-mcp is deleted in the same write. No token is stored here: coord-mcp reads your login from ~/.tower/config.json.

In the repo, with --repo-files

.kiro/settings/mcp.json: the same coordigent server, found through $HOME so the file is identical on every teammate's machine, with the repo named in COORDIGENT_REPO.
.kiro/steering/coordigent.md: the coordination rules, with inclusion: always front matter so Kiro loads them for every agent in the repo.

coord connect --repo-files also writes Claude Code's repo files; see Claude Code.

Only for Kiro

coord install kiro writes Kiro's repo files without the rest of coord connect. Add --user to write ~/.kiro/settings/mcp.json and ~/.kiro/steering/coordigent.md instead.

$ coord install kiro --user

Update

$ coord update

This downloads the current coord and coord-mcp and restarts the daemon. Reconnect the MCP server in Kiro to load the new coord-mcp.

Check it

$ coord doctor

coord doctor lists kiro with a ✓ and the config file it found. A ✗ line names the command that fixes it. In Kiro, open MCP Servers > coordigent, reconnect, and ask the agent to call coordigent.status: its own row is marked (you).

What works and what degrades

Kiro uses none of the optional MCP features: no resources, prompts, sampling, elicitation, roots or server notifications. Coordigent does not need them.

Identity. Kiro gives every agent a KIRO_SESSION_ID, and Coordigent uses it directly, so the agent you see in Coordigent is the same one Kiro's transcript names.
Files in use. Coordigent has no hook in Kiro. The daemon reads the transcripts Kiro writes under ~/.kiro/sessions/cli/ and records edits from them. An agent ends when Kiro's lock file for its transcript goes away.
Messages. Nothing can reach a running Kiro agent from outside. A message or conflict waits until the agent's next coordigent.* tool call, and arrives as a ⚠ COORD: banner on its result. coordigent.message.inbox reads the rest.

Remove

To remove Coordigent from this machine entirely, run coord uninstall (add --dry-run to see the plan first). It keeps anything you edited by hand.

To remove only Kiro's setup by hand, delete the coordigent entry from ~/.kiro/settings/mcp.json and the repo's .kiro/settings/mcp.json, and delete .kiro/steering/coordigent.md.

MCP tools lists every coordigent.* tool the agent can call.
Messages explains when a message is delivered.

#Set it up

#What gets written

#On this machine

#In the repo, with --repo-files

#Only for Kiro

#Update

#Check it

#What works and what degrades

#Remove

#Next