SuperLocalMemory vs SuperLocalMemory: MCP server comparison
Superlocalmemory and SuperLocalMemory side by side: tools, transport, auth, license and activity, measured from GitHub, npm and PyPI.
vs
Which one to pick
On the data we measure the two are close. Compare the tools each one exposes and pick the one that covers your task.
Built only from the numbers below. It changes when they do.
Side by side
| Feature | Superlocalmemory | SuperLocalMemory |
|---|---|---|
| Publisher | Community | Community |
| Automated checks | 100/100 · Verified | 100/100 · Verified |
| Transport | stdio | stdio |
| Auth | none | none |
| Tools | 5 | 5 |
| Settings (env vars) | 0 | 0 |
| Language | Python | Python |
| License | AGPL-3.0 | AGPL-3.0 |
| GitHub stars | 276 | 275 |
| Downloads, 30 days | — | — |
| Latest version | 2.7.5 | 4.2.19 |
| Last commit | Nov 14, 2026 | Nov 13, 2026 |
| Install | npx -y superlocalmemory | uvx superlocalmemory |
Tools compared
Read from the README, may include argument namesOnly in Superlocalmemory 0
—
In both 5
corecodemeshpowerwhole
Only in SuperLocalMemory 0
—
Superlocalmemory vs SuperLocalMemory questions
Is Superlocalmemory or SuperLocalMemory better?
On the data we measure the two are close. Compare the tools each one exposes and pick the one that covers your task.
Can I use Superlocalmemory and SuperLocalMemory together?
Yes. MCP clients load several servers at once; add both to the same config and give each its own name.