kanbantool-mcp
Related Servers
Alternatives to kanbantool-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceAn MCP server that enables AI assistants to interact with Kan boards through the Kanban API, allowing tasks like viewing and managing boards via natural language.789 npmMIT
- AlicenseBqualityFmaintenanceAn MCP server that provides a database-backed kanban board with 40+ tools for AI agents to track issues, features, todos, epics, and diary entries across projects, including status workflows, relationships, and semantic search.4583MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that enables AI agents to manage tasks, boards, lists, and comments on a Kanban-style project management system through JSON-RPC methods.3 npm2AGPL 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-
- AlicenseNot gradedqualityBmaintenanceAn AI-native kanban board MCP server where agents pull tasks via the Model Context Protocol. It provides tools for task discovery, claiming, progress updates, and review workflows.4MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for kanban-tui, a terminal-based task manager, that exposes task, board, and column management commands for AI agents to interact with.105 PyPI283MIT
TDQS
Scored across 26 tools
Each tool targets a distinct resource and action (e.g., add_comment vs add_subtask, start_timer vs stop_timer). There is no overlap in purpose, and descriptions clearly differentiate them.
Almost all tools follow a consistent verb_noun pattern in snake_case (e.g., create_task, list_boards, delete_comment). Exceptions like 'ping' and 'whoami' are standard conventions and do not disrupt coherence.
With 26 tools, the set is slightly larger than ideal but still well-scoped for a comprehensive Kanban server. Each tool serves a clear purpose without redundancy.
The surface covers core workflows (CRUD for tasks, subtasks, comments, timers, boards, users, search, and custom fields). Minor gaps include the absence of a delete_task tool and an update_comment tool, but these are acceptable for the domain.