kaiten-mcp
Related Servers
Alternatives to kaiten-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for managing Kaiten tasks through AI agents like Claude, enabling task retrieval, creation, updating, and time logging.24 npm2MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for integrating Kaiten API with Claude Desktop, enabling management of cards, comments, spaces, and boards with advanced features like verbosity control, response format selection, and auto-truncation.33MIT
- AlicenseNot gradedqualityDmaintenanceMCP server and CLI tool for interacting with Kaiten project management API, optimized for token efficiency. Enables AI assistants to search, create, update, and manage tasks with minimal token usage.MIT
- FlicenseAqualityDmaintenanceMCP server for interacting with Kaiten (kaiten.ru) project management. Supports listing, moving tasks, setting responsible persons, and adding comments via natural language.7-
- FlicenseNot gradedqualityDmaintenanceAn MCP server for managing tasks in Cursor IDE, enabling AI agents to create, update, and comment on tasks via MCP tools, with a kanban dashboard and WebSocket events.1-
- AlicenseBqualityFmaintenanceMCP server for Panel Todo — lets AI assistants manage your tasks, issues, and sprints directly in VS Code.388 npmMIT
TDQS
Scored across 15 tools
Most tools target a clearly distinct resource+action (spaces, boards, columns, lanes, tasks, comments, tags), and descriptions explicitly resolve the riskiest boundary: update_task vs move_task for workflow status. The remaining overlap is minor — list_tags (workspace catalog) vs get_task_tags (per-task attachments) vs add/remove_tag_from_task are distinguishable but require reading descriptions rather than names.
All 15 tools use snake_case verb_noun form with a small, predictable verb set (list_/get_/create_/update_/move_/add_/remove_). The one wrinkle is get_task_tags using 'get' for what is a list operation, but it still fits the verb_noun pattern.
15 tools is well-scoped for a Kaiten project-management surface: four read-only hierarchy navigators, task CRUD plus move, and tag/comment operations. Each tool corresponds to a distinct API endpoint with no filler.
Core lifecycle is covered (create/get/list/update tasks, move between columns/lanes, comments, tags, board structure), and deletion is reachable via update_task condition=3. However, there is no way to list users/members, and the description states responsible is only settable on create_task — so reassigning a task is impossible, a real dead end for a task tracker.