Engram MCP Server

Engram is a hosted MCP server that provides reliable memory for AI agents:. That is what the engram mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Give your AI agents a memory they can trust. Engram lets your AI remember past conversations, facts, and decisions, so it feels more like a real teammate.

The tools it exposes

The server publishes 4 tools. What each one is for:

• Cursor — The Cursor tool exposed by this server
• Windsurf — The Windsurf tool exposed by this server
• OpenCode — The OpenCode tool exposed by this server
• OpenClaw — Once the skill is live on ClawHub:

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

What it needs from you

Configuration is passed through the environment: ENGRAM_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Engram's toolset — Cursor, Windsurf, OpenCode and 1 more — is a fair guide to whether it matches your workflow.

This entry was verified against Engram's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.