← Discover MCPs and Agents
M
MCPAI & MLMCP Registry

MemCell

Living memory for AI coding agents: recall before acting, report outcomes so confidence is earned.

Links

README

From the repo.

MemCell Logo

memcell

Persistent, adaptive memory engine for AI agents.
Stop your agents from repeating the same mistakes across sessions.

npm version License: Apache-2.0 Node.js >= 20 Documentation

# Install globally
npm install -g memcell

# In any project:
memcell connect

Run it in any project. memcell connect automatically:

  • Approves in 1 tap: Opens browser approval (no upfront account needed; guest memories carry over seamlessly on sign-in).
  • Auto-detects agents: Wires Claude Code, Cursor, Copilot CLI, Gemini CLI, OpenAI Codex, OpenCode, Cline, Windsurf, and more with non-destructive lifecycle hooks and the local stdio MCP server (memcell mcp).
  • Secures credentials: Stores scoped agent keys directly in your OS keyring (Keychain / Secret Service / Credential Manager).
  • Creates .memcell: Adds a clean, git-safe project descriptor to your repo root.

Verify anytime:

memcell status

Why MemCell?

Every time you start a new session with an AI agent, it starts with complete amnesia. It falls into the same traps, repeats outdated assumptions, and recreates issues you already resolved yesterday.

Static instruction files and monolithic system prompts don't solve this:

  • Context Bloat: Stacking dozens of instructions wastes tokens on every turn and dilutes model attention.
  • Zero Adaptability: Outdated instructions keep firing even when requirements change.
  • Manual Overhead: You remain the sole feedback loop, constantly hand-editing markdown files.

MemCell gives your agents closed-loop memory:

  1. Pre-Action Recall — Before taking action, agents receive verified statements relevant to the current task.
  2. Execution & Feedback — When actions succeed or fail, real outcomes are reported back.
  3. Earned Confidence — Statements that work gain confidence; statements that fail decay. Zero manual prompt maintenance.

How It Works

MemCell pairs two lightweight layers so agents stay aligned without getting in your way:

  • Deterministic Hooks (Zero-Touch): Fire automatically on session start, prompt submit, and turn end. Relevant statements and directives are checked before actions begin—without relying on the model remembering to call a tool. Hooks fail open in <50ms, so offline or slow networks never block your editor.
  • MCP Tool Bridge (memcell mcp): Provides interactive tools (recall, remember, report, ingest) when agents need to search memory or record discoveries mid-turn.

Everyday Usage

Once connected, agents recall and report memory automatically. You can also interact with memory directly from your terminal:

1. Recall Verified Context Before Implementing

memcell recall "how do we handle multi-tenant database sessions?"

2. Record a Decision or Convention

# Record a project convention
memcell remember "Always use pnpm for package operations; never invoke npm directly"

# Bind an invariant to a specific lifecycle trigger
memcell remember "Check database migrations for column locks before altering tables" --at "before db:migrate"

3. Report What Happened

Memories sharpen when told what happened. When an approach succeeds or fails, report the outcome:

memcell report stmt_019a4b2c worked --note "CI suite passed cleanly"
memcell report stmt_019a4b2c failed --note "broke Next.js 15 async cookies"

4. Ingest Specs and Existing Guidelines

# Ingest an architecture doc, spec, or post-mortem
memcell ingest docs/architecture/auth.md

# Scan and import existing guideline files (CLAUDE.md, etc.)
memcell import

5. Check Attributed Token Savings

memcell stats

Displays statements followed, errors avoided, estimated tokens saved from prevented error loops, and 30-day activity sparklines.


Supported Agents & IDEs

Agent / HarnessIntegrationHow It Runs
Claude CodeHooks + MCP + PluginAutomatic lifecycle hooks or marketplace plugin (/plugin marketplace add memcell-ai/cli)
CursorHooks + MCP BridgeNative lifecycle hooks in .cursor/hooks.json and stdio bridge in .cursor/mcp.json
Gemini CLIHooks + MCPSession and prompt hooks via native CLI harness
GitHub Copilot CLILifecycle HooksPre-command validation hooks
OpenAI Codex / OpenCodeHooks + MCPProject descriptor hooks and stdio tools
Cline & WindsurfMCP BridgeNative editor MCP client configuration
Factory Droid, Devin, Kiro, GooseHooks + MCPWorkspace adapters and tool harnesses

Command Cheat Sheet

CommandDescription
memcell connectConnect this directory to MemCell, install hooks, and configure MCP
memcell statusCheck authentication standing, active project, and connection health
memcell statsShow statements followed, errors avoided, and token savings
memcell recall <intent>Query memory for verified statements and past outcomes before acting
memcell remember <text>File a project convention or directive (--at for lifecycle triggers)
memcell report <id> <outcome>Report worked, failed, or avoided to update confidence
memcell ingest <file>Distill a document or specification into atomic memories
memcell import [files...]Import existing guideline files (CLAUDE.md, etc.)
memcell exportExport project memories as a portable document (--format json|md)
memcell orgsList or switch active organization (memcell orgs switch <slug>)
memcell projectsList or switch active project (memcell projects use <slug>)
memcell hook removeCleanly remove all MemCell hooks from this directory
memcell resetClear all cached credentials, keys, and tokens on this machine

Run memcell --help or memcell <command> --help for full flag details.


Clean Uninstall

To remove MemCell hooks from a repository without touching your code:

memcell hook remove
rm .memcell

To remove all stored keys and credentials from your local machine:

memcell reset

Links

Apache License 2.0 · © 2026 OpenOri

Config for your environment

Use the endpoint URL below in your config. No API key — you connect directly.

Tool

OS

Config file: ~/.cursor/mcp.json

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://memcell.ai/mcp"
    }
  }
}

Paste into mcpServers in the config file. Restart Cursor after saving.

If this MCP is also published on mcpchannel.ai, you can subscribe from Browse and use the gateway config there instead.