Memory alternatives
6 servers that overlap with Memory. Compared on install command, provenance, and the tags they share — not on a feature checklist nobody maintains.
What these have in common
All of them overlap with Memory on at least one capability tag. Overlap is not equivalence: two servers can both say "database" and solve different problems. Read the full entry for what the current one is actually for before switching.
Side by side
| Server | Install | Source | Shared tags |
|---|---|---|---|
| Memory | npx -y @modelcontextprotocol/server-memory | Official | memory, knowledge-graph, reference |
| Filesystem | npx -y ./ | Official | files, local, reference |
| Git | npx -y ./ | Official | git, repo, reference |
| Fetch | npx -y mcp-server-fetch | Official | web, scraping, reference |
| Time | npx -y mcp-server-time | Official | time, utility, reference |
| Sequential Thinking | npx -y @modelcontextprotocol/server-sequential-thinking | Official | reasoning, planning, reference |
| Everything | npx -y @modelcontextprotocol/server-everything | Official | testing, reference, debugging |
How to choose
Prefer the official server when one exists, unless its install path or auth model does not fit. Prefer the smaller surface area: a server that exposes four tools you use beats one that exposes forty you do not, because every definition costs context on every request.