Kanbini
Related Servers
Alternatives to Kanbini
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceKanban board over plain - [ ] task lines in an Obsidian vault, with two-way Markdown sync. Lets AI assistants list boards, find, create, update, move and comment on cards; deleting cards or boards is not exposed.2MIT

Kanban Zone MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI assistants to manage Kanban Zone workspaces via 23 tools for boards, cards, comments, checklists, and tasks.27185 npm1MIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage Kanban tasks, boards, teams, and checklists via natural language, with full CRUD operations and live updates.78 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage a local-first Kanban board with Azure DevOps-style workflow rules, including task creation, status updates, subtask breakdown, full-text search, daily summaries, and next-task suggestions.-
- AlicenseBqualityDmaintenanceEnables AI agents to manage kanban boards with tasks, including creating boards, items, moving between columns, and searching.81MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to work a Noeto kanban board: browse boards and cards, search across them, create and update cards, move and reorder them between columns, comment, and read or write documents and attachments on cards. It runs as a local process for Claude Code and Claude Desktop and deliberately avoids destructive actions such as deleting human-created content.MIT
TDQS
Scored across 30 tools
Each tool targets a distinct resource and action (boards, lists, cards, labels, checklists, blockers, attachments, comments). The read tools (get_board, get_card, search_cards, get_agenda) have clearly differentiated purposes and the descriptions state when to prefer each. Archive vs delete vs update are explicitly separated.
All tools are snake_case with a consistent `kanbini_` prefix and verb_noun structure (list_boards, create_card, update_list, archive_card, add_blocker, set_card_labels). No camelCase or mixed conventions appear.
30 tools is on the heavy side for a single kanban board server, exceeding the typical comfortable range. The domain is genuinely rich (boards, lists, cards, labels, checklists, attachments, comments, blockers, archive), but some could be consolidated (e.g., three checklist tools, four label tools).
Core lifecycle coverage is strong: create/update/move/archive/delete for cards, create/update/archive/move for lists and boards, and full label CRUD. Minor gaps exist: no delete for boards or lists (archive serves as a workaround), and no way to remove a checklist item or checklist (only toggle completed).