MCP integration
szpont install-mcp registers szpont mcp with all three tools (claude mcp add, codex mcp add, ~/.kimi-code/mcp.json). Agents can then call:
| Tool | Purpose |
|---|---|
report_session_start | track a session as soon as it starts |
mark_session_completed | move a finished session to the archive (works with just cwd if the agent does not know its session id) |
reopen_session | undo a completed mark |
There is deliberately no list_sessions tool: connected agents can report and complete sessions, but they cannot enumerate sessions from other repos (titles and paths of unrelated private work stay private).
The MCP server writes to the shared database; the TUI picks changes up on its next refresh tick (15s default, --refresh-secs). Every call is recorded in a local audit table (mcp_events, arguments JSON capped at 4KB, newest 1000 rows kept).
Install details: Claude Code is registered with --scope user; for Kimi the entry is written to ~/.kimi-code/mcp.json and a previous file is kept at mcp.json.bak.