Recallium MCP
Engineering team memory over MCP: decisions, bug causes and constraints recalled by every agent, from Claude Code to Cursor.
- 58 ★ on the repository
- Last commit
Extended access
Why this level
- The cloud version receives saved memory entries and edit metadata, and the installer changes agent settings after confirmation
Install
- Works in
Manual install
npx -y recallium@latest installThe installer finds agents, shows a plan and writes only after confirmation. Node.js 22 or newer is required.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The cloud version receives saved memory entries and edit metadata, and the installer changes agent settings after confirmation
This is third-party code. Review the repository files before installing.
What it does
Recallium keeps what usually gets lost between agent sessions: a decision and the options rejected, a bug cause and its fix, constraints that forced a change, team rules and the state of a task. Each entry is tied to files, a commit and an author. When another session, another agent or a teammate opens the same code, the `recallium` MCP server supplies what was found before work starts. If one decision replaced another, agents follow the current one. The installer finds agents on the machine, shows a plan and writes nothing until confirmed. The cloud version works at once, while the free self-hosted version runs in Docker from the `community/` directory.
Who it is for. Teams where several agents and people work on one repository and the reasons behind past decisions have to be rediscovered.
Good fit when
- A fresh Claude Code session starts work on a module and needs decisions taken in earlier sessions
- A teammate runs Cursor or Codex on the same code and the first agent’s findings must not be lost
- Before changing authorization you want to see which constraints and open tasks are already recorded
- An old decision was replaced by a new one and agents must not return to the outdated one
Not a fit when
- Personalization for the users of your product is needed, since the service remembers developers’ decisions, not customers
- Code and discussions cannot go to an outside service and a Docker deployment is not possible
- One project rules file is enough and memory between sessions is not required
Example request
Which decisions and open tasks should I know before changing the authentication flow? Save the outcome of the change as a decision with its reason.MCP
- Transport
- http
- Authentication
- OAuth
Limitations
The cloud version sends the content of saved entries and edit telemetry to the server: file paths, hashes, counts, and branch and commit data. The client does not transmit the contents of source files. Shared memory per repository is available on the paid Pro plan, nothing is shared on the free Cloud Free plan, and per the README the limit is 500 entries a month until December 2026. The self-hosted version is under the Elastic License v2 and cannot be offered to third parties as a service. The client needs Node.js 22 or newer.
How to disable. Run `npx -y recallium@latest uninstall --all` to remove the connection from all agents and the local state. Data in the cloud is deleted in the account dashboard.
FAQ
Which agents connect?
The installer finds Claude Code, Codex, Cursor, GitHub Copilot, VS Code and Claude Desktop. Other MCP clients connect manually to the same endpoint.
Can it run without the cloud?
Yes. The `community/` version runs in Docker on your machine or network for free and was called MiniMe MCP before the rename.
How do I check that memory works?
`status` shows the client, sign-in and connected agents, and `doctor` checks capture and integrations and gives a repair for each failure.
What happens with several projects?
The project name comes from the Git repository. If a clone name differs from an imported one, map it with `git config --local recallium.projectName`.
Does the service see my code?
Source file contents are not sent. Saved memory entries and edit metadata such as paths and hashes are sent.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server that keeps project decisions in Redis or Valkey and brings them back in new sessions and after compaction.
Long-term memory for Claude Code, Cursor and Codex: the agent saves decisions and finds them again in later sessions
Local agent memory built on a corrections ledger: tell Claude Code once and a new session reads the rule before it starts work
The Memanto memory MCP server: an agent stores facts and decisions and finds them in later sessions, even as of a date.
Local memory for agents: stores conversations and project files verbatim and retrieves them with semantic search over MCP
An MCP server for long-term agent memory: compresses dialogues into atomic facts, resolves pronouns and anchors relative time to absolute dates
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Recallium (this card) | yes | OAuth | 58 | |
| Claude-Mem | no | 116,790 | keeps one user’s notes inside Claude Code; Recallium ties decisions to files and commits and shares them across a team’s agents | |
| Mem0 | no | 68,929 | a memory layer for your product’s end users; Recallium remembers developers’ decisions |
README in short
Memory follows the repository, not the person: sharing depends on who connected the repository. Decisions are superseded by newer ones, and the latest is treated as current.