MCP server for Kaiten
mcp_server_for_kaiten
A simple Python MCP server for CRUD operations on Kaiten spaces, boards and cards
- 0 ★ on the repository
- Last commit
Broad access
Why this level
- Tools create, update and delete boards and cards in a live Kaiten workspace
- Board deletion supports a forced mode without extra confirmation
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/mcp-server-for-kaitenDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Tools create, update and delete boards and cards in a live Kaiten workspace
- Board deletion supports a forced mode without extra confirmation
This is third-party code. Review the repository files before installing.
What it does
The server wraps part of the Kaiten REST API in MCP tools: listing, creating, updating and deleting spaces, boards and cards. Requests to Kaiten go through an async httpx client, and errors are logged to a file. The server works with MCP Inspector for debugging. The Kaiten domain and access token are passed through environment variables.
Who it is for. For small Kaiten teams who want a minimal set of CRUD tools for an agent without extra features.
Good fit when
- You want a simple wrapper over Kaiten without complex setup
- You want to create and update boards and cards from an agent chat
- A local run via uv without any deployment is fine
Not a fit when
- You need cards with comments, checklists, sprints and backlog analytics
- You need a ready remote server with auth for a team
Example request
Show all boards in space 123 and create a new card in the first oneMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
DOMAINrequired- Kaiten workspace domain
TOKENrequired, secret- Kaiten API access token
Limitations
The project is small and has not been updated in over a year, and it is the author's only repository of this kind. There are few tools: only basic operations on spaces, boards and cards, no comments, checklists or sprints. Board deletion supports a force flag, which can wipe data with no way to undo it.
How to disable. Remove the server from your MCP client config and stop the uv run process.
FAQ
Can I delete a whole board?
Yes, the boards_delete tool accepts a force parameter for forced deletion.
Do I need a separate key per space?
No, one token from .env gives access to every space available to that Kaiten user.
Discussion
No questions or reviews yet.
Related
All Kaiten toolsKaiten MCP (Python)
Kaiten MCP
A single-file FastMCP server for Kaiten: 22 tools for cards, comments, checklists and time tracking
kaiten-mcp-server (nedgar8)
kaiten-mcp-server
A compact Python MCP server for Kaiten: list cards, move them between columns, set the owner and add comments
An MCP server for Kaiten: cards, comments, spaces and boards with control over response verbosity
Kaiten MCP with team hosting
kaiten-mcp
A Kaiten MCP server on PyPI with local stdio and a remote Streamable HTTP mode for a whole team via Docker or Kubernetes
kaiten-mcp (ViktorOgnev)
kaiten-mcp
An MCP server for Kaiten with 246 tools across 27 modules: cards, Service Desk, automations, audit and charts
A Kaiten MCP server with a full tool set for cards, time logs, boards, comments and checklists, installed with one npx command
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| MCP server for Kaiten (this card) | no | API key | 0 | |
| browser-use-mcp-server | no | API key | 848 | drives a browser through Playwright |
| MCP server for 1C:Naparnik | no | API key | 47 | on Spring Boot, for the 1C:Naparnik API |
| Kommo CRM MCP server | no | OAuth | 0 | in Python, with OAuth for Kommo |
README in short
The README lists the features: CRUD for spaces, boards (with forced deletion) and cards, async requests via httpx, error logging and MCP Inspector compatibility. The quick start covers installing dependencies, filling in .env from the example, and running with uv run src/main.py.