Remem runs on your own machine — the client starts it, so there is no endpoint to ping. 800 installs a week from npm. Last commit 14 Oct 2026.
Local-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite.
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
postinstall: node scripts/install.js
const result = spawnSync(bin, process.argv.slice(2), {
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
content: fs.readFileSync(path.join(__dirname, "public", asset.file), "utf8"),
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add remem -- npx -y @remem-ai/remem
{
"mcpServers": {
"remem": {
"command": "npx",
"args": [
"-y",
"@remem-ai/remem"
]
}
}
}
[mcp_servers.remem]
command = "npx"
args = ["-y", "@remem-ai/remem"]
{
"mcpServers": {
"remem": {
"command": "npx",
"args": [
"-y",
"@remem-ai/remem"
]
}
}
}
{
"servers": {
"remem": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@remem-ai/remem"
]
}
}
}
Local-first persistent session memory for Claude Code and other agents. SQLite + FTS5, no cloud.
Cross-session memory for Claude Code — context capture, semantic search, recall
Read and write Claude Code auto memory from Codex, Cursor or any MCP client. Zero dependencies.
Persistent memory for Claude Code. Search, recall, and re-inject context from any session.
Local memory for Claude Code. Semantic recall across session history with zero API calls.
Persistent memory MCP server for Claude Code, Codex and OpenCode, stored locally in SQLite
Automatic project memory for Claude Code and Cursor; Codex and Claude Desktop over MCP.
Local-first AI memory: search your Claude Code, Codex, Claude desktop, Pieces and browser history.
Answers built from our own checks of this server.