Kanban MCP
Related Servers
Alternatives to Kanban MCP
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables AI agents to create, query, update, claim, hand off, and complete tasks on a local SQLite-backed, project-namespaced kanban board through stdio MCP tools, including filtering for ready/blocked/stale work and exchanging task attachments. It also lets agents list projects and manage statuses, ownership, and evidence without any server or accounts.MIT- FlicenseAqualityBmaintenanceEnables coding agents to track and coordinate project work through a shared SQLite ledger, including task plans, session ancestry, claims, work locations, blockers, and commits via MCP tools.9-
- AlicenseNot gradedqualityAmaintenanceLocal-first task governance board for AI agents, enabling session registration, task creation, progress updates, and evidence reporting via MCP, with separation of agent claims and human acceptance.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceSelf-hosted kanban board that dispatches AI agent fleets against tickets. The embedded Streamable HTTP /mcp endpoint exposes 7 tools to list projects, read boards and tickets, and create, move and comment tickets from any MCP client.26AGPL 3.0
- AlicenseNot gradedqualityAmaintenanceA local, provider-neutral MCP server for repository-scoped issue handling. It provides a guarded interface to Linear, GitHub Issues, GitHub Projects v2, and Jira Cloud, with preview/apply safety and host-local configuration.51 npm1MIT
- AlicenseNot gradedqualityAmaintenanceLocal-first MCP server providing a shared, AES-256-GCM encrypted SQLite ledger of structured user state (stack, projects, preferences) that any MCP-aware tool can read/write, with user-held keys and optional zero-knowledge sync.1Apache 2.0
TDQS
Scored across 32 tools
Most tools map cleanly to distinct resource-action pairs, but kanban_update_ticket and kanban_move_ticket both allow moving tickets and updating completion summaries, which creates possible confusion. The two doc-link tools also have inverse orientations that could be mistaken for each other.
Names follow a mostly consistent kanban_verb_noun pattern, but kanban_column_top_ticket lacks a verb and find/search are used interchangeably. Overall, the convention is predictable and readable.
With 32 tools, the surface is heavy and exceeds the comfortable range for an agent to quickly select between operations. Many tools are individually reasonable, but the count feels bloated for a kanban server, especially with niche entries like kanban_list_scrum_values and kanban_get_batch.
Core CRUD/lifecycle coverage exists for projects, columns, tickets, epics, doc links, and the staging lease. Notable gaps include no project update/delete, no doc-link removal, and no batch mutators, but agents can work around most of these.