GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
Is this GitHub issue free to take, is the project alive, will maintainers reply? Read-only.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
GITHUB_TOKENValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"contri": {
"command": "npx",
"args": [
"-y",
"contri-mcp"
],
"env": {
"GITHUB_TOKEN": "your-value"
}
}
}
}Run this in your terminal
claude mcp add contri --env GITHUB_TOKEN=your-value -- npx -y contri-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"contri": {
"command": "npx",
"args": [
"-y",
"contri-mcp"
],
"env": {
"GITHUB_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"contri": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"contri-mcp"
],
"env": {
"GITHUB_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account alphasafal, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: GITHUB_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 8 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
CONTRI for AI coding agents. Before your agent starts on a GitHub issue, it can check what CONTRI shows people in the browser: is someone already working on it, is the project alive, and will a maintainer reply?
check_issue finds assignees, “I'd like to work on this” comments (and claims that went quiet) and open pull requests that reference the issue.api.github.com, and never comments, claims or opens pull requests.| Tool | Answers | Requests (signed in / anonymous) |
|---|---|---|
check_issue | Can I take this issue? Looks free, Claimed by @x, Claim went quiet, Open PR #n, Assigned… | 1–2 / ~4 |
check_issues | The same for up to 10 issues in one call: verdicts only by default, so a shortlist is cheap | per issue, as above |
repo_health | Is it alive? PRs merged in 90 days (bots excluded), human authors, time to merge, release | 2 / ~7 |
team_responsiveness | Will someone reply? First team reply to outside PRs and issues, who is waiting, maintainers | 2–3 / ~35 |
find_issues | Beginner issues without an assignee; signed in, also whether an open PR already references it | 3 / 2 |
discover_projects | Active projects for a language or topic, ranked by recent human merges and good first issues | 1 / ~7 |
contribution_brief | A source-linked brief plus the README, contributing guide, code of conduct and templates | 2–3 / ~5 |
Prompts: find_first_issue (find an active project and an issue nobody is working on) and can_i_take_this (check one issue and say whether to start, ask first or pick another).
Every result carries a github field with the sign-in state and the requests GitHub says are left, so an agent can budget and knows when to offer sign-in. Reports are cached in memory for the same times as the extension (issue checks 10 minutes, overview 30 minutes, team 6 hours).
Token budget. Results are compact JSON without padding: a full check_issue is about 200–300 tokens, detail: "brief" (verdict and URL) about 40, thread: "digest" adds the issue head and last three comments for about 400 (the full thread can be ~3,500), and check_issues returns one footer for the whole batch. Numbers are rounded to one decimal and empty sections are left out, so an agent that only needs to know whether to proceed pays for little more than the verdict.
The server runs on Node.js 20.3 or later and is published to npm as contri-mcp, so there is nothing to clone or build.
Claude Code
claude mcp add --transport stdio contri -- npx -y contri-mcp
Claude Desktop, Cursor, Windsurf and other clients that use an mcpServers config file:
{
"mcpServers": { "contri": { "command": "npx", "args": ["-y", "contri-mcp"] } } }
If the client cannot find npx (it does not read your shell setup), use the full path from which npx.
From source (to try unreleased changes; building needs Node.js 22.12 or later, 24 recommended):
git clone https://github.com/alphasafal/contri ~/contri
cd ~/contri && npm ci && npm run build:mcp # writes mcp/dist/contri-mcp.js claude mcp add --transport stdio contri -- node ~/contri/mcp/dist/contri-mcp.js
To update a source install: cd ~/contri && git pull && npm ci && npm run build:mcp, then restart your MCP client.
Without signing in, GitHub allows 60 requests an hour, which an agent uses up quickly. Signing in raises it to 5,000 and lets CONTRI use one GraphQL request instead of dozens. There is no token to copy:
github.com/login/device. Open it, enter the code and approve CONTRI.This is the same sign-in as the extension: GitHub's device flow with the CONTRI OAuth App, no scopes (public, read-only access), no password through CONTRI. The sign-in is saved for next time in ~/.config/contri/mcp-credentials.json, readable only by you (set CONTRI_MCP_CREDENTIALS to use another path, or ask the agent to sign in with remember: false to keep it for this session only). sign_out forgets it; revoke it any time at github.com/settings/applications.
Prefer a token? Set GITHUB_TOKEN (or GH_TOKEN) in the server's env to a fine-grained token with Public repositories and every permission at No access. If GitHub rejects it, or it is still a placeholder like PASTE_YOUR_TOKEN_HERE, CONTRI carries on anonymously and offers to sign in instead of failing.
Ask your agent something like:
There is no backend and no analytics. The server sends requests only to GitHub (api.github.com, plus github.com for the sign-in), and your sign-in only there. Only public repositories are analyzed. Reports are kept in memory and are gone when the process exits; the only file written is the saved sign-in, if you sign in. Issue text goes to your agent only when it asks for it (check_issue with includeThread). See PRIVACY.md.
MIT