Context7 vs Memory MCP
Side-by-side comparison with live GitHub signals. Last updated April 1, 2026.
| Metric | Context7 | Memory MCP |
|---|---|---|
| GitHub Stars | 51.3K | 82.7K |
| Contributors | 114 | 430 |
| Last Commit | Mar 31, 2026 | Mar 29, 2026 |
| Open Issues | 159 | 628 |
| License | open-source | open-source |
| Pricing | open-source | open-source |
| Free Tier | Yes | Yes |
| Category | mcp-servers | mcp-servers |
| Trending | No | No |
Shared Tags
Only in Context7
Only in Memory MCP
About Context7
Context7 solves the stale-docs problem: instead of relying on an LLM's outdated training data, it fetches live, version-specific documentation for thousands of popular libraries and injects it directly into the model's context window. Ask Claude Code to use React 19, Next.js 15, or any other library and get answers grounded in the actual current API — not hallucinated method signatures from two years ago.
View full listingAbout Memory MCP
The official Anthropic memory MCP server gives AI assistants persistent, cross-session memory using a local knowledge graph stored as a JSON file. Claude can create entities (people, projects, concepts), record relations between them, and add observations over time — then recall that information in future sessions. Ideal for long-running projects where continuity matters: the assistant remembers your architecture decisions, team conventions, and in-progress work without you having to repeat context.
View full listing