Field-by-field comparison
Compare the evidence before choosing an MCP.
Each signal stays separate, missing facts remain visible, and the column order follows your selection.
| Evidence field | GitHub MCPMCP100 Selected | Context7 MCPMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP GitHub · Publisher source ↗ | First-party MCP Upstash · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Aug 14, 2026 Package: Not documented | Repo: Aug 14, 2026 Package: Aug 11, 2026 |
| Popularity evidence | ||
| GitHub stars | 32,248 GitHub stars · checked 2026-08-14T18:46:26.000Z | 60,740 GitHub stars · checked 2026-08-14T18:46:26.000Z |
| 30-day package downloads | No reliable download data | 3,916,841 30-day package downloads · checked 2026-08-14T18:46:26.000Z |
| External adoption evidence |
|
|
| Client coverage | ||
| Client coverage details | Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP | Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | Hosted service supports OAuth; local stdio uses GITHUB_PERSONAL_ACCESS_TOKEN. GitHub recommends minimum scopes, separate tokens, rotation, and environment-variable handling. | Remote MCP accepts CONTEXT7_API_KEY as an HTTP header. The local package accepts --api-key. The CLI can use OAuth to generate an API key; unauthenticated documentation commands may have lower limits. |
| Cost | The open-source server is MIT licensed. GitHub account, Copilot, Enterprise, Actions, API, or other product charges and limits may apply independently. | A free API key and free usage are documented, with higher-rate or team/enterprise offerings potentially requiring a paid plan. Applicable limits should be checked in the current Context7 dashboard. |
| Permissions | Access follows the authenticated GitHub identity and granted OAuth/PAT permissions. The server supports tool allow-lists, read-only mode, repository-oriented toolsets, and lockdown mode; write tools remain possible unless read-only mode is enabled. | The MCP surface resolves library identifiers and queries documentation. It does not require repository or filesystem write access for the documented hosted mode. |
| Data handling | Repository contents, issues, pull requests, users, actions, and other enabled GitHub API data may be returned to the MCP client. The local server passes requests to GitHub; the hosted server is operated by GitHub. Do not place PATs in committed configuration. | Context7 states that formulated queries are sent to its API while full prompts, source code, and conversation history are not transmitted; its tool descriptions instruct clients to remove secrets, personal data, and proprietary code. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | A broadly scoped token plus write-capable tools can alter repositories and collaboration records. Prefer fine-grained credentials, repository restriction, explicit toolsets, GITHUB_READ_ONLY=1, and lockdown mode where public-content prompt injection is a concern. | Primary risks are query disclosure, stale or inaccurate indexed documentation, and accidental API-key exposure. Keep queries free of proprietary details and verify consequential advice against first-party library documentation. |
| Evidence date | ||
| Editorial review | 2026-07-24 | 2026-07-24 |
| Candidate evidence | 2026-08-14T18:46:26.000Z | 2026-08-14T18:46:26.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →