KanbanFlow MCP Server
Related Servers
Alternatives to KanbanFlow MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables managing KanbanFlow boards, tasks, and workflows directly from Cursor/Claude with a one-command setup.168 npm7MIT
- AlicenseAqualityAmaintenanceA read-only Model Context Protocol server that connects MCP clients such as Claude Desktop, Claude Code, Cursor or VS Code to KanbanFlow, exposing the configured boards and the tasks assigned to a chosen person across all of them. It resolves board, column, swimlane, color, label and people ids to readable names, reports which boards or columns could not be fully loaded, and never modifies any board.6222 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to work a self-hosted kanban board as first-class users, exposing eleven kanban_* tools over a stateless Streamable HTTP endpoint for listing projects, stages, members and custom fields, and for creating, updating, moving and deleting tasks. Authenticates with bearer-token scopes so read-only or write access can be granted per agent, with every mutation audited.4MIT
- AlicenseNot gradedqualityAmaintenanceEnables agents to read and drive a local-first Kanban board for issue tracking, allowing them to list, create, update, and resolve issues from Claude Code sessions.8 npm1MIT
- FlicenseBqualityDmaintenanceMCP server that exposes the full Flow Boards REST API as Claude tools, enabling natural language management of tickets, flows, bins, boards, comments, and more.3810 npm1-
- 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 32 tools
Most tools have distinct resource+action targets, but a few read-only tools can be confused: get_manual_time_entries_for_task overlaps with get_time_entries_for_task (manual subset vs all types), and get_users vs get_collaborators differ by board access vs task collaboration.
Names mostly follow a snake_case verb_noun convention, e.g. create_task, update_task, get_comments. Minor inconsistencies include list_boards vs get_* reads, singular/plural mismatches (get_labels/create_label, set_date/get_dates), but overall the pattern is predictable.
32 tools is above the recommended 3-15 range and exceeds the 25+ threshold for 'too many.' While a Kanban API has many resources, the surface is heavy and includes many narrow read-only endpoints, making it over-scoped for an MCP server.
Core task lifecycle is covered (create/get/update/delete/move), plus boards, comments, labels, subtasks, and time entries. However several resources have create+get but no update/delete (subtasks, labels, comments) and others are read-only (attachments, relations, custom fields), leaving notable gaps an agent cannot fill.