Kanbini
Related Servers
Alternatives to Kanbini
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceKanban 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.4MIT

Kanban Zone MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI assistants to manage Kanban Zone workspaces via 23 tools for boards, cards, comments, checklists, and tasks.2747 npm1MIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage Kanban tasks, boards, teams, and checklists via natural language, with full CRUD operations and live updates.MIT
- 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 gradedqualityBmaintenanceEnables 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 42 tools
Tools are cleanly partitioned by resource+action (board/list/card/label/checklist/comment/attachment/blocker), with clear read-vs-write and archive-vs-delete separation. The only real overlaps are toggle_checklist_item vs update_checklist_item (the former is a subset of the latter) and create_checklist vs add_checklist_item, both of which the descriptions do distinguish.
Every tool follows the same kanbini_<verb>_<noun> snake_case pattern (create_card, update_board, archive_list, remove_blocker, set_card_labels). Verb choice is semantically consistent — get_ for single-resource reads, list_ for enumerations, move_/copy_/archive_ for specific mutations.
42 tools is well above the comfortable band, but the domain genuinely spans nine entities (boards, lists, cards, checklists, checklist items, comments, labels, attachments, blockers) plus search, agenda, and batch. A few slots feel redundant (toggle_checklist_item, and the get_board/get_list_cards/get_card trio could be consolidated), so it is heavy rather than tight.
Full lifecycle is covered for boards, lists, cards, labels, checklists/items, comments, and attachments, plus blockers, archival, global search, an agenda view, and an atomic batch tool that composes the write surface. No obvious dead ends; the only minor omission is reading back attachment file content.