github-triage-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TRIAGE_ORG | No | A GitHub organisation name to scope the search to, e.g. 'acme'. Only used if GITHUB_TRIAGE_REPOS is not set. | |
| GITHUB_TRIAGE_REPOS | No | Comma-separated list of repositories to scope the search to, e.g. 'acme/api,acme/web'. Overrides GITHUB_TRIAGE_ORG and the repos argument on a call overrides both. |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| triageA | Open issues that involve you, sorted by whose turn it is: waiting on you, waiting on someone else, pulled in, unassigned. Returns a ready-to-read Markdown report — relay it as-is rather than rewriting it. Start here when asked what needs attention. |
| get_issueA | The full text of one issue: body and every comment, untrimmed. Use after |
| search_issuesB | Search issues with GitHub search syntax. The configured scope is added automatically unless |
| linked_issuesA | Issues and pull requests cross-referenced from an issue, and ones that reference it back. Use to find the PR that implements an issue, or the sibling issue a discussion moved to. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| digest_issue | Read one issue thread and report what was decided, what is still open, and what happens next. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool serves a distinct purpose: triage provides an overview, get_issue retrieves full thread content, search_issues queries by syntax, and linked_issues discovers cross-references. There is no overlap or ambiguity between them.
get_issue and search_issues follow a clear verb_noun pattern, but triage is a bare imperative and linked_issues is a descriptive noun phrase rather than an action. The mixed conventions are still readable, but not fully consistent.
Four tools is exactly right for a focused triage server. Each tool covers a necessary step in the triage workflow without redundancy or bloat.
The tool surface covers the complete read-only triage workflow: get an overview, drill into full details, search, and trace relationships between issues and PRs. No obvious gaps exist for the stated purpose.