Summary
GitHub search without the browser, and with better sorting than it gives you.
The sort fields are the useful part: issues ordered by reactions or interactions surface what people actually care about, which default relevance ranking buries.
What it is
A GitHub MCP server built on the GitHub REST API and focused on search. Every call takes a query with page and per_page; issue and commit searches add sort and order fields of their own.
What you get
- Repositories searched by query
- Issues searched, sorted by comments, reactions, interactions, created or updated
- Commits searched, sorted by committer date or author date
- Code searched across repositories
- Users, topics and labels searched
- One repository's issues listed
- Pagination on every call — page and per_page, up to 100 per page
Requirements
A GitHub personal access token in GITHUB_PERSONAL_ACCESS_TOKEN. Run it with npx -y github-mcp-server; a fine-grained token scoped to what you want searched is enough.
Setup effort
One command plus a key — npx -y github-mcp-server, then supply credentials