Skip to main content
Glama
timaw513

KanbanFlow MCP Server

by timaw513

Related Servers

Alternatives to KanbanFlow MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      A 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.
      6
      222 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      4
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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

    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