kanban-pro
Related Servers
Alternatives to kanban-pro
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA local MCP server with a web board that lets coding agents manage kanban cards, checklists, and work tracking through 30 MCP tools, with live updates and session tracking.MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that integrates a Kanban task board into a sandboxed agent environment, with tools for task management and deterministic state snapshots for agent evaluation.-
- AlicenseBqualityDmaintenanceAn 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.4580MIT
- 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
- 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 37 tools
Each tool has a clearly distinct purpose, with detailed descriptions that prevent ambiguity. The verbs and nouns are specific (e.g., 'claim_card' vs 'heartbeat_claim' and 'release_claim'), and overlapping operations are differentiated by context (e.g., 'list_work' vs 'list_cards').
All tool names follow a consistent verb_noun pattern in snake_case, with clear actions like 'create', 'delete', 'list', 'update', and specific nouns. No mixing of conventions or vague verbs.
With 37 tools, the server is comprehensive but slightly heavy. Each tool serves a distinct function in the Kanban lifecycle, covering boards, columns, cards, comments, relations, placements, claims, workflow, and auditing. The count is justifiable but at the upper bound of typical scope.
The tool surface covers most CRUD operations and advanced features (claims, workflow transitions, change feed, work reports). Minor gaps exist: lack of explicit label management (only present in get_board) and inability to create or modify workflow schemes, but core Kanban operations are fully supported.