A
licenseNot graded
qualityD
maintenanceEnables AI assistants to manage Planka kanban boards, including creating, updating, and organizing tasks, lists, and cards via MCP.
7 npm
59
MIT
Kanban MCP
by SawatKia
Related Servers
Alternatives to Kanban MCP
No user-submitted related servers found.
Related Servers
- FlicenseCqualityAmaintenanceEnables AI assistants to manage Planka projects, boards, lists, cards, tasks, labels, comments, stopwatches, and memberships through MCP tools.56-
- AlicenseAqualityFmaintenanceMCP server enabling AI agents to manage PLANKA kanban boards with full CRUD support for cards, tasks, labels, comments, and lists.1540 npm10MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to interact with Planka, a real-time Kanban board application, for managing projects, boards, lists, cards, and more.1044 npm5MIT
- 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
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to interact with self-hosted Planka boards through the Planka REST API. It allows users to list, search, create, and update projects, boards, and cards using natural language.3-
TDQS
C2.8/5.0
Scored across 13 tools
Disambiguation2/5
Several tools have overlapping or duplicated purposes: scheduler_list_labels and mcp_kanban_list_labels are identical, as are scheduler_query_tasks and mcp_kanban_query_tasks. Also, mcp_kanban_comment_manager and mcp_kanban_batch_cards both handle comments, and mcp_kanban_card_manager and mcp_kanban_task_manager might confuse agents about task vs card (though the hierarchy clarifies).
Naming Consistency2/5
Naming is inconsistent: most tools use a 'mcp_kanban_' prefix with a manager suffix, but two are prefixed with 'scheduler_' and lack the manager suffix. Verbs vary (list vs get_all vs query), and there is a mix of 'batch_cards' and 'manager' patterns, breaking a predictable convention.
Tool Count2/5
With 13 tools, the count is on the higher end, but the duplication (two pairs of identical tools) inflates the count. The server has a broad scope (boards, cards, labels, tasks, memberships, comments, batch operations) but could be consolidated to ~10-11 unique tools without losing functionality.
Completeness3/5
The tool surface covers most CRUD operations for boards, cards, labels, tasks, and memberships, plus batch creation and querying. Missing are operations like bulk updates or moves across lists, but the core lifecycle is present. However, with the duplicated query/list tools, the actual coverage of unique operations is thinner than it appears.
Maintenance
ActivityMaintained
ResponsivenessNo issues