About MCP AutoMem
MCP AutoMem connects AI platforms to the AutoMem persistent-memory service for agents that need context across sessions. It combines graph and vector memory operations with setup and configuration tools for multiple platforms.
Key features
- 01Store, recall, update, and delete memories
- 02Enumerate and process memories by tag
- 03Expand multi-hop retrieval through graph relations
- 04Configure installations for multiple clients
- 05Integrate platform-specific rules and session hooks
Use cases
- 01Retain coding preferences and project context across sessions
- 02Connect decisions and related memories to answer complex questions
- 03Configure memory access for Cursor, Claude Code, and other clients
MCP support
It acts as an MCP client connecting AI platforms to the AutoMem service and exposes memory operations to them. An optional remote MCP sidecar supports platforms using Streamable HTTP or SSE.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://{endpoint}/mcpclaude mcp add --transport http verygoodplugins-mcp-automem https://{endpoint}/mcp{"mcpServers":{"verygoodplugins-mcp-automem":{"type":"http","url":"https://{endpoint}/mcp"}}}Open in Cursor{"servers":{"verygoodplugins-mcp-automem":{"type":"http","url":"https://{endpoint}/mcp"}}}Open in VS Code{"mcpServers":{"verygoodplugins-mcp-automem":{"type":"http","url":"https://{endpoint}/mcp"}}}{"mcpServers":{"verygoodplugins-mcp-automem":{"serverUrl":"https://{endpoint}/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://{endpoint}/mcpAuth requiredhttps://{endpoint}/mcp/sseAuth requiredTools
Details
From the project READMEAutoMem MCP: Give Your AI Perfect Memory
One command. Infinite memory. Perfect recall across all your AI tools.
npx @verygoodplugins/mcp-automem install
Your AI assistant now remembers everything. Forever. Across every conversation.
The guided installer — npx @verygoodplugins/mcp-automem install walks you through local, hosted, or existing-endpoint setup.
Works with Claude Desktop, Cursor IDE, Claude Code, GitHub Copilot (coding agent), ChatGPT, ElevenLabs, OpenAI Codex, OpenClaw, Hermes, Grok Build, Google Antigravity - any MCP-compatible AI platform.
The Problem We Solve
Every AI conversation starts from zero. Claude forgets your coding style. Cursor can't learn your patterns. Your assistant doesn't remember yesterday's decisions.
Until now.
AutoMem MCP connects your AI to persistent memory powered by AutoMem - a graph-vector memory service.
What You Get
🧠 Persistent Memory Across Sessions
- AI remembers decisions, patterns, and context forever
- Works across all MCP platforms - Claude Desktop, Cursor, Claude Code, OpenAI Codex, OpenClaw, Hermes, Grok Build, Google Antigravity
- Cross-device sync - same memory on Mac, Windows, Linux
🏆 Graph-Vector Architecture
- 11 public authorable relationship types between memories (recall results may also include read-only system/internal relations that are not valid
associate_memoriesinputs) - Research-validated approach (HippoRAG 2: 7% better associative memory)
- Sub-second retrieval even with millions of memories
🚀 Works Everywhere You Code
| Platform | Support | Setup Time |
|---|---|---|
| Claude Desktop | ✅ Full | 30 seconds |
| Cursor IDE | ✅ Full | 30 seconds |
| Claude Code | ✅ Full | 30 seconds |
| GitHub Copilot | ✅ Full | 2 minutes |
| OpenAI Codex | ✅ Full | 30 seconds |
| OpenClaw | ✅ Full | 30 seconds |
| Hermes Agent | ✅ Full | 30 seconds |
| Grok Build | ✅ Full | 30 seconds |
| Google Antigravity | ✅ Full | 30 seconds |
| Any MCP client | ✅ Full | 30 seconds |
See It In Action
Claude Desktop with Personal Preferences
Claude automatically recalls memories using the Personal Preferences template
Cursor IDE with Memory Rules
Cursor uses AutoMem project rules to recall context and save durable memories during work
Claude Code with Session Memory
Session-start recall plus LLM-judged storage: Claude decides what's durable and stores it via the memory tools
More platform walkthroughs (Codex, Hermes, Antigravity, remote MCP) live in the Installation Guide.
Quick Start
1. Set Up AutoMem Service
You need a running AutoMem service (the memory backend). Choose one:
Option A: Local Development (fastest, free)
git clone https://github.com/verygoodplugins/automem.git
cd automem
make dev
Service runs at http://localhost:8001 - perfect for single-machine use.
Option B: Railway Cloud (recommended for production)
One-click deploy with $5 free credits. Typical cost: ~$0.50-1/month after trial.
👉 AutoMem Service Installation Guide - Complete setup instructions for local, Railway, Docker, and production deployments.
2. Install MCP Client
Claude Desktop - One-Click Install
Download the extension, then open Settings → Extensions → Advanced settings → Install Extension in Claude Desktop and select the file:
⬇️ Download AutoMem for Claude Desktop (.mcpb)
After installing:
- Claude Desktop will prompt you for your AutoMem API URL (
http://127.0.0.1:8001for local) - Optionally enter your API Key (required for Railway, skip for local)
- Click Enable
The bundle includes a fixed version of the MCP server. To update, download and install the latest .mcpb again; restarting Claude or updating the npm package does not upgrade an installed bundle. See updating Claude Desktop for version checks and migration from JSON configuration. The AutoMem backend runs separately.
Then add the paste-ready Personal Preferences starter from templates/CLAUDE_DESKTOP_INSTRUCTIONS.md. That's it: Claude now has persistent memory and knows when to use it.
Other Platforms
Connect your AI tools to the AutoMem service you just started.
# Guided install - pick where AutoMem runs, verify it, write .env, and
# configure your agents (Codex, Claude Code, Cursor, OpenClaw, Hermes)
npx @verygoodplugins/mcp-automem install
Every change is shown in a review plan before anything is written, and each
modified file keeps a .bak backup. Add --dry-run to preview, --yes to
apply non-interactively. See the Installation Guide
for all flags.
setup is an alias of install. To print config snippets again later, use npx @verygoodplugins/mcp-automem config.
3. Platform-Specific Setup
For Claude Code (plugin — recommended):
# In Claude Code:
/plugin marketplace add verygoodplugins/mcp-automem
/plugin install automem@verygoodplugins-mcp-automem
Claude Code prompts for your AutoMem URL and API key at enable time, bundles the MCP server and silent recall/store-tracking hooks, and auto-updates. Prefer hooks and permissions written directly into ~/.claude/ instead? Run npx @verygoodplugins/mcp-automem claude-code.
On Windows, the hook payload assumes a POSIX shell environment such as Git Bash, MSYS2, or WSL — only bash is required (the hooks are pure bash+sed).
For Cursor IDE:
Run the guided installer from your project and select Cursor:
npx @verygoodplugins/mcp-automem install
This connects Cursor to your AutoMem service, installs project memory rules, and registers a session-start recall hook. Already have an endpoint? Use npx @verygoodplugins/mcp-automem cursor --endpoint https://your-automem.example.
The one-click button configures only the MCP server for a local AutoMem instance. Update its endpoint/key in Cursor if needed, then run the CLI above to add project rules and the hook:
Other platforms — Claude Desktop (one-click .mcpb above, plus the Personal Preferences template), OpenAI Codex, Hermes Agent, Grok Build, OpenClaw, Google Antigravity, and GitHub Copilot:
👉 Full Installation Guide for every platform's setup and verification steps
Remote MCP via HTTP
An optional sidecar service (deployable to Railway or any Docker host) connects AutoMem to platforms that support remote MCP over Streamable HTTP or SSE — ChatGPT (Developer Mode connectors), Claude.ai web and Claude Mobile, and ElevenLabs Agents.
👉 Remote MCP setup for deployment, connect URLs, and per-platform screenshots.
Architecture
┌─────────────────────────────────────────────┐
│ Your AI Platforms │
│ Claude Desktop │ Cursor │ Claude Code │
└──────────────┬──────────────────────────────┘
│ MCP Protocol
▼
┌──────────────────────────────────────────────┐
│ @verygoodplugins/mcp-automem (this repo) │
│ • Translates MCP calls → AutoMem API │
│ • Platform integrations & rules │
│ • Handles authentication │
└──────────────┬───────────────────────────────┘
│ HTTP API
▼
┌──────────────────────────────────────────────┐
│ AutoMem Service (separate repo) │
│ github.com/verygoodplugins/automem │
│ ┌────────────┐ ┌────────────┐ │
│ │ FalkorDB │ │ Qdrant │ │
│ │ (Graph) │ │ (Vectors) │ │
│ └────────────┘ └────────────┘ │
└──────────────────────────────────────────────┘
This repo (mcp-automem):
- MCP client that connects AI platforms to AutoMem
- Platform-specific integrations (Cursor rules, Claude Code hooks, etc.)
- Setup wizards and configuration tools
- Backend memory service with graph + vector storage
- Deployment guides (local, Railway, Docker, production)
- API server with FalkorDB + Qdrant
Features
Core Memory Operations
store_memory— Save memories with content, tags, importance, metadata. Two modes:- Single (default): top-level
contentplus optional fields, includingembedding,t_valid,t_invalid, customid. - Batch:
memories: [...](≤500 items) for bulk ingestion. Per-itemid/embedding/t_valid/t_invalidare not supported in batch mode.
- Single (default): top-level
recall_memory— Three modes selected by which params you pass:- ID fetch:
memory_id→ fetches one memory by ID; updateslast_accessed. - Tag enumeration:
tags+exhaustive: true→ paginated exact-match listing for cleanup/audit workflows where ranked recall undercounts. Pair withlimit(≤200) andoffset; returnshas_more, plusnext_offsetfor the next page while more remain. - Ranked retrieval (default): hybrid search across vector, keyword, tags, recency/state controls, score filters, and graph expansion. Supports
state_mode,recency_bias,scope_fallback,expand_respect_tags,min_score,adaptive_floor, and diagnostics such astag_scope,score_filter,query_time_ms,vector_search, and per-resultoutside_tag_scope/state_replaces.
- ID fetch:
associate_memories— Create relationships (11 public authorable types; recall results may also include read-only system relations). Supports single-pair mode and batch mode viaassociations: [...](≤500) with relation-specific props likereason,context,resolution,observations,transformation, androle.update_memory— Modify existing memoriesdelete_memory— Two modes:- Single (default):
memory_id→ removes one memory and its embedding. - Bulk-by-tag:
tags: [...]→ bulk-delete all memories matching ANY tag (exact, case-insensitive). No dry-run; verify withrecall_memory({ tags, exhaustive: true })first.
- Single (default):
check_database_health— Monitor service health, degraded state, sync counts, vector dimensions, and enrichment diagnostics when the service provides them
Advanced Recall (v0.8.0+)
Multi-hop Reasoning - Answer complex questions like "What is Amanda's sister's career?"
mcp__memory__recall_memory({
query: "What is Amanda's sister's career?",
expand_entities: true, // Finds "Amanda's sister is Rachel" → memories about Rachel
});
Context-Aware Coding - Recall prioritizes language and style preferences
mcp__memory__recall_memory({
query: "error handling patterns",
language: "typescript",
context_types: ["Style", "Pattern"],
});
Platform Integrations
Cursor IDE
- ✅ Guided setup configures the global MCP server with your endpoint and API key
- ✅ Project memory rules in
.cursor/rules/automem.mdc - ✅ Session-start hook prompts recall, with rules as a fallback
- ✅ Model-judged storage during work; hooks never write memories
- ✅ Auto-detects project context (package.json, git remote)
Claude Code
- ✅ Native plugin - MCP server, silent hooks, and skill in one
/plugin install, with enable-time config prompts and auto-updates - ✅ LLM-judged storage - session-start guidance nudges Claude to store, verify, and associate durable memories during normal work
- ✅ Memory rules in CLAUDE.md guide Claude's memory usage
GitHub Copilot
- ✅ Standalone hook JSON files installed into
$COPILOT_HOME/hooks/or~/.copilot/hooks/ - ✅ Memory rules template for
copilot-instructions.md - ✅ Format flag -
--format cli(camelCase) or--format vscode(PascalCase) - ✅ Setup:
npx @verygoodplugins/mcp-automem copilot --yes
Claude Desktop
- ✅ Direct MCP integration
- ✅ Paste-ready Personal Preferences starter template
- ✅ Full memory API access
Why AutoMem MCP?
vs. Building Your Own
- ✅ 2 years of R&D already done
- ✅ Research-validated architecture (HippoRAG 2, MELODI, A-MEM)
- ✅ Working integrations across all MCP platforms
- ✅ Active development and community
vs. Other Memory Solutions
- ✅ True graph relationships (not just vector similarity)
- ✅ Universal MCP compatibility (works with any MCP client)
- ✅ 7 memory types (Decision/Pattern/Preference/Style/Habit/Insight/Context)
- ✅ Self-hostable ($5/month vs $150+ for alternatives)
vs. Native AI Memory
- ✅ Persistent across sessions (not just context window)
- ✅ Cross-platform (same memory in Claude, Cursor, Code)
- ✅ Structured relationships (not just RAG)
- ✅ Infinite scale (no context window limits)
Documentation
MCP Client & Integrations (this repo)
- 📦 Installation Guide - MCP client setup for all platforms
- 🌐 Remote MCP via HTTP - Connect ChatGPT, Claude Web/Mobile, ElevenLabs
- 🎯 Cursor Setup - IDE integration with rules and a session-start hook
- 🤖 Claude Code Setup - Plugin install, hooks, and memory rules
- ⚠️ Deprecations - History of the plugin deprecation and its reversal
- 🚀 OpenAI Codex Setup - Codex CLI/IDE/Cloud integration
- 🪐 Google Antigravity Setup - Raw MCP config via Antigravity's MCP Store
- 📖 MCP Tools Reference - All memory operations
- 📝 Changelog - Release history
AutoMem Service (separate repo)
- 🏗️ AutoMem Service - Backend repository
- 🚀 Service Installation - Local, Railway, Docker deployment
- ⚙️ API Documentation - REST API reference
- 🧪 Evaluation Lab - Exploratory recall-quality benchmarks and ruleset A/B testing
The Science Behind AutoMem
The AutoMem service implements cutting-edge 2025 research:
- HippoRAG 2 (OSU, June 2025): Graph-vector approach achieves 7% better associative memory
- A-MEM (July 2025): Dynamic memory organization with Zettelkasten principles
- MELODI (DeepMind, 2025): 8x memory compression without quality loss
- ReadAgent (DeepMind, 2024): 20x context extension through gist memories
This MCP package provides the bridge between your AI and that research-validated memory system. The backend has also been benchmarked on the neutral Agent Memory Benchmark, including BEAM large-context scaling tiers — reproducible end to end, so you can run it yourself.
Community & Support
- 💬 Discord - Join the community, get help, share feedback
- 🐦 X Community - Discussion and updates
- 📣 @automem_ai - Official announcements
- 📦 NPM Package - This MCP client
- 🔬 AutoMem Service - Backend repo with deployment guides
- 🐛 GitHub Issues - Bug reports and feature requests
Contributing
We welcome contributions! Please:
- Fork the repository
- Create a feature branch
- Make your changes with tests
- Submit a pull request with a Conventional Commit title such as
fix:,feat:,docs:, orchore: - Do not prefix the PR title with labels like
[codex]or[wip]because the squash-merge commit is taken from the PR title
License
MIT - Because great memory should be free.
Ready to give your AI perfect memory?
npx @verygoodplugins/mcp-automem install
Built with obsession. Validated by neuroscience. Powered by graph theory. Works with every MCP-enabled AI.
Designed by Jack Arturo at Very Good Plugins 🧡
Transform your AI from a tool into a teammate. Start now.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.