Memory and knowledge · MCP server
Context memory: MCP server, setup and security
Context memory is an open-source MCP server published on GitHub that lets an AI agent retrieve Claude Code session context summaries and recover from saved checkpoints. Its repository has 7 stars and its last commit is from February 17, 2026 and it is licensed under MIT.
What Context memory does
According to its repository: “Persistent, searchable context storage across Claude Code sessions using SQLite FTS5, with AI session summaries, checkpoint recovery and a web dashboard.”
The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. Context memory is listed under Memory and knowledge, a category of 250 servers in the directory, where it ranks #212 by stars.
Topics declared by the repository: claude-code, claude-code-plugin, context, full-text-search, memory, plugin.
Installing and connecting Context memory
No package or remote server is declared in the official MCP registry: you install it from source, following the repository README.
It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: Python. Listed systems: macOS, Windows, Linux.
Security: what to check
Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.
None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Context memory. That does not replace reading the code.
Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.
Project activity and maintenance
Created on February 12, 2026, the ErebusEnigma/context-memory repository has 7 stars and 2 forks, with 0 open issues. It has more stars than 19% of the servers in the directory. Last change 8 months ago.
Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.
Verdict
Context memory is still a modest project: read its code and compare it with the alternatives before using it.
Strengths
- Permissive licence (MIT)
Limitations
- No commit for 8 months
- Few visible users
- Install from source
Alternatives
- Context763.6K ★
- Basic memory4.3K ★
- Hindsight53.4K ★
- Cognee32.7K ★
- Skill Seekers15.2K ★
- Honcho7.8K ★
Learn more
Frequently asked questions
How do I install Context memory?
No package is declared in the MCP registry: clone the ErebusEnigma/context-memory repository, follow its README, then declare the start command in your client's MCP configuration.
Is Context memory free?
The code is published under the MIT licence and can be used free of charge.
Is Context memory safe?
No risk signal found (system access, secrets, licence, abandonment). As with any MCP server, keep rights minimal and read the code before sensitive use.
Is it an official server?
Nothing says so: it is a project published by ErebusEnigma on GitHub. Check who maintains it before giving it access.
What are the alternatives to Context memory?
In the same category: Context7, Basic memory, Hindsight, and Cognee. Context7 and Basic memory score higher on our grid.
Related articles
- Build your own MCP server in 30 minutesOctober 24, 2026
- Automate your inbox with an AI agentOctober 18, 2026
- MCP, A2A, and tool calling: agent protocols explainedOctober 17, 2026
- Build an AI agent with n8n, without codingOctober 16, 2026
Neutrality. No affiliate links. No vendor pays to be reviewed, rated or ranked. Reviews are directed by François Chollet, neutral and factual, and every data point is dated and sourced. How we score