github-triage-mcp
Provides GitHub issue triage capabilities, including determining whose turn it is on each issue, generating Markdown triage reports, retrieving full issue threads, searching issues, and finding linked issues and pull requests.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@github-triage-mcp what needs me right now?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
github-triage-mcp
An MCP server that answers "what needs me right now?" across your GitHub issues, and returns the answer as Markdown that is already formatted.
Why
gh issue list can tell you which issues are open and who they are assigned
to. It cannot tell you the thing you actually want to know, which is whose
turn it is — that needs the author of the most recent comment compared
against the assignee. So you end up asking an assistant to work it out, and
explaining the grouping you want, again, every time.
This server does that comparison and ships the formatting with it. The report comes out the same shape whether you asked for "what's on my plate" or "정리해 줘".
Related MCP server: oss-issues-mcp
What you get
**12 open issues** involving `you` in `acme`
## 🔴 Your turn (3)
<sub>assigned to you and nothing is blocking them</sub>
| Issue | Repo | Type | Title | Last word | Idle |
|---|---|---|---|---|---|
| #412 | api | bug | retry budget is consumed before the first… | reviewer | 13d |
| #398 | api | perf | stale scan takes 71% of the time budget | opened by you | 9d |
| #77 | web | — | dark mode flashes on first paint | teammate | 2d |
## 🟡 Waiting on others (6)
## 🟠 You were pulled in (1)
## ⚪ Unassigned (2)
> Longest untouched on your side: #412 — 13d.
> No reply for 35d on #301 — worth chasing.Issues are bucketed by whose turn it is, then ordered longest-idle first inside each bucket, because the thing that has sat untouched longest is the thing most likely to have been forgotten.
[feat] / [bug] / [chore] title prefixes are lifted into their own column.
On repositories that use title prefixes rather than labels — which is most of
them — that is the real taxonomy.
Requirements
Node.js 18+
The GitHub CLI (
gh), authenticated:gh auth login
Everything goes through gh, so this server never stores a token of its own and
works with GitHub Enterprise wherever gh does.
Install
claude mcp add --scope user github-triage -- npx -y github-triage-mcpgit clone https://github.com/yangchoi/github-triage-mcp.git
cd github-triage-mcp
npm install && npm run build
claude mcp add --scope user github-triage -- node /absolute/path/to/dist/index.jsScope
Without configuration the search covers every repository you can see, which is slow and noisy. Narrow it:
Variable | Example | Effect |
|
| Only these repositories. |
|
| The whole organisation. |
GITHUB_TRIAGE_REPOS wins when both are set, and the repos argument on a
call overrides both.
Tools
Tool | Arguments | Purpose |
|
| The report above. Start here. |
|
| One thread in full — body and every comment, untrimmed. |
|
| GitHub search syntax, scope added automatically. |
|
| Cross-referenced issues and the PRs that close them. |
get_issue deliberately does not trim. Issue threads are often where the design
actually lives — a single comment can run to several thousand characters of
specification — and a summary of a summary loses the specifics that matter.
The digest_issue prompt
An MCP server has no language model inside it, and Claude Code does not support sampling (where a server can ask its client to run a completion). So the server does not summarise.
It does something better suited to it: it owns the instruction. The
digest_issue prompt tells the model reading the thread to report what was
decided, what is still open, and what happens next — with a fixed set of
headings, and an instruction not to invent a next step the thread never agreed
on. The summarising is done by the model that already has your conversation and
your project history; the shape of it comes from here.
Tests
npm testThe suite covers the turn-taking rules, ordering, Markdown rendering, the tool and prompt surface, and the failure modes — all against fixtures and the built server, with no network access and no GitHub account needed.
License
MIT
Available Tools
4 toolsget_issueA
The full text of one issue: body and every comment, untrimmed. Use after triage or search_issues when a thread needs to be read or summarised.
Inputs: repo (required), number (required).
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.
Inputs: repo (required), number (required).
search_issuesB
Search issues with GitHub search syntax. The configured scope is added automatically unless repos is given.
Inputs: query (required), limit, repos, state.
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.
Inputs: limit, repos.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Writes your daily standup from GitLab or GitHub merge request state: what's ready, blocked or waiting on your review, and why a pipeline is red, read from the failing job log. OAuth sign-in, no API keys; can post the note to Slack, Discord or Google Chat on a schedule.
Find open-source GitHub issues to contribute to, matched to your skills; you approve every PR.
Work your users' feedback queue from your editor: triage, approve fixes, ship draft PRs.
Manage repositories, users, releases, and automate GitHub workflows
Related MCP Servers
- AlicenseAqualityDmaintenanceGenerates engineering intelligence reports (standups, weekly summaries, sprint retrospectives) from GitHub and Jira data, accessible via MCP clients or CLI.10MIT
- AlicenseAqualityCmaintenanceEnables triage of GitHub issues by fetching and filtering issues, checking claim status, and listing new open issues across a watch-list.4MIT
- AlicenseNot gradedqualityBmaintenanceRanks your open pull requests by urgency with human-readable reasons, surfacing changes requested, unresolved review threads, real failing checks, merge conflicts, and reviewer silence. Exposes tools for an attention report, a simple list of open PRs, and a per-PR deep dive covering reviews, checks, and threads.87 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables agents and developers to check, before they comment or write code, which issue claims have gone stale and which finished fork branches never became a pull request. It ranks abandoned claims oldest-first, flags parked branches with compare data, and reports every claimant and linked PR for a single issue.94 npmMIT