Skip to main content
Glama

Related Servers

Alternatives to Kanboard MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude Code to control a Planka 2.x board via 15 MCP tools, with writes re-read and verified so reported success matches the board, plus an optional workflow that turns the board into durable agent memory.
      15
      56 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Planka kanban boards, including creating, updating, and organizing tasks, lists, and cards via MCP.
      65
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables people and their AI agents to share a kanban board whose tasks, hand-offs, reviews, notes and alerts live as markdown files in a private GitHub repo, with per-person access control. Works from Claude, ChatGPT, Claude Code, Codex or any MCP-speaking client, and can draw the board inside chats.
      AGPL 3.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Connect AI assistants to Kanera project management. Search and manage work across boards and workspaces, including cards, assignments, due dates, checklists, comments, attachments, personal notes, priorities, automations, activity history, reporting, and portfolio insights. Kanera MCP also supports creating new workspaces and boards from templates.
      17
      -

    TDQS

    B3.4/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools target a clear resource+action pair (get_task, move_task, close_task, add_comment), and the create/update split is well signposted. The only real overlap is list_tasks vs search_tasks vs get_board vs get_overdue_tasks, which all return task collections, but the descriptions differentiate them by filter mechanism (status/column vs Kanboard filter syntax vs board layout vs due date).

    Naming Consistency5/5

    Every name is snake_case verb_noun: get_*, list_*, search_*, create_*, update_*, move_*, close_*, reopen_*, add_*. Verb choice is semantically consistent (get for single-item fetch, list for collections, create/update for mutations), with only trivial variance like add_comment vs create_subtask reflecting the domain.

    Tool Count4/5

    17 tools is slightly on the heavy side but each covers a distinct slice of the Kanboard domain (identity, projects, board, tasks, subtasks, comments, files, users) with little redundancy. Nothing looks like filler; it sits just above the comfortable band rather than being bloated.

    Completeness3/5

    The task lifecycle is well covered (create, update, move, close, reopen, comment, subtask, read attachment), but project management is read-only — no create_project, update_project, or archive, and there is no delete_task, delete_subtask, or delete_comment. File handling is also read-only (get_task_file with no upload), so an agent hitting those operations dead-ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues