Memory MCP Server vs Chroma MCP Server
Persistent memory for Claude, at two levels of ambition. The official Memory server implements a simple knowledge-graph store — easy to run, no infrastructure. Chroma's server brings a real vector database with semantic retrieval. Start with Memory for lightweight recall across sessions; reach for Chroma when you need embeddings-based search over a growing corpus.
GitHub data verified 2026-07-30 — objective fields only, no editorial scoring.
| Memory MCP Server Persistent memory and knowledge graph for Claude conversations | Chroma MCP Server Vector database for semantic search and RAG applications | |
|---|---|---|
| GitHub stars | 89,034 | 580 |
| Forks | 11,331 | 118 |
| Open issues | 479 | 29 |
| Last commit | 2026-07-29 | 2025-09-17 |
| Maintenance status | Actively maintained | Actively maintained |
| License | Other | Apache-2.0 |
| Language | TypeScript | Python |
| Install | npx @modelcontextprotocol/server-memory | — |
| Author | Anthropic | Chroma |
| Official listing | Yes | No |
| 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.