mcp-automem
The AutoMem MCP server provides persistent, cross-session memory for AI assistants using a graph-vector hybrid backend (FalkorDB + Qdrant), enabling storage, retrieval, and management of memories across conversations and platforms.
Store Memories: Save individual memories or batch-ingest up to 500 at once. Supports 7 memory types (Decision, Pattern, Preference, Style, Habit, Insight, Context), tags, importance scores (0ā1), metadata, confidence, custom IDs, time-bounded validity, custom embeddings, and supersede/correct modes that automatically link old and new memories via
INVALIDATED_BYorEVOLVED_INTOrelationships.Recall Memories: Retrieve memories in three modes:
ID fetch: Retrieve a single memory by ID
Tag enumeration: Paginated exact-match listing by tag (up to 200/page) for audits or cleanup
Ranked retrieval: Hybrid semantic + keyword + tag + recency search with graph expansion, multi-hop reasoning (
expand_entities), language hints, score filtering, and state filtering (current vs. historical)
Associate Memories: Build a knowledge graph with 11 typed relationship types (RELATES_TO, LEADS_TO, OCCURRED_BEFORE, PREFERS_OVER, EXEMPLIFIES, CONTRADICTS, REINFORCES, INVALIDATED_BY, EVOLVED_INTO, DERIVED_FROM, PART_OF). Supports single-pair or batch mode (up to 500 associations) with customizable strength, reason, and context.
Update Memories: Modify content, tags, importance, type, confidence, metadata, or timestamps of existing memories without creating duplicates.
Delete Memories: Remove a single memory by ID, or bulk-delete all memories matching any of a given list of tags (irreversible).
Check Database Health: Monitor the AutoMem service, FalkorDB graph, and Qdrant vector databases, including memory/vector counts, sync status, vector dimensions, and enrichment diagnostics.
Connects to ElevenLabs Agents Platform via remote MCP, giving AI agents memory persistence and recall capabilities.
Integrates with GitHub Copilot to offer persistent memory, allowing the coding agent to recall user patterns and decisions across sessions.
Works with OpenAI Codex and ChatGPT (through remote MCP) to provide persistent memory, enabling the AI to remember context and user preferences across conversations.
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., "@mcp-automemremember my preference for dark mode in code editors"
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.
AutoMem MCP: Give Your AI Perfect Memory
One command. Infinite memory. Perfect recall across all your AI tools.
npx @verygoodplugins/mcp-automem setupYour AI assistant now remembers everything. Forever. Across every conversation.
https://github.com/user-attachments/assets/fd79112b-5158-4320-a054-8c18ab1ea314
Works with Claude Desktop, Cursor IDE, Claude Code, GitHub Copilot (coding agent), ChatGPT, ElevenLabs, OpenAI Codex, OpenClaw, Hermes, 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.
Related MCP server: my-memory-mcp
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, 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 |
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.mdc rule to automatically recall and store memories
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 devService 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 and double-click to install AutoMem in Claude Desktop:
ā¬ļø Download AutoMem for Claude Desktop (.mcpb)
After installing:
Claude Desktop will prompt you for your AutoMem Endpoint (
http://127.0.0.1:8001for local)Optionally enter your API Key (required for Railway, skip for local)
Click Enable
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 installEvery 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.
Just need the .env + config snippets without the agent setup? Use the lighter wizard:
# Creates .env and prints config for your AI platform
npx @verygoodplugins/mcp-automem setupWhen prompted:
AutoMem Endpoint:
http://localhost:8001(or your Railway URL if deployed)API Key: Leave blank for local development (or paste your token for Railway)
The wizard will:
ā Save your endpoint and API key to
.envā Generate config snippets for Claude Desktop/Cursor/Code
ā Validate connection to your AutoMem service
3. Platform-Specific Setup
For Claude Code (plugin ā recommended):
# In Claude Code:
/plugin marketplace add verygoodplugins/mcp-automem
/plugin install automem@verygoodplugins-mcp-automemClaude 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:
# Or use CLI to install automem.mdc rule file
npx @verygoodplugins/mcp-automem cursorOther platforms ā Claude Desktop (one-click .mcpb above, plus the Personal Preferences template), OpenAI Codex, Hermes Agent, 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.
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.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.
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.
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
ā Memory-first rule file (
automem.mdcin.cursor/rules/)ā Automatic memory recall at conversation start
ā Auto-detects project context (package.json, git remote)
ā Global user rules option for all projects
ā Simple setup via CLI or one-click install
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
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
š¤ 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 setupBuilt 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.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityBmaintenanceA personal AI memory hub that stores and retrieves personal data from any MCP-enabled AI assistant, enabling persistent memory across conversations.Last updated4MIT
- Flicense-qualityDmaintenanceA MCP server that provides persistent memory for AI assistants, storing personal information, relationships, and observations to enable personalized and contextual conversations.Last updated4
- Alicense-qualityDmaintenanceA persistent, self-organizing memory MCP server for AI assistants, using semantic search, knowledge graphs, and reinforcement learning to automatically manage and retrieve memories.Last updatedMIT
- Alicense-qualityAmaintenanceEnables AI assistants to have a living memory with atomic knowledge storage, multi-factor recall, organic decay, automatic learning, and graph traversal via MCP.Last updated1MIT
Related MCP Connectors
Your memory, everywhere AI goes. Build knowledge once, access it via MCP anywhere.
Persistent memory and knowledge graph for AI assistants ā keyword + vector + graph search.
User-owned memory for AI agents, Copilot, Claude, IDEs, CLIs, and chat apps over remote MCP.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- 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/verygoodplugins/mcp-automem'
If you have feedback or need assistance with the MCP directory API, please join our Discord server