ctx
★ 1.2k
vs
mcp-memory-service
★ 2.1k
ctx vs mcp-memory-service
ctx: ctx indexes local coding-agent histories for search, transcript retrieval and attribution of committed code to agent sessions. Its CLI also maps code relationships with ctx graph and compacts command output with ctx sift, with local processing as the default.; mcp-memory-service: MCP Memory Service prevents AI assistants from losing context across sessions by automatically capturing project architecture, decisions, and code patterns. This ensures your AI always remembers essential information, eliminating the need for repetitive re-explanation and saving valuable development time.
01
TL;DR
ctxMemory & Context · ★ 1.2k
When to choose:
- You need to recover decisions and failed approaches from existing coding transcripts.
- You can verify source roots, refresh policy, exact readback and import diagnostics.
When to skip:
- You require verified semantic or code-attribution capabilities from this review.
- You expect retrieval to redact everything automatically or always return physical file locations.
mcp-memory-serviceMemory & Context · ★ 2.1k
When to choose:
- You use Claude Code, Claude Desktop, Cursor, VS Code or another MCP client and want chat sessions to stop starting from zero.
- You want a choice of storage: local SQLite, Cloudflare for multi-device sync, or a hybrid.
- You need team features: the README lists OAuth, a dashboard and document ingestion.
When to skip:
- Your problem is codebase navigation rather than conversation memory; a code-graph tool or a project scaffold fits better.
- You handle sensitive material and cannot put it in a persistent store, especially with cloud sync.
- You want a short README to start from: it mixes release notes with documentation.
02
Side-by-Side Comparison
Field
Category
Memory & Context
Memory & Context
Stars
★ 1.2k
★ 2.1k
License
Apache-2.0
Apache-2.0
Install Command
curl -fsSL https://ctx.rs/install | sh
pip install mcp-memory-service
Updated
1w ago
1d ago
Open Source
Yes
Yes
Tags
agent, agent-skills, agentic
AI Memory, Context Management, Developer Tools
03
Features
01Searches local sessions with BM25 and optional local semantic search.
02Links committed code to recorded sessions and tool calls when evidence is available.
03Indexes code relationships in SQLite for graph queries and incremental updates.
04Compacts noisy command output and optionally retains originals for recall.
01Persistent Memory
02Smart Retrieval
03Multi-Client Compatibility
04Cloud Sync (Optional)
05Web Dashboard
04
Use Cases
↳Recover decisions and failed approaches from earlier coding-agent sessions.
↳Investigate a code change by opening the agent transcript associated with its commit.
↳Inspect callers and dependencies while reducing repetitive tool output.
↳Maintaining AI context across multiple development sessions.
↳Avoiding repetitive explanations of project architecture and tech stack to AI.
↳Enhancing continuous and intelligent collaboration with AI assistants.
05
Best For
—
EssentialTrending
FAQ
FAQ
What is the difference between ctx and mcp-memory-service?
Both ctx and mcp-memory-service are in the Memory & Context category. ctx has 1.2k stars, while mcp-memory-service has 2.1k stars.
Which is better, ctx or mcp-memory-service?
The best choice depends on your use case. Choose ctx if Recover decisions and failed approaches from earlier coding-agent sessions., and mcp-memory-service if Maintaining AI context across multiple development sessions..
Is ctx free or open source?
Yes, ctx is open source on GitHub (Apache-2.0).
Is mcp-memory-service free or open source?
Yes, mcp-memory-service is open source on GitHub (Apache-2.0).
Cloud Infrastructure
AdDeploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.
→