neo vs hippo-memory: mcp-servers for Claude compared
data as of 2026-11-21
4.1k
combined stars
312
combined forks
0
ecosystem connections
100%
open-source
// summary
neo has more GitHub stars (3.3k vs 794).
hippo-memory was updated more recently (2 months ago vs 5 months ago).
The right choice depends on your use case — the full spec is below.
neo
★ 3.3kactive
Neo.mjs is a self-evolving software organism: a professional end-to-end AI engineering team whose cross-model swarm inhabits live apps via Neural Link, Activ…
claudeagent-memoryaiai-agentai-memory
view full listing →hippo-memory
★ 794active
Memory for AI agents that learns what is wrong and stops repeating it. Mark a memory wrong and it stops coming back; newer facts replace old ones. Local SQLi…
claudeagent-memoryai-agentsai-memoryclaude-code
view full listing →// head to head
| spec | neo | hippo-memory |
|---|---|---|
| GitHub stars | 3.3k | 794 |
| Forks | 265 | 47 |
| Rating | — | — |
| Upvotes | 0 | 0 |
| Health | active | active |
| Last updated | 5 months ago | 2 months ago |
| Language | JavaScript | TypeScript |
| License | MIT | MIT |
| Pricing | open-source | open-source |
| Platforms | cli, api, desktop, web | cli, api, desktop, web, mobile |
| AI compatibility | claude | claude |
| Verified | no | no |
| Ecosystem connections | 0 | 0 |
// related comparisons
More: all mcp-servers for Claude compared · the mcp-servers for Claude category
Own neo or hippo-memory?
Claim your listing to keep its page accurate and earn CC.