@theyahia/kaiten-mcp
Related Servers
Alternatives to @theyahia/kaiten-mcp
No user-submitted related servers found.
Related Servers
- FlicenseCqualityDmaintenanceEnables interaction with Kaiten project management platform through 246 tools for managing cards, comments, time logs, boards, and more.2466-
- AlicenseBqualityAmaintenanceConnects an AI assistant to a Kaiten workspace through 44 tools that search and read cards, browse spaces, boards, columns and lanes, and create, update, move, archive or delete cards along with their comments, members, tags, checklists and custom field values. Changes are applied immediately with the permissions of the supplied API token.44562 npmMIT
- AlicenseAqualityDmaintenanceMCP server for Kaiten project management, providing 63 tools for managing cards, comments, checklists, time tracking, and more. Enables AI assistants to interact with Kaiten workspaces through natural language.6337 npmMIT

Kanban Zone MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI assistants to manage Kanban Zone workspaces via 23 tools for boards, cards, comments, checklists, and tasks.2722 npm1MIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage Kanban tasks, boards, teams, and checklists via natural language, with full CRUD operations and live updates.53 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with Kaiten project management through its REST API. Enables managing spaces, boards, cards, comments, checklists, tags, and time logs.1MIT
TDQS
Scored across 63 tools
Every tool targets a distinct resource or subresource (spaces, boards, columns, lanes, cards, members, tags, blockers, checklists, comments, sprints, custom properties), and the verb prefixes clearly separate read from mutation operations. An agent should rarely confuse one tool with another, even within the dense card subresource family.
The set largely follows a snake_case verb_noun pattern (list_spaces, create_board, update_card), and card subresources consistently use list_card_* / add_card_* / remove_card_*. Minor inconsistencies like block_card/unblock_card instead of create/delete_card_blocker, and delete_comment vs remove_* for other subresources, prevent a perfect score.
With 63 exposed operations, the tool surface is far beyond the 3–15 range that makes a coherent MCP server easy for an agent to navigate. Even though the tools are logically grouped by Kaiten's domain, the raw API-style granularity creates an extreme selection burden and warrants a low score.
The core lifecycle is well covered: spaces, boards, columns, lanes, cards, comments, checklists, members, tags, blockers, and external links all have create/read/update/delete or equivalent operations. Minor gaps remain—no get_column/get_lane, no workspace-level tag or sprint CRUD, and custom properties are read-only—but agents can usually work around them via list and board endpoints.