gh-triage-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub personal access token. For public repos, scope `public_repo` is sufficient; for private repos, use `repo`. Comment posting always requires a token. |
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 |
|---|---|
| search_issuesA | Search GitHub issues. Returns a short, LLM-shaped list: number, url, labels, owner/repo, and a suggested next action. Not a raw REST dump. Scope with repo=owner/name when you know it. |
| summarize_issueA | Load one issue and its recent comments, shaped for triage: excerpts, labels, and the owner/repo/number you need to comment. Use this before draft_comment. |
| draft_commentA | Draft a comment on an issue. Does not post unless confirm=true. Always show the draft to a human first. |
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 3 tools
Each tool has a clearly distinct role: search_issues finds issues, summarize_issue loads details and comments, and draft_comment creates a proposed response. There is no meaningful overlap or ambiguous boundary between them.
All tool names follow a consistent verb_noun pattern in snake_case: search_issues, summarize_issue, draft_comment. The naming style is uniform and predictable across the entire server.
Three tools form a tight, well-scoped set for an issue triage workflow: find, understand, and draft a response. The count is neither too sparse nor excessive for the stated purpose.
The server covers the full triage lifecycle: discovering relevant issues, reading issue context with comments, and drafting a comment with optional posting. There are no obvious dead ends for the intended use case.