A
licenseNot graded
qualityD
maintenanceA local-first Kanban board for AI agents that enables ticket management via MCP tools, with a real-time web UI.
7 npm
4
MIT
Vibeflow
by zorcec
Related Servers
Alternatives to Vibeflow
No user-submitted related servers found.
Related Servers
- 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.29AGPL 3.0
- FlicenseNot gradedqualityDmaintenanceA local-first Kanban system with MCP tools for AI agents to manage tickets, features, and tasks, paired with a React UI for human users.-
- AlicenseNot gradedqualityBmaintenanceLocal kanban board & harness for coding agents over MCP: agents claim and move tasks, read and write notes, and build Auto-code workflows, within per-folder permissions and an audit log.12 npm1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceA local kanban board and docs tool that AI agents can drive over MCP. It enables project management without accounts or API keys.MIT
- AlicenseAqualityCmaintenanceA kanban board system served over MCP that lets coding agents manage shared work pipelines with enforced state transitions, work reports, and audit trails.37AGPL 3.0
TDQS
A4.2/5.0
Scored across 13 tools
Disambiguation4/5
Most tools target clearly distinct operations (create/get/list/update task, attach/get file, claim, pull, start server), and the descriptions explicitly cross-reference each other to route the agent. The only real overlaps are update_task's `comment` field vs add_comment, and update_task's setVerify verdict vs verify_task running verification — both are called out in the text, so confusion is limited but possible.
Naming Consistency4/5
The set is overwhelmingly consistent verb_noun snake_case (get_project, list_tasks, create_task, claim_next_task, add_comment, attach_file, verify_task, start_kanban). The lone deviation is `pull`, a bare verb, and get_integration_guide is longer than the rest, but the pattern is easy to read and predict.
Tool Count5/5
13 tools is squarely in the well-scoped range and each one maps to a distinct lifecycle action (read, create, edit, comment, attach, claim, verify, sync, serve). Nothing feels padded or missing purely on count grounds.
Completeness3/5
The task surface has create/read/list/update, comments, attachments, claiming and verification, but there is no delete/archive task operation and no push tool even though `pull` is explicitly described as the inverse of a push. Agents can work around deletes via other means, but these are notable lifecycle gaps for a board server.
Maintenance
ActivityActive
ResponsivenessSyncing