Skip to main content
Glama
JovianIce

git-bug-broker

by JovianIce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to git-bug-broker

No user-submitted related servers found.

    Related Servers

    • AgentXFlow

      harlixay7
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple AI coding agents to collaborate on the same Git repository without conflicts through isolated worktrees, file locking, automated test verification, and a serialized merge queue.
      2 npm
      7
      MIT

    • agentclaim

      volkangunay
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple AI coding agents to safely collaborate in the same git working tree by managing file ownership, merging writes, and preventing snapshot races.
      4 npm
      2
      MIT

    • tower-mcp

      Rohanxmalik
      A
      license
      B
      quality
      A
      maintenance
      Enables AI coding agents on different machines and accounts to work one repository as a team by declaring file and symbol claims before editing, so collisions are refused up front rather than discovered at merge. It also supports delegating tasks between teammates' agents, which do the work with their own tokens and commit, with replies, commit shas, claims and messages landing on one shared board.
      20
      2
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.3/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool maps to a fairly distinct action: create (file_entry), read (get), list (query), and targeted mutations (set_status, set_title, relabel, edit_body, edit_comment, comment). The main friction is edit_body vs edit_comment, which overlap since the body is described as 'its first comment'—an agent could hesitate over which to use.

    Naming Consistency3/5

    Several tools follow a clean verb_noun pattern (edit_comment, set_status, set_title, edit_body, file_entry), but others are bare single words (get, query, relabel, comment). It's readable but the convention is mixed rather than predictable.

    Tool Count5/5

    Nine tools is well-scoped for an issue-tracker surface, covering the core lifecycle without bloat or redundancy. Each tool clearly earns its place.

    Completeness4/5

    Creation, reading, listing, commenting, and most update operations (status, title, labels, body, comments) are covered. The notable gap is deletion—no tool to remove an entry or a comment—though this may be intentional for an append-oriented bug tracker.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources