Kiro MCP Server

Export a Kiro session

kiro_session_export

Export a Kiro session to a file inside KIRO_MCP_ROOTS, like chat save. Set overwrite to true to replace an existing destination file.

Instructions

Export a session to a file inside KIRO_MCP_ROOTS with _kiro/session/export, like /chat save. Fails with PATH_EXISTS unless overwrite is true. Importing an archive is not possible over ACP.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>",
      "path": "<path>"
    },
    "name": "kiro_session_export"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Destination file inside KIRO_MCP_ROOTS (relative paths resolve against the session's cwd).
`overwrite`	No
`session_id`	Yes	Kiro session id (sess_<uuid>).

Output Schema

Name	Required	Description	Default
`path`	Yes
`bytes`	Yes
`session_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 5, 2026

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare the non-read-only, non-destructive, non-idempotent profile, and the description adds concrete behavior on top: the PATH_EXISTS failure mode and the overwrite escape hatch. It does not, however, say what an overwrite actually replaces or whether the destination is trusted to be sandboxed beyond KIRO_MCP_ROOTS.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with purpose then failure mode then exclusion, with no filler. The '_kiro/session/export' token and the 'ACP' reference are slightly opaque for an agent without prior context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no prose, and the description still covers destination constraints, error handling, the overwrite switch, and the unsupported inverse operation. That is everything an agent needs before invoking a three-parameter export tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the description compensates for the one undocumented parameter by explaining that overwrite governs the PATH_EXISTS failure. Path scoping and the session id are covered between schema and description, leaving no parameter semantically opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Export a session to a file') and constrains where the file lands (KIRO_MCP_ROOTS), which separates it from sibling read tools like kiro_session_list or kiro_session_history. It does not explicitly name the sibling it is not, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The analogy 'like /chat save' plus the note that 'Importing an archive is not possible over ACP' gives a clear sense of the intended use and rules out the inverse operation. It still leaves the choice against kiro_session_history or kiro_session_state to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.