claude-memory-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@claude-memory-mcpremember that we are using SQLite for local dev"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
claude-memory-mcp
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.
Install
# Via uvx (no install needed)
uvx claude-memory-mcp
# Or pip
pip install claude-memory-mcpRelated MCP server: MCP Memory Server
Configure Claude Code
Add to your project's .mcp.json (or ~/.claude.json for global):
{
"mcpServers": {
"memory": {
"command": "uvx",
"args": ["claude-memory-mcp"]
}
}
}Tools
Tool | Description |
| Read a stored value |
| Write a value |
| List all keys |
How it works
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.Project-scoped: different repos = different memory files
Git-tracked: commit
.claude-memory.md— memory persists across machines and teammatesHuman-readable: open the file, edit it, diff it like any other source file
No auth, no cloud, no database: just a file
Use cases
Remember architectural decisions across sessions
Store "where I left off" context so Claude doesn't ask again
Share team conventions without repeating them in every prompt
Track ongoing debugging context across long refactors
Show HN post
Show 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.
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/santicalderon/claude-memory-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server