list_repository_issuesLABSCO SUMMARY
Reading a hundred issues without spending the context on JSON.
General-purpose GitHub servers return every field GitHub has; this one returns five, which is what makes a bulk pass over a repository's issue history fit in a single session. It only lists — nothing here writes.
What it is
Two GitHub listing tools that return only id, html_url, title, body and comment bodies — built for reading a lot of issues or PRs in one session.
What you get
- Issues from a repository, updated at or after a timestamp you give
- Pull requests from the same repository, in the same trimmed shape
- Five fields per item: id, html_url, title, body, comment bodies
- Responses a fraction of the size of the full GitHub API equivalent, because every field outside those five is dropped
- Awareness of GitHub's API rate limits built in
Requirements
A GitHub personal access token as GITHUB_TOKEN, scoped repo or public_repo, plus read:org for organisation repositories. Installed globally from npm as @wipiano/github-mcp-lightweight.
Setup effort
One command plus a key — npm install -g @wipiano/github-mcp-lightweight, then supply credentials
USE CASES
01
Summarising what has been reported since a release
Set the since timestamp to the release date and read every issue raised after it.
02
Reviewing what has landed in a period
The same since filter over pull requests gives the changes without opening the compare view.
03
Finding patterns across many issues at once
Titles, bodies and comment bodies for the whole set, which is enough to cluster complaints without any further fetches.
04
Keeping a large repo scan inside one context window
Both listings drop everything except the five readable fields, so the scan does not exhaust the budget halfway through.
2 tools
Listed in project docs. Your client may show a different list.
list_repository_pull_requestsBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- npx on PATH
- GITHUB_TOKEN in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g @wipiano/github-mcp-lightweightMCP Clients
Cline
CLINE · JSON
{
"mcpServers": {
"github-lightweight": {
"command": "npx",
"type": "stdio",
"args": [
"-y",
"@wipiano/github-mcp-lightweight"
],
"env": {
"GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
}
}
}
}Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"github-lightweight": {
"command": "github-mcp-lightweight",
"env": {
"GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
}
}
}
}
