kanban-mcp
Related Servers
Alternatives to kanban-mcp
No user-submitted related servers found.
Related Servers
- 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 gradedqualityAmaintenanceA kanban board MCP server that enables AI agents to read and write project boards through session loops, with built-in cost tracking and local-first storage.10 npm1MIT
- FlicenseNot gradedqualityDmaintenanceA minimal MCP server that enables AI assistants to manage a kanban issue board. It provides tools for listing, creating, updating, and deleting issues with support for both local development and team deployments.10-
- 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.6 npm2AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server for tracking issues across multiple AI agent sessions, enabling agents to file, claim, complete, review, and close issues with a web UI for monitoring.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that provides a real-time project management board with cards, sprints, comments, and docs, enabling coding agents to query and edit project state.MIT
TDQS
Scored across 45 tools
Most tools have distinct purposes, but a few convenience functions overlap with general ones (e.g., get_todos vs list_items with status filter, close_item vs set_status). The descriptions clarify intent, but the large number of get_* tools could cause initial confusion.
Most tools follow a verb_noun pattern, but there are inconsistencies: 'new_item' vs 'add_*' verbs, 'edit_item' vs 'update_tag', 'remove_tag' vs 'delete_item', and 'project_summary' lacks a verb. The mixed conventions are still readable but not uniform.
With 45 tools, the server is heavily over-scoped for a Kanban board. Many tools are specialized (metrics, decisions, embeddings) and could be combined or removed. The sheer number overwhelms an agent's tool selection.
The tool surface covers the full lifecycle of items (CRUD, status, relationships, tags, decisions, updates, search, export) with few gaps. Minor missing features include no edit for decisions and no item type change, but these are workable.