GitHub Triage Agent MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRY_RUN | No | Set to 'false' to enable live GitHub mutations. Default is 'true'. | true |
| GITHUB_TOKEN | Yes | GitHub personal access token used for API access. | |
| TRIAGE_CONFIG | No | Path to the YAML configuration file for policies and thresholds. Defaults to config.yaml. | |
| OPENAI_API_KEY | No | OpenAI API key (alternative LLM backend). | |
| ANTHROPIC_API_KEY | No | Anthropic API key (default LLM backend). |
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 |
|---|---|
| get_issueB | Fetch full issue metadata including labels, assignees and comments. |
| search_issuesB | Search issues/PRs in one repository (GitHub search syntax) to find related or duplicate reports. |
| add_labelsA | Add one or more labels to an issue or pull request. |
| post_commentB | Post a comment on an issue or pull request. |
| assign_issueA | Assign one or more GitHub users. Users are verified as assignable first; unverifiable users are rejected, never guessed. |
| close_issueA | Close an issue. DESTRUCTIVE: the first call returns a proposed action for human review and does NOT close anything. Only call again with confirm=true after the human has explicitly approved. |
| get_repository_contextA | Fetch repository decision context: description, topics, README, CONTRIBUTING.md, CODEOWNERS and the available labels. |
| get_pull_requestA | Fetch a pull request with changed files, commits, reviews, CI check status and linked issues. |
| reopen_issueB | Reopen a closed issue. DESTRUCTIVE: requires confirm=true after explicit human approval, same flow as close_issue. |
| get_recent_repository_activityB | List recently updated issues/PRs (default: last 14 days). |
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 10 tools
Each tool maps to a distinct resource-action pair: fetching issues vs PRs, searching, labeling, commenting, assigning, closing, reopening, and retrieving repo context or recent activity. No two tools appear to overlap in purpose, and descriptions clarify the boundaries.
All tools follow a consistent verb_noun snake_case pattern (get_issue, search_issues, add_labels, close_issue, etc.). The naming style is uniform and predictable across the entire set.
10 tools is well-scoped for a GitHub triage agent: it covers fetching, searching, acting on issues/PRs, and gathering repository context without unnecessary redundancy or bloat.
The surface covers the core triage workflow: discover, inspect, label, comment, assign, close, and reopen. Minor gaps exist such as no explicit remove_labels, unassign, or edit_issue, but agents can work around these without major dead ends.