Kaiten CLI and MCP server (Go)
kaiten-mcp
A native Go CLI and MCP server for Kaiten with safe defaults: write tools are off until explicitly enabled
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- When KAITEN_ENABLE_WRITE_TOOLS is on, it can change cards and comments
- The token gives user-level rights in your Kaiten
Install
Manual install
kaiten-mcp --transport streamable-http --host 127.0.0.1 --port 8000Run as an HTTP server on loopback instead of stdio.
This is third-party code. Review the repository files before installing.
What it does
The project builds two native Go binaries: kaiten, a command line that prints API results as JSON, and kaiten-mcp, an MCP server exposing the same data to an agent (also available as kaiten mcp). It covers spaces, boards, columns, lanes, cards, comments, blockers, members, tags and checklists. The MCP server exposes read tools only by default; writes are turned on with KAITEN_ENABLE_WRITE_TOOLS. It can run over stdio or as a Streamable HTTP server bound to loopback. Releases ship binaries for macOS, Linux and Windows with SHA-256 checksums and an SBOM.
Who it is for. For people who want a ready binary with no Node.js or Python, and want to turn on writes to Kaiten deliberately.
Good fit when
- You want a native binary with no Node.js or Python runtime to install
- You want the agent to only read Kaiten by default
- You need both a CLI for scripts and an MCP server for an agent
Not a fit when
- You want to install via npm or pip: there is no registry package, only a release download
- You run Linux or Windows and need a ready background service: those installers are still in beta
Example request
Show the list of spaces in Kaiten and card number 123Limitations
Installation only by downloading a release archive and adding it to PATH, no npm or PyPI package. The background-service installer is verified only on macOS; Linux and Windows are still beta for that path. The project is independent, not an official Kaiten distribution.
How to disable. Stop the background service if installed, remove the binaries from PATH, and delete the kaiten-mcp entry from your MCP client config.
MCP
- Transport
- stdio, http
- Authentication
- API key
| Environment variables | |
|---|---|
| KAITEN_URL required | Kaiten instance URL |
| KAITEN_API_TOKEN required, secret | API token |
| KAITEN_ENABLE_WRITE_TOOLS | Set to true to enable write tools, only read tools are available by default |
Security check
- When KAITEN_ENABLE_WRITE_TOOLS is on, it can change cards and comments
- The token gives user-level rights in your Kaiten
README in short
The README details support status by OS (stable on macOS, beta on Linux and Windows), safe defaults (writes off, HTTP on loopback, tokens not logged), CLI and MCP commands, the Go 1.26 build requirement, and links to separate docs on architecture, installation, configuration and security. It stresses that the project is independent and not an official Kaiten distribution.
FAQ
Can the agent change data in Kaiten right away?
No, write tools are hidden until the KAITEN_ENABLE_WRITE_TOOLS=true variable is set.
Can I install it via npx or pip?
No, only by downloading the release archive for your OS and architecture.
Related
A self-hosted knowledge base with block-level references and a built-in MCP server for connecting AI agents to your notes
A CLI for every Google Workspace API with JSON output and agent skills: Drive, Gmail, Calendar, Sheets and more
Local search over Markdown notes, docs and meeting transcripts: keywords, semantic search and reranking, with an MCP server
A task manager for AI-driven development: breaks a PRD into dependent tasks and guides the agent through them via MCP or CLI