Kaiten MCP (Python)
Kaiten MCP
A single-file FastMCP server for Kaiten: 22 tools for cards, comments, checklists and time tracking
- 1 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Can permanently delete a card
- Changes columns, members and tags on a real board
Install
- Works in
- Services
Manual install
pip install -r requirements.txtOr pip install "mcp>=1.2.0" httpx without cloning the whole repository.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Can permanently delete a card
- Changes columns, members and tags on a real board
This is third-party code. Review the repository files before installing.
What it does
The server wraps the Kaiten REST API in 22 Python tools (FastMCP) over stdio. Reference lookups cover the current user, spaces, boards, board structure with columns and lanes, users, and card types. For cards: filtered search by text, board, column, owner, state, dates and tags, plus get, create, update, move, archive and permanent delete. Separate tools handle comments, checklists, members, tags and time logs in minutes. Lists and search return compact summaries to save context, and Kaiten's rate limit (50 requests per second) is handled with auto-retry based on the X-RateLimit-Reset header.
Who it is for. For Kaiten teams that want a full set of card operations from a single script with no project build step.
Good fit when
- You need the full card lifecycle: create, find, update, move, archive
- You need checklists, comments and time logging in one server
- You want to run the server as a single python file with no build step
Not a fit when
- You need an HTTP transport for team hosting: the server only runs over stdio
- You need a ready PyPI package: it is installed manually via requirements.txt
Example request
Find Kaiten cards tagged hotfix on the support board and show their statusMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
KAITEN_API_TOKENrequired, secret- Bearer token, required
KAITEN_DOMAIN- Subdomain, e.g. mycompany for mycompany.kaiten.ru
KAITEN_BASE_URL- Alternative to the domain: the full API URL, e.g. for a self-hosted instance
KAITEN_API_VERSION- v1 (default) or latest
KAITEN_TIMEOUT- Request timeout in seconds, defaults to 30
Limitations
Stdio transport only, no HTTP. No PyPI package, dependencies (mcp, httpx) are installed manually. Card deletion is permanent. Single author, few stars and releases.
How to disable. Remove the kaiten server with claude mcp remove kaiten, or delete it from claude_desktop_config.json.
FAQ
Is there an HTTP mode for a team?
No, the server only runs over stdio, each user starts their own process.
How do I set a custom company domain?
Use the KAITEN_BASE_URL variable with the full API address instead of KAITEN_DOMAIN.
Discussion
No questions or reviews yet.
Related
All Kaiten toolsMCP server for Kaiten
mcp_server_for_kaiten
A simple Python MCP server for CRUD operations on Kaiten spaces, boards and cards
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
Kaiten MCP: 51 tools for cards
kaiten-mcp
A local Node.js 24 stdio server for finding and editing Kaiten cards, checklists, comments and custom fields from Codex and Claude Code
An MCP server for Kaiten: cards, comments, spaces and boards with control over response verbosity
A Kaiten MCP server with a full tool set for cards, time logs, boards, comments and checklists, installed with one npx command
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
README in short
The README lists 22 tools by group: reference data, cards, comments, checklists, members, tags, time logs. It shows pip installation, running and checking via MCP Inspector, connecting Claude Code and Claude Desktop, an environment variable table, and a typical workflow from listing spaces to moving a card.