Skip to main content
Glama
maoxiangzhe

board-mcp

by maoxiangzhe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to board-mcp

No user-submitted related servers found.

    Related Servers

    • Axis

      VirSanghavi
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for coordinating multiple AI agents across developers and vendors with a shared job board, per-file locking, and live project context.
      5
      AGPL 3.0

    • dibs

      Agenxy
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server enabling AI agents to coordinate on a shared board: they can declare work, exchange typed messages, transfer files, and hold advisory claims, preventing duplicate effort across agents.
      2
      Apache 2.0

    • AgentRoom MCP Server

      seonglae
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that provides coordination tools (claim, release, broadcast, state) for concurrent coding agents working on a CRDT-merged shared filesystem, ensuring no edits are lost and enabling collaborative task completion.
      MIT

    • agent-locks

      luohoa97
      A
      license
      A
      quality
      D
      maintenance
      A filesystem-based MCP server for AI coding agents to coordinate work across git worktrees by claiming files, checking for conflicts, and logging progress without affecting the repository's git history.
      5
      MIT

    • susan

      arkone-ai
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides cross-session awareness for Claude Code, tracking active sessions, file conflicts, and shared todos to enable agent coordination without blocking tool calls.
      860 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes: send_note/read_notes/ack_notes form a messaging trio, while claim_files/report_done/release_claim/check_conflict handle file ownership. The only minor overlap is between get_board and read_notes since both surface unread messages, but get_board is the board overview while read_notes is the dedicated mailbox, so the boundary is acceptable.

    Naming Consistency4/5

    Tool names mostly follow a verb_noun pattern: send_note, read_notes, ack_notes, claim_files, report_done, check_conflict, release_claim, post_decision. init_bulletin and get_board deviate slightly (init_/get_ instead of a plain verb), but the pattern is still recognizable and readable.

    Tool Count5/5

    10 tools is well-scoped for a collaboration board MCP server. Each tool covers a distinct workflow: initialization, board reading, messaging, file claiming, conflict checking, and decision posting. No tool feels redundant or unnecessary.

    Completeness4/5

    The tool surface covers the core collaboration lifecycle: init_bulletin bootstraps the board, get_board reads it, send_note/read_notes/ack_notes handle directed messaging, claim_files/report_done/release_claim/check_conflict manage file ownership, and post_decision records shared decisions. A minor gap is the lack of a way to edit or remove a posted decision, but agents can work around that by posting a correction.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources