AgentMemory Offline
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., "@AgentMemory Offlinesave the current conversation context for this project"
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.
AgentMemory Offline
Persistent, project-aware memory for local coding agents, derived from rohitg00/agentmemory.
This fork keeps memory on the machine and runs its memory services without outbound network access. It preserves the useful parts of AgentMemory—session capture, recall, summaries, semantic structure, MCP tools, hooks, and a local viewer—while disabling cloud model providers, telemetry, runtime downloads, and update checks.
What “offline” means
The runtime is designed so that memory content is never sent to a remote service:
no cloud LLM provider is selected;
no provider API key is required;
no telemetry or update check is enabled;
MCP points to the locally installed executable, never to
npx;on macOS, the bundled engine is launched through
sandbox-execwith non-loopback outbound traffic denied;local retrieval falls back to lexical/BM25 and the local graph.
Building or installing dependencies may still require access to npm and GitHub. That is outside the runtime guarantee. Linux and Windows do not currently get the macOS process-level network sandbox; use an OS firewall or container network policy there if you need an independently enforced boundary.
See docs/OFFLINE_SECURITY.md for the threat model, ports, limitations, and verification procedure.
Related MCP server: UseCortex MCP Server
Where memory is stored
The database and engine state live outside project repositories by default:
Platform | Default location |
macOS |
|
Linux |
|
Windows |
|
Override the location with --data-dir <path> or
AGENTMEMORY_DATA_DIR=<path>. Memory records carry project/session context, so
multiple sessions for the same project can contribute to the same project
memory without mixing their session history.
Architecture
Local agent
├─ lifecycle hooks ───────────────┐
└─ MCP tools ────────────────┐ │
v v
AgentMemory REST service :3111
├─ local retrieval
├─ local graph/index
├─ session observations
└─ local viewer :3113
│
v
local iii engineThe default interfaces are local HTTP/MCP surfaces. Set
AGENTMEMORY_SECRET to require bearer authentication even on localhost.
Build and run
Requirements: Node.js 20 or newer and the pinned iii engine version shown in
src/version.ts.
npm install
npm run build
npm link
agentmemory --data-dir "$HOME/.local/share/agentmemory"The application will not download the engine at runtime in offline mode. Install the pinned engine ahead of time while online, or place the compatible binary in the private AgentMemory bin directory.
For MCP-only clients:
{
"mcpServers": {
"agentmemory": {
"command": "agentmemory",
"args": ["mcp"],
"env": {
"AGENTMEMORY_URL": "http://127.0.0.1:3111"
}
}
}
}Host integration
The repository includes portable skills and lifecycle hooks. Installation must
merge these declarations with the host's existing configuration; it must not
replace unrelated hooks or skills. The MCP manifest calls the locally installed
agentmemory executable.
Current limitations
Runtime network enforcement is strongest on macOS.
The iii engine may create an internal listener on port
49134. The macOS sandbox rejects non-loopback inbound traffic, but users on other systems must bind or firewall that port themselves.Optional vector embeddings are not part of the guaranteed offline profile. BM25 and graph retrieval remain available.
Mesh/peer synchronization is outside the offline profile and must remain disabled.
Verification
npm test
npm run build
rg -n "OPENAI_API_KEY|ANTHROPIC_API_KEY|OPENROUTER_API_KEY" .env 2>/dev/null
lsof -nP -iTCP -sTCP:LISTEN | rg "3111|3112|3113|49134"For a stronger test, deny all external traffic at the OS firewall, start the service, create a memory, stop it, start it again, and recall the same memory.
Provenance and license
This is an independent offline adaptation of AgentMemory. The original project and attribution are preserved in docs/UPSTREAM_README.md. Licensed under Apache-2.0; see LICENSE.
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.
Related MCP Servers
- AlicenseBqualityDmaintenanceA local-first MCP server that provides AI agents with safe codebase access through file discovery, hybrid lexical-semantic search, and project introspection. It features durable local memory and semantic indexing while keeping all data and processing entirely on your local machine.Last updated74615MIT
- Alicense-qualityCmaintenanceProvides persistent memory for AI coding agents, enabling them to read and write structured knowledge through MCP-compatible tools.Last updated1MIT
- Alicense-qualityAmaintenanceLocal persistent memory for AI coding tools. Stores project context and conversation recall locally via MCP.Last updated1114MIT
- Alicense-qualityBmaintenanceProvides a persistent, local-first memory for coding agents over MCP, enabling automatic recall and recording of past work, failures, and decisions to reduce repetition and token usage.Last updatedMIT
Related MCP Connectors
User-owned memory for AI agents, Copilot, Claude, IDEs, CLIs, and chat apps over remote MCP.
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
The project brain for AI coding agents — memory, decisions, sprints, knowledge base via 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/rmarquesa/agentmemory-offline'
If you have feedback or need assistance with the MCP directory API, please join our Discord server