triage-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | Optional GitHub token with public read access. Without it, you get GitHub's lower unauthenticated rate limit, and find_related_code returns an error because GitHub's code search refuses requests with no token. | |
| TRIAGE_MAX_WAIT_MS | No | Configures the longest wait for GitHub rate limits. If GitHub says to retry within 10 seconds, the server waits and retries twice at most; if the wait is longer, it does not wait and returns an error saying when the limit resets. |
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_issuesB | Search issues in a GitHub repository by free text and state. |
| get_issueA | Get one issue: title, body (truncated if long), labels, assignees, author, state and the most recent comments. |
| find_related_codeB | Search the code of a repository for a term. Requires GITHUB_TOKEN because GitHub code search needs authentication. |
| check_existing_fixB | Check whether an issue is assigned and whether open or merged pull requests reference it. Returns a verdict: unclaimed, assigned, open_pr_exists or already_fixed. |
| repo_contribution_rulesA | Fetch CONTRIBUTING.md and the pull request template, and list lines that mention AI use or disclosure. |
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 targets a distinct step of issue triage: fetching an issue, searching issues, searching code, checking for existing fixes, and fetching contribution rules. Minor overlap exists between get_issue (returns assignees) and check_existing_fix (checks assignment status) and between the two search tools, but descriptions make the boundaries clear.
Four of five names follow a verb_noun snake_case pattern (get_issue, find_related_code, check_existing_fix, search_issues). repo_contribution_rules breaks the pattern by dropping the verb, but it is still readable and unambiguous.
Five tools is well-scoped for a narrow triage workflow, and each one maps to a distinct decision an agent needs to make before claiming an issue. Nothing appears redundant or padding the surface.
The read-only triage lifecycle is well covered: discover an issue, search related issues/code, verify no existing fix, and check contribution rules before acting. Gaps are minor (no full untruncated issue body, no direct PR inspection or comment listing beyond what get_issue returns), but an agent can work around them.