Kaiten MCP (tyunn)
Kaiten MCP
An MCP server and CLI for Kaiten with per-project settings and access limited to chosen spaces and boards
- 0 ★ on the repository
- Last commit
Extended access
Why this level
- The access token is stored in a plain config file on disk
- Without KAITEN_ALLOWED_SPACE_IDS the agent sees every space the token can reach
Install
- Works in
- Services
Manual install
git clone https://github.com/tyunn/kaiten-mcp.git
cd kaiten-mcpThen create ~/.kaiten/config with KAITEN_API_URL and KAITEN_API_TOKEN.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The access token is stored in a plain config file on disk
- Without KAITEN_ALLOWED_SPACE_IDS the agent sees every space the token can reach
This is third-party code. Review the repository files before installing.
What it does
The project wraps the Kaiten API in an MCP server and a matching CLI. A shared token and API address live in the global ~/.kaiten/config file, while project-specific settings such as the default space and board go into .kaiten.env in the project folder. Access can be restricted to listed spaces and boards via KAITEN_ALLOWED_SPACE_IDS and KAITEN_ALLOWED_BOARD_IDS, with adjustable log verbosity and an API client covering cards, comments, subtasks and files.
Who it is for. For teams running several Kaiten projects who want to restrict an agent to specific spaces and boards.
Good fit when
- You want one shared token but need to limit access per project
- You also want a CLI, not just an MCP server
- You need to control the verbosity of Kaiten request logging
Not a fit when
- You want a simple setup without a global config and per-project env variables
- You need a published npm package instead of cloning the repository
Example request
Show overdue cards in the default space, limited to the allowed boardsMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
KAITEN_API_URLrequired- API URL of your Kaiten space
KAITEN_API_TOKENrequired, secret- Kaiten access token
KAITEN_ALLOWED_SPACE_IDS- List of space IDs the agent may access
KAITEN_ALLOWED_BOARD_IDS- List of board IDs the agent may access
Limitations
The project has no stars or license and installs only via git clone; there is no published npm package. The ~/.kaiten/config file stores the token in plain text and must not be committed.
How to disable. Remove the server from your MCP client configuration and delete the ~/.kaiten/config file with the token.
FAQ
What order are settings read in?
The global ~/.kaiten/config first, then the project's .kaiten.env on top of it.
Discussion
No questions or reviews yet.
Related
All Kaiten toolsAn MCP server for Kaiten with 36 tools: cards, checklists, time tracking and day planning, local or remote with OAuth
kaiten-mcp (Go)
kaiten-mcp
A Go MCP server for Kaiten with readonly and full access profiles, where the tool set is set by config instead of one blanket key
Kaiten MCP
kaiten-mcp
Swift MCP server for Kaiten: spaces, boards, columns, lanes, cards, comments and custom properties
A Kaiten MCP server with a full tool set for cards, time logs, boards, comments and checklists, installed with one npx command
An MCP server for Kaiten: cards, comments, spaces and boards with control over response verbosity
kaiten-mcp (ViktorOgnev)
kaiten-mcp
An MCP server for Kaiten with 246 tools across 27 modules: cards, Service Desk, automations, audit and charts
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Kaiten MCP (tyunn) (this card) | no | API key | 0 | |
| Kaiten MCP Server | no | API key | 33 | with adjustable response detail |
| Kaiten MCP | no | not required | 20 | boards and cards |
| kaiten-mcp (ViktorOgnev) | no | OAuth | 6 | 246 tools and Service Desk |
README in short
The extensive Russian README covers installing from the repository, the mandatory global access config, an optional project config with space and board restrictions, response token optimization, and a separate section of instructions for AI assistants on using the tools.