GitHub MCP server
Issues, pull requests and code search without leaving the conversation. Scope the token to what you need.
Tested on Claude Sonnet · 4.5 ·
MCP · Free, open source
It helps with the dull half of maintenance: reading an issue thread, summarising what a pull request changed, tracing where something was introduced.
What it does well. Context that would cost five browser tabs arrives in one request. Triage across many issues stops eating an afternoon.
What it does badly. Strangers write issue bodies and comments, so they can carry instructions aimed at your model. Treat anything it reads from a public repository as untrusted input, because it is.
Token scope. A classic token with repo scope can also push and close things. For reading only, use a fine-grained token limited to the repositories you name, with read permissions and nothing more.
Notes from the author
Keep the token out of the config file if your client can read it from the environment. A config file holding a write-capable token is a credential sitting in a directory the filesystem server may be able to read as well.
For information only, not professional advice. You use it at your own risk and we are not liable for any loss or damage. See the disclaimer.
Tagged