GitHub (read Only) vs Github MCP
A side-by-side look at the GitHub (read Only) and Github MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose GitHub (read Only) for version control work as a local process; choose Github MCP for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose GitHub (read Only) when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
Choose Github MCP when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GITHUB_MCP_ENABLE_WRITE, GITHUB_TOKEN. - You want tools like
get_repo, list_issues, get_issue.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 33/100 · Emerging | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | GITHUB_MCP_ENABLE_WRITEGITHUB_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 14 |
| Full listing | View GitHub (read Only) | View Github MCP |
Tools & capabilities
GitHub (read Only) tools
No tool names declared yet. Check the project README from the listing page.
Github MCP tools 14
get_repoRepo metadata (stars, language, license, default branch, archived flag...)list_issuesList issues on a repo (PRs filtered out)get_issueFetch a single issuelist_pull_requestsList pull requests on a repoget_pull_requestFetch a single pull requestget_file_contentRead a repo file's content (base64-decoded, binary detected not decoded)search_reposSearch public repositoriesget_userPublic user/org profilelist_commitsList commits on a branch/refcreate_issueOpen an issuecomment_on_issueComment on an issue/PRupdate_issue_stateOpen/close an issue- +2 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
GitHub (read Only)
{
"mcpServers": {
"github-read-only": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/AbdulMuhaiminKhan/github-mcp",
"github-mcp"
]
}
}
}
Github MCP
{
"mcpServers": {
"github-mcp": {
"command": "uvx",
"args": [
"jaimenbell-github-mcp"
],
"env": {
"GITHUB_MCP_ENABLE_WRITE": "YOUR_GITHUB_MCP_ENABLE_WRITE_HERE",
"GITHUB_TOKEN": "YOUR_GITHUB_TOKEN_HERE"
}
}
}
}
Frequently asked questions
GitHub (read Only) is categorized under Version Control and uses a local stdio subprocess. Github MCP belongs to Version Control and uses a local stdio subprocess. Pick GitHub (read Only) for version control work and Github MCP for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
GitHub (read Only) has no declared pricing — check the project's own site. Auth: api key required. Github MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add github-read-only and github-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, GitHub (read Only) has a quality signal of 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Github MCP has 49/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.