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.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldGitHub MCPMCP100 RecommendedContext7 MCPMCP100 Recommended
Task fit
Best for
  • Repository, issue, pull-request, and code context
  • Teams that can issue a narrowly scoped PAT or use the hosted OAuth flow
  • Read-only GitHub investigation using restricted toolsets
  • Current library and API documentation inside coding agents
  • Read-only technical lookup with a small two-tool surface
  • Users who want remote or local npx connection options
Not ideal for
  • Git hosting outside GitHub
  • Users unable to run Docker for the documented local configuration
  • Workflows that need only a small amount of public repository context
  • Private internal documentation not indexed by Context7
  • Guaranteed authoritative answers without checking the cited upstream docs
  • Offline-only development
Avoid when
  • You cannot restrict the token to the necessary repositories and scopes
  • The agent must not receive private repository, issue, pull-request, or user data
  • Your organization has not approved the OAuth app or PAT policy
  • Your policy prohibits sending formulated documentation queries to a hosted service
  • You require complete or guaranteed-correct community-contributed documentation
  • You cannot keep an API key out of shared configuration
Provenance
Provenance details

First-party MCP

GitHub · Publisher source ↗

First-party MCP

Upstash · Publisher source ↗

Maintenance
Maintenance details

Repo: Sep 22, 2026

Package: Not documented

Repo: Sep 24, 2026

Package: Sep 21, 2026

Popularity evidence
GitHub stars

33,158

GitHub stars · checked 2026-09-24T04:14:26.342000Z

62,372

GitHub stars · checked 2026-09-24T04:14:16.247000Z

Package downloads / 30 daysNo reliable download data

3,451,044

package downloads / 30 days · checked 2026-09-24T04:17:39.154000Z

External adoption evidenceNot documented
  • npm: package downloads: 3,916,841Exact attributable signal.npm: package downloads · Rolling 30 days · checked 2026-08-14T18:46:26.000ZEvidence source ↗
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 noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationHosted 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.
CostThe 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.
PermissionsAccess 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 handlingRepository 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
  • The default local toolsets include repositories, issues, pull requests, users, and context; limiting toolsets reduces capability and context size.
  • Local Docker keeps the MCP process local but still sends authorized requests to GitHub APIs.
  • PAT setup is explicit and portable, while hosted OAuth is easier but relies on GitHub's remote MCP service.
  • An API key is recommended for higher limits, adding account and secret management.
  • Context7 says it sends formulated queries rather than full prompts or source code, but queries still leave the client.
  • Community-contributed projects can be incomplete or inaccurate and should be checked against primary documentation.
Risk contextA 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 review2026-07-242026-07-24
Candidate evidence2026-09-24T04:25:05.554391Z2026-09-24T04:25:05.554391Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →