MCP reference
Kleio's MCP server is the same kleio binary, invoked with the mcp subcommand. It speaks MCP over stdio (and an HTTP transport behind JWT for hosted scenarios). See Onboarding › Editor setup for the install/registration flow.
Tools
| Tool | Purpose | Notes |
|---|---|---|
kleio_capture | Capture a work-item signal (signal_type=work_item). | Only work_item synthesizes into backlog items. checkpoint and decision types are rejected here — use the dedicated tools below. |
kleio_decide | Log a decision. | Required: content, rationale, confidence (low/medium/high). Include alternatives when they exist. |
kleio_checkpoint | Log an implementation slice. | Required: content, slice_category, slice_status, validation_status. Optional: caveats, deferred, backlog_item_id (UUID or KL-N) to close the item. |
kleio_backlog_list | List backlog items. | Filters: search, assignee (self/none/UUID), status, limit. |
kleio_backlog_show | Show one backlog item. | Accepts UUID or KL-N. |
kleio_backlog_prioritize | Update priority. | urgency, importance, status, assignee_id. |
kleio_ask | Query workspace memory. | RAG over captures, decisions, checkpoints. Read-only. |
Canonical schemas
Each tool's full input schema, including required fields and validation rules, is exposed by the MCP server itself (your editor's MCP UI can list them) and is also documented inline in the kleio-cli README.
For the wire-level capture format that backs kleio_capture — including the smart vs. relational paths and the JSON Schema — see CAPTURE_INGESTION.md in kleio-app (when published) and the docs/api/schemas/ directory in that repo.
Configuration
The MCP server reads credentials and API URL from ~/.kleio/environments/production.yaml (written by kleio login). Both hot-reload roughly every 30 seconds, so re-running kleio login or kleio workspace select does not require restarting your editor.