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 | CodeGraph MCPWatchlist candidate | Context7 MCPMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP CodeGraph AI · Publisher source ↗ | First-party MCP Upstash · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Aug 10, 2026 Package: Aug 10, 2026 | Repo: Aug 14, 2026 Package: Aug 11, 2026 |
| Popularity evidence | ||
| GitHub stars | 61 GitHub stars · checked 2026-08-14T18:46:26.000Z | 60,740 GitHub stars · checked 2026-08-14T18:46:26.000Z |
| 30-day package downloads | 5,470 30-day package downloads · checked 2026-08-14T18:46:26.000Z | 3,916,841 30-day package downloads · checked 2026-08-14T18:46:26.000Z |
| External adoption evidence |
|
|
| Client coverage | ||
| Client coverage details | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio | 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 | None for the local stdio community server. | 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 repository is Apache-2.0 licensed and the community server has no documented service fee. Local compute and storage apply, and separately offered CodeGraph Pro capabilities may be paid. | 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 | The server reads and indexes the current working directory by default or explicit `--workspace` paths. Tools can query and reindex code, index Markdown, persist project memories, and generate architecture documentation. Exclusion flags and profiles narrow filesystem and tool reach. | 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 | Code-derived graph data, embeddings, indexed documentation, and memories persist locally under the CodeGraph data directory. The default embedding model is downloaded on first run; built-in exclusions cover common build, credential, and secret-file paths but do not replace an explicit workspace review. | 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 | The main risks are indexing unintended source or sensitive files, persisting source-derived embeddings and memories, and exposing broad tools to the agent. Set an explicit workspace, add exclusions, start with a narrow profile or graph-only mode, and protect or remove local index data when no longer needed. | 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 →