start-work
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub fine-grained token for the repo with Issues: read/write, Pull requests: read/write, and Metadata: read permissions. | |
| GITHUB_REPOSITORY | Yes | The GitHub repository in owner/repo form that holds the tickets. | |
| START_WORK_BRANCH_PREFIX | No | Optional branch prefix, e.g. hn/ gives hn/42-add-csv-export. Default is none. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_my_ticketsA | Open tickets assigned to me, highest priority first. Use this to pick what to work on next. |
| get_ticket_contextB | A ticket's description, acceptance criteria and discussion, plus its parent and child tickets, as a work brief. |
| start_ticketA | Claim a ticket: assign it to me, mark it in progress, and return the branch name to create plus the full work brief. Call this before writing any code. |
| open_pull_requestA | After the branch is pushed and tests pass: open a PR that closes the ticket, move the ticket to in review, and leave a comment linking the PR. A human reviews before merge. |
| set_ticket_statusB | Move a ticket to todo, in-progress, in-review or done. Use to put a ticket back if you stop work on it. |
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 5 tools
Each tool maps to a distinct step in the workflow: listing, reading context, claiming, opening a PR, and setting status. The only mild overlap is between start_ticket (which implicitly sets in-progress) and set_ticket_status, but the descriptions clarify that start_ticket is the claim-and-brief action while set_ticket_status is for manual moves.
All five tools follow a consistent snake_case verb_noun pattern (list_my_tickets, get_ticket_context, start_ticket, open_pull_request, set_ticket_status). No mixed conventions or vague verbs.
Five tools is well-scoped for a focused start-work workflow, and each tool earns its place as a distinct step. Nothing feels redundant or missing at the count level.
The surface covers the core lifecycle: discover tickets, read context, claim, open PR, and adjust status. Minor gaps exist—no way to create tickets, add standalone comments, or search/filter beyond 'my tickets'—but these are outside the apparent narrow purpose and agents can work around them.