This MCP server provides a Zettelkasten-based memory system for Claude, allowing persistent context awareness across multiple coding sessions. It creates a "living" memory system that evolves as new information is added, automatically discovering relationships between memories.
The easiest way to get started is with the one-command installation:
git clone [email protected]:nixlim/amem_mcp.git
cd amem_mcp
./scripts/install.sh
This installer will:
If you prefer to install manually:
cp .env.example .env
docker-compose up -d && make build
After installation, verify that A-MEM is working correctly:
# Check services
docker-compose ps
# Validate installation
./scripts/validate_installation.sh
You can also verify in Claude by asking: "What tools do you have available?" - you should see memory-related tools in the response.
The server provides three main MCP tools that Claude can use:
Stores code snippets with AI-generated analysis:
{
"tool": "store_coding_memory",
"arguments": {
"content": "function fibonacci(n) { return n <= 1 ? n : fibonacci(n-1) + fibonacci(n-2); }",
"project_path": "/projects/algorithms",
"code_type": "javascript",
"context": "Recursive implementation of Fibonacci sequence"
}
}
Search for relevant memories using vector similarity:
{
"tool": "retrieve_relevant_memories",
"arguments": {
"query": "How to implement fibonacci efficiently?",
"max_results": 5,
"min_relevance": 0.7
}
}
Triggers memory network evolution to update connections and relationships:
{
"tool": "evolve_memory_network",
"arguments": {
"trigger_type": "manual",
"scope": "recent",
"max_memories": 100
}
}
The server supports workspace management with these additional tools:
Configuration is managed through YAML files and environment variables:
config/development.yaml
- Development settingsconfig/production.yaml
- Production settings.env
- Environment variables (API keys, overrides)ChromaDB connection failed:
docker-compose ps chromadb
chromadb.url
LLM API errors:
.env
fileMemory storage errors:
docker-compose logs chromadb
# Docker deployment
docker-compose logs amem-server
# Direct execution
./amem-server -log-level debug
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "amem" '{"command":"docker-compose","args":["up","-d"]}'
See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"amem": {
"command": "docker-compose",
"args": [
"up",
"-d"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
2. Add this to your configuration file:
{
"mcpServers": {
"amem": {
"command": "docker-compose",
"args": [
"up",
"-d"
]
}
}
}
3. Restart Claude Desktop for the changes to take effect