Context7 MCP Server vs Fetch MCP Server
Both pull external content into Claude's context, differently: Context7 serves curated, version-accurate library documentation on demand, while Fetch retrieves and converts arbitrary URLs to markdown. For 'my model keeps hallucinating this API', Context7 is purpose-built; Fetch is the general-purpose tool when you need any page, not just docs.
GitHub data verified 2026-07-30 — objective fields only, no editorial scoring.
| Context7 MCP Server Real-time documentation lookup for libraries and frameworks | Fetch MCP Server Make HTTP requests to any URL with configurable options | |
|---|---|---|
| GitHub stars | 59,989 | 89,034 |
| Forks | 2,872 | 11,331 |
| Open issues | 30 | 479 |
| Last commit | 2026-07-29 | 2026-07-29 |
| Maintenance status | Actively maintained | Actively maintained |
| License | MIT | Other |
| Language | TypeScript | TypeScript |
| Install | npx @upstash/context7-mcp | npx @modelcontextprotocol/server-fetch |
| Author | Upstash | Anthropic |
| Official listing | No | Yes |
| Community votes | 0 | 0 |
| Copies from directory | 0 | 0 |
GitHub statistics are measured at repository level; servers that live in a shared monorepo show that repository's stats. This comparison is generated from directory data — no sponsored placement, see the curation policy.