Practical overview
When it fits
Use it when an MCP-compatible assistant needs access to persistent context held by an AutoMem service, including when configuring separate tools to share memory across conversations.
Who it is for
- Developers configuring MCP-compatible assistants such as Claude Desktop, Cursor or Codex to use durable memory.
- Teams or individuals who already operate, or plan to set up, an AutoMem service and want to connect supported AI tools to it.
Documented uses
- Connect an MCP client to a local, hosted or existing AutoMem endpoint.
- Configure supported assistants to store and recall context across sessions.
- Set up a remote MCP sidecar for platforms that connect over Streamable HTTP or SSE.
Requirements & limits
The repository identifies the client as open source under the MIT license. Local AutoMem setup can omit an API key; hosted Railway setup requires one according to the README.
- MCP Automem is the client, while AutoMem is a separate backend that must be running and reachable.
- The README documents local, Railway and existing-endpoint setup paths.
- The installer presents a review plan before writing changes and keeps
.bakcopies of modified files. - A separate HTTP sidecar is documented for remote MCP connections using Streamable HTTP or SSE.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Configure MCP Automem with the guided installer
Connect supported agent configurations to a running AutoMem service.
Before you start
- A running AutoMem service and its endpoint URL.
- An API key if the endpoint requires one, such as the documented Railway setup.
- Node.js package execution through npx.
Steps
Run the command below.
npx @verygoodplugins/mcp-automem installChoose where AutoMem runs and provide the endpoint and any required API key when prompted.
Review the proposed changes before applying them; modified files receive
.bakbackups.
Expected outcome
The installer prepares environment settings and configures supported agents to connect to the AutoMem endpoint.
Guide limitations
- The AutoMem backend must be running separately.
- The documented agent configuration targets Codex, Claude Code, Cursor, OpenClaw and Hermes; platform-specific steps may differ.
Set up the Claude Desktop package
Connect Claude Desktop to a local or hosted AutoMem endpoint.
Before you start
- A running AutoMem service and its endpoint.
- The endpoint's API key if required; the README says local development can omit it.
Steps
Download and open the AutoMem Claude Desktop
.mcpbpackage.Enter the AutoMem endpoint when Claude Desktop prompts for it.
Enter an API key if the endpoint requires one, then enable the integration.
Add the documented Personal Preferences starter template.
Expected outcome
Claude Desktop is configured with the MCP client and the documented starter instructions for using persistent memory.
Guide limitations
- This procedure requires a separately running AutoMem service.
- The API key requirement depends on the endpoint.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- verygoodplugins/mcp-automem · Official homepage title · retained in its source language

