Skip to main content
Glama

Related Servers

Alternatives to Standup MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to manage Kanban tasks, boards, teams, and checklists via natural language, with full CRUD operations and live updates.
      48 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to operate a Kanban board through MCP tools: taking and moving cards, updating statuses, splitting subtasks, linking pull requests, and pausing for human approval that only people can grant.
      409 npm
      PolyForm Noncommercial 1.0.0
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to manage kanban boards with tasks, including creating boards, items, moving between columns, and searching.
      8
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to read and write a local kanban board, adding and editing cards, moving them between columns, managing projects, and writing update entries so their work is visible in real time.
      3 npm
      1
      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.
      11 npm
      1
      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

    TDQS

    A3.6/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action: card CRUD (create/update/move/delete), assignment pair (assign/unassign), comment pair (add/get), board reads (get/list), and specialized setters (set_card_work, update_board_context, update_column_agents). Descriptions clarify boundaries where concepts could touch, e.g. update_card only edits text while move_card changes columns. No two tools appear to do the same thing.

    Naming Consistency5/5

    Every tool follows a clean verb_noun snake_case pattern: get_board, list_boards, create_card, update_card, delete_card, move_card, add_comment, get_comments, assign_card, unassign_card, search_cards, set_card_work, update_board_context, update_column_agents. No convention mixing.

    Tool Count5/5

    14 tools is well within the sweet spot for a kanban/standup server and each tool earns its place across card, comment, assignment, board, and work-tracking concerns. Nothing feels padded or redundant.

    Completeness4/5

    Card lifecycle is fully covered (create, update, move, delete, assign, unassign, comment, search) plus board context and work tracking. Minor gaps exist: no create_board/delete_board and no edit/delete for comments, but these are workable around and the core standup workflow is intact.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues