A
licenseA
qualityD
maintenanceEnables managing KanbanFlow boards, tasks, and workflows directly from Cursor/Claude with a one-command setup.
16
7 npm
6
MIT
KanbanFlow MCP Server
by timaw513
Related Servers
Alternatives to KanbanFlow MCP Server
No user-submitted related servers found.
Related Servers
- 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.7 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.387 npm1-
Yokan Board MCPofficial
FlicenseAqualityDmaintenanceEnables AI agents to interact with Yokan Kanban Board API to manage boards, columns, and tasks through a tool-based interface.172-- FlicenseNot gradedqualityCmaintenanceEnables AI assistants like Claude to interact with Trello boards through natural language, supporting board operations including card management, list manipulation, attachments, labels, comments, checklists, and daily workflow automation.-
- FlicenseCqualityCmaintenanceEnables interaction with Wekan kanban boards through the Wekan REST API, supporting board, list, and card operations via natural language.76-
TDQS
C2.9/5.0
Scored across 32 tools
Disambiguation4/5
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.
Naming Consistency4/5
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.
Tool Count2/5
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.
Completeness3/5
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.
Maintenance
ActivityMaintained
ResponsivenessNo issues