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.
14 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.27AGPL 3.0
- FlicenseNot gradedqualityCmaintenanceA 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.1 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
A3.6/5.0
Scored across 12 tools
Disambiguation4/5
Most tools target a distinct resource+action (task CRUD, comments, files, kanban server). However, add_comment duplicates update_task's documented comment-adding capability, and verify_task (visual verification) overlaps with update_task's setVerify verdict field, creating mild boundary confusion.
Naming Consistency5/5
All 12 tools follow a consistent snake_case verb_noun pattern (list_tasks, get_project, create_task, update_task, claim_next_task, get_task, add_comment, attach_file, export_prompt, verify_task, start_kanban, get_integration_guide). No mixing of conventions or vague verbs.
Tool Count5/5
12 tools is well within the healthy range and each earns its place: task lifecycle, comments/files, verification, and kanban/integration serving all map to distinct needs. No redundancy that bloats the surface.
Completeness4/5
Core lifecycle is covered (create, get, list, update, claim, plus comments/files/verification). The obvious gap is the absence of a delete_task tool, leaving no direct way to remove tasks, though status transitions can partially work around this.
Maintenance
ActivityActive
ResponsivenessNo issues