github-triage-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | Read-only fine-grained GitHub token with Issues: Read-only and Metadata: Read-only permissions. | |
| ALLOWED_REPOS | Yes | Comma-separated allowlist of repositories that may be accessed, e.g. kenzoob/My-Engine,facebook/react. | |
| MAX_BODY_CHARS | No | Truncation limit for issue text (optional, default 4000). | 4000 |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_issuesC | Lists issues (not pull requests) for an allowlisted repository, with labels, author, date and comment count. |
| get_issueB | Returns an issue's body and its 20 most recent comments. |
| search_issuesC | Searches issues in an allowlisted repository matching a query. |
| repo_activityC | Summarizes issues opened and closed, and pull requests merged, over a recent period. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| triage_issues | Lists the open issues of a repository, groups them by theme, suggests a label and a priority for each one, and flags likely duplicates. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
list_issues, get_issue, and search_issues all target issues and could be confused at the margins, but the descriptions draw clear lines (enumerate vs. fetch one vs. query-match), and repo_activity is unmistakably distinct as a period summary.
Three tools follow a clean verb_noun pattern (list_issues, get_issue, search_issues), but repo_activity breaks it with a noun-only form, a minor deviation from an otherwise predictable convention.
Four tools is a tight, well-scoped set for a triage-focused server; each earns its place, though the surface arguably sits at the thin end given the absence of any action tools.
The toolset is entirely read-only: it can list, fetch, search, and summarize issues but offers no way to label, comment on, assign, or close them, which are core actions for an actual triage workflow.