A
licenseA
qualityB
maintenanceMCP server that connects AI coding tools to VibeCompass projects for reading context and writing decisions, conflicts, and session notes.
10
12 npm
MIT
mcp-vibekanban
by yigitkonur
Related Servers
Alternatives to mcp-vibekanban
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for Kaiten kanban boards, enabling task management via AI assistants like Cursor and Claude Code.1MIT
- AlicenseBqualityCmaintenanceAn MCP server that enables AI assistants to interact with Kan boards through the Kanban API, allowing tasks like viewing and managing boards via natural language.7819 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for task management that enables AI agents to read, create, update tasks, and track work sessions, allowing agents and humans to collaborate on the same task board.6 npm9MIT
- AlicenseAqualityCmaintenanceAn MCP server that connects AI assistants to Kanban Tool for reading and managing boards, tasks, and workflows via natural language.26MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI coding agents to communicate, share state, and coordinate work in real time via MCP tools or REST API.123 npm5MIT
TDQS
A4/5.0
Scored across 12 tools
Disambiguation5/5
Each tool targets a distinct action and resource. Task tools (create, read, update, delete) are clearly separated from session tools (start, list, get, send, cancel, queue status) and context retrieval. No overlap or ambiguity.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_task, list_sessions, get_queue_status). The verbs are descriptive and the pattern is uniform across the entire set.
Tool Count5/5
With 12 tools, the server covers task management (CRUD), session lifecycle, queue operations, and workspace context. The count feels well-balanced for the domain without being excessive or sparse.
Completeness4/5
Task CRUD is fully covered. Sessions have start, list, get, and message sending. Lacks an explicit end/close session tool, but the current set supports core workflows. Minor gap, but agents can manage via cancel_queue or context.
Maintenance
ActivityInactive
ResponsivenessNo issues