Prerequisite: Install the
engram binary first via Homebrew or binary download.Setup
Add to.cursor/mcp.json in your project (same path on all platforms):
1
Install engram binary
2
Create MCP config
Create
.cursor/mcp.json in your project root:3
Restart Cursor
Reload the window or restart Cursor.
Adding the Memory Protocol (Recommended)
Add the Memory Protocol to.cursorrules file to teach the agent when to use memory.
Create or edit .cursorrules in your project root:
Platform-Specific Notes
Windows
Make sureengram.exe is in your PATH. Cursor resolves MCP commands from the system PATH.
Check:
engram.exe to your PATH.
macOS
If you installed via Homebrew,engram is automatically in PATH:
Linux
If you installed via Homebrew:/usr/local/bin or add its directory to PATH.
Cursor Rules File
The.cursorrules file is Cursor’s project-level instruction file. It’s similar to:
.clauderules(Claude Code).windsurfrules(Windsurf)CLAUDE.md(Claude Code)GEMINI.md(Gemini CLI)
.cursorrules is injected into the agent’s system prompt.
Memory Protocol Behavior
With the Memory Protocol in.cursorrules, the agent:
- Saves proactively after bugfixes, decisions, discoveries, patterns
- Searches reactively when you say “remember” or “what did we do”
- Searches proactively when starting work that might overlap past sessions
- Closes sessions with
mem_session_summarybefore saying “done” - Recovers state after compaction with
mem_context
Troubleshooting
MCP tools not showing up
Check that.cursor/mcp.json exists:
Binary not found
Cursor can’t findengram command:
Agent doesn’t use memory
Check that.cursorrules includes the Memory Protocol:
Next Steps
- Learn about the Memory Protocol
- Explore MCP Tools
- Set up Git Sync for team memory sharing