git-bug-broker
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITBUG_BROKER_URL | No | Optional URL of an already running git-bug web UI. If not provided, the broker will start its own. | |
| GITBUG_BROKER_REPO | Yes | Path to the git-bug repository | |
| GITBUG_BROKER_RULES | No | Optional path to a JSON rules file enforcing project conventions. If omitted, defaults are used. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| file_entryA | File a new entry. labels must include exactly one area/ and one kind/ (defect, chore, decision, investigation, idea); add filed-by/ when an agent files it. |
| commentC | Add a comment to an entry, by id or unique id prefix. |
| edit_bodyC | Replace an entry's body (its first comment). Checked against the entry's kind. |
| edit_commentB | Replace the text of one comment, by the comment id that get() returns. |
| relabelA | Add and remove labels in one operation. The resulting set must satisfy the standard, so swap an area with add=['area/new'], remove=['area/old'] in one call. |
| set_statusB | Open or close an entry ('open' or 'closed'), optionally with a comment in the same operation. A closing comment should name the commit and the test that pins the fix. |
| set_titleC | Retitle an entry. The new title is checked against the standard. |
| getB | Read one entry: title, status, labels, body and comments with their ids. |
| queryA | List entries matching a git-bug query, for example 'status:open label:area/api' or 'label:kind/defect sort:edit'. Returns ids, titles, status and labels, not bodies. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
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.
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.
Nine tools is well-scoped for an issue-tracker surface, covering the core lifecycle without bloat or redundancy. Each tool clearly earns its place.
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.