Claude Memory Manager MCP Server

by nyxtoolsdev Your server? Claim it

local only

Claude Memory Manager runs on your own machine — the client starts it, so there is no endpoint to ping. 149 installs a week from pypi. Last commit 6 Apr 2026.

Cross-session memory for Claude Code — context capture, semantic search, recall

Installs per day peak 32 · avg 18 · +9% w/w

a month agotoday

149

Installs / week

pypi · claude-memory-manager

Stars

0 open issues

6 Apr 2026

Last commit

from GitHub

MIT

License

Python

Nothing serious here today

Today is the operative word: we check Claude Memory Manager every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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 Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add claude-memory-manager -- uvx claude-memory-manager

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "claude-memory-manager": {
      "command": "uvx",
      "args": [
        "claude-memory-manager"
      ]
    }
  }
}

~/.codex/config.toml

[mcp_servers.claude-memory-manager]
command = "uvx"
args = ["claude-memory-manager"]

.cursor/mcp.json

{
  "mcpServers": {
    "claude-memory-manager": {
      "command": "uvx",
      "args": [
        "claude-memory-manager"
      ]
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "claude-memory-manager": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "claude-memory-manager"
      ]
    }
  }
}

Alternatives to Claude Memory Manager

same job, measured the same way

Recall

by clauderecallhq

Persistent memory for Claude Code. Search, recall, and re-inject context from any session.

317 installs/wk local only

Korg Recall MCP

by new1direction

Cross-vendor semantic memory: recall across Claude Code / Codex / Grok sessions by meaning.

55 installs/wk local only

Longhand

by wynelson94

Local memory for Claude Code. Semantic recall across session history with zero API calls.

408 installs/wk local only

Recall

by clauderecall

Persistent memory for Claude Code and Codex. Search and re-inject context from any session.

local only

Longmem

by marerem

Persistent cross-project memory for Cursor and Claude Code using local semantic search.

38 installs/wk local only

Repomemory

by danielguru

Persistent memory for AI coding agents. Hybrid search, auto-session capture, context routing.

101 installs/wk local only

Remem

by majiayu000

Local-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite.

800 installs/wk local only

ContextStream MCP Server

by contextstreamio

ContextStream MCP server for code context, memory, search, and AI tools.

3 749 installs/wk local only

Claude Memory Manager — questions

Answers built from our own checks of this server.

Why is there no uptime for Claude Memory Manager?

Claude Memory Manager runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the pypi package claude-memory-manager was installed 149 times last week.

How do I connect Claude Memory Manager?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls claude-memory-manager straight from pypi; nothing to host, nothing to sign up for.

How many people use Claude Memory Manager?

The pypi package claude-memory-manager was installed 149 times in the last week. Week over week that is +9%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Claude Memory Manager open source?

Yes — it is published under the MIT licence, written in Python and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.