MCP server that persists Claude Code memory to a git-tracked file
{
"mcpServers": {
"claude-memory-mcp": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server that persists Claude Code memory to a git-tracked file
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 1 days ago.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
Dynamic problem-solving through sequential thought chains
A Model Context Protocol server for searching and analyzing arXiv papers
The Apify MCP server enables your AI agents to extract data from social media, search engines, maps, e-commerce sites, or any other website using thousands of ready-made scrapers, crawlers, and automation tools available on the Apify Store.
MCP Security Weekly
Get CVE alerts and security updates for Claude Memory Mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP server that gives Claude Code cross-session memory — persisted to a plain .claude-memory.md file inside your repo.
Each project gets its own memory. Commit the file to git and it follows the codebase forever.
# Via uvx (no install needed)
uvx claude-memory-mcp
# Or pip
pip install claude-memory-mcp
Add to your project's .mcp.json (or ~/.claude.json for global):
{
"mcpServers": {
"memory": {
"command": "uvx",
"args": ["claude-memory-mcp"]
}
}
}
| Tool | Description |
|---|---|
memory_read(key) | Read a stored value |
memory_write(key, value) | Write a value |
memory_list() | List all keys |
Memory is stored as ## sections in .claude-memory.md at your repo root:
# Claude Memory
## architecture-decisions
We use SQLite for local dev and Postgres in prod.
Decided 2025-01-15 — migration too risky mid-sprint.
## current-sprint-context
Working on payment webhook handler. Stripe sends events
to /api/webhooks/stripe. See stripe_handler.py:42.
.claude-memory.md — memory persists across machines and teammatesShow HN: I built an MCP server that gives Claude Code a persistent memory file
The problem: every Claude Code session starts fresh. I keep explaining the same architectural decisions, the same "don't touch X" rules, the same "we use Y for Z" conventions.
This MCP server persists memory to
.claude-memory.md— a plain markdown file in your repo. Claude reads and writes it across sessions. Commit it to git and it follows the codebase.Three tools:
memory_read,memory_write,memory_list. That's it.Install: add 8 lines to your
.mcp.json, runuvx claude-memory-mcp.
MIT