Engrm MCP Server

Shared memory across devices, sessions, and agents for OpenClaw, Claude Code, and Codex.

Remote serverstreamable-httpPython

What is the Engrm MCP server?

Shared memory across devices, sessions, and agents for OpenClaw, Claude Code, and Codex. Exposed over MCP by the engrm mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Cross-device persistent memory for OpenClaw, Claude Code, Codex, and any MCP-compatible agent. Start free with 2 devices.

  • Cross-device sync — — Fix a bug on your laptop, continue on your desktop. No other memory tool does this
  • Cross-agent compatible — — Works with OpenClaw, Claude Code, Codex, Cursor, Windsurf, Cline, Zed
  • Free tier — — 2 devices, 5,000 observations, full sync. £0 forever
  • Offline-first — — Local SQLite + sqlite-vec. <50ms search. Works on a plane
  • Delivery Review — — Compare what was promised vs what shipped
  • Sentinel — — Real-time code audit before changes land

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

  • Feature — Engrm Free
  • Cost — £0
  • Cross-device — ✅ 2 devices
  • Sentinel — ✅ (Vibe+)
  • search — Find relevant observations from memory (hybrid FTS5 + vector)
  • timeline — Chronological context around an observation
  • get_observations — Fetch full details by ID
  • save_observation — Manually save something worth remembering
  • install_pack — Load a curated knowledge pack for your stack
  • send_message — Leave a cross-device or team note
  • recent_activity — Inspect what Engrm captured most recently
  • memory_stats — View high-level capture and sync health

Caveats

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 13 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Engrm.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the engrm mcp server does with a few real requests.

When to reach for it

This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Engrm's toolset — Feature, Cost, Cross-device and 10 more — is a fair guide to whether it matches your workflow. It is maintained by dr12hes; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
FeatureEngrm Free
Cost£0
Cross-device✅ 2 devices
Sentinel✅ (Vibe+)
searchFind relevant observations from memory (hybrid FTS5 + vector)
timelineChronological context around an observation
get_observationsFetch full details by ID
save_observationManually save something worth remembering
install_packLoad a curated knowledge pack for your stack
send_messageLeave a cross-device or team note
recent_activityInspect what Engrm captured most recently
memory_statsView high-level capture and sync health
ArchitectureThe Architecture tool exposed by this server.

How to install the Engrm MCP server

{
  "mcpServers": {
    "engrm": {
      "command": "npx",
      "args": ["-y", "engrm"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Engrm to Feature.
  • Use Engrm to Cost.
  • Use Engrm to Cross-device.

Frequently asked questions

It connects Engrm to MCP-compatible AI assistants such as Claude and Cursor, exposing 13 tools (Feature, Cost, Cross-device, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Engrm directly.