kaiten-mcp
Related Servers
Alternatives to kaiten-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables interaction with Kaiten's kanban and project management system, offering tools to manage spaces, boards, cards, comments, members, tags, checklists, and more via natural language.6323 npm1MIT
- 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.4439 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.6335 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 gradedqualityDmaintenanceMCP server for interacting with Kaiten project management through its REST API. Enables managing spaces, boards, cards, comments, checklists, tags, and time logs.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered project management by connecting Claude to Planka kanban boards via 75+ MCP tools for creating, updating, and managing projects, boards, lists, and cards.1GPL 3.0
TDQS
Scored across 246 tools
With 246 tools, several near-duplicates blur boundaries: list_cards vs list_all_cards, get_space_activity vs get_all_space_activity, and chart_control vs chart_cycle_time vs chart_lead_time. While many resource areas are distinct, the sheer volume plus overlapping bulk/all variants makes reliable tool selection difficult.
The vast majority follow a consistent kaiten_verb_noun pattern (list, get, create, update, delete, add, remove). Minor deviations like kaiten_chart_cfd and kaiten_batch_add_sd_org_users break the pattern slightly, but overall naming is predictable.
246 tools is an extreme mismatch for an MCP server; even a full platform API is better grouped into multiple focused servers. The count alone makes the toolset impractical for an agent to navigate and select from efficiently.
The surface is very comprehensive, covering CRUD-style operations for spaces, boards, cards, documents, checklists, custom properties, Service Desk, SLA policies, webhooks, and more. Minor gaps exist, such as missing single-get endpoints for some resources and a few operations documented as likely returning 405.