Prerequisite: Install the
engram binary first via Homebrew or binary download.Option A: Workspace Config (Recommended for Teams)
Commit to source control so the whole team gets Engram automatically. Create.vscode/mcp.json in your project:
Option B: User Profile (Global)
Available across all workspaces, but not committed to git.User MCP Config Paths
| Platform | Path |
|---|---|
| macOS | ~/Library/Application Support/Code/User/mcp.json |
| Linux | ~/.config/Code/User/mcp.json |
| Windows | %APPDATA%\Code\User\mcp.json |
Option C: CLI One-Liner
Quick install via command line:Using with Claude Code Extension
The Claude Code extension in VS Code uses its own MCP config at
.claude/settings.json, not .vscode/mcp.json..claude/settings.json config works whether you use Claude Code as:
- A standalone CLI
- A VS Code extension
Adding the Memory Protocol (Recommended)
Without the Memory Protocol, the agent has the tools but doesn’t know WHEN to use them.For Copilot
Create a.instructions.md file in the VS Code User prompts/ folder:
| Platform | Path |
|---|---|
| macOS | ~/Library/Application Support/Code/User/prompts/engram-memory.instructions.md |
| Linux | ~/.config/Code/User/prompts/engram-memory.instructions.md |
| Windows | %APPDATA%\Code\User\prompts\engram-memory.instructions.md |
For Other Chat Extensions
Add the Memory Protocol text to your extension’s custom instructions or system prompt configuration. See Memory Protocol for the full text.Memory Protocol Content
The Memory Protocol tells the agent:- When to save — After bugfixes, decisions, discoveries, config changes, patterns
- When to search — Reactive (“remember”, “recall”) + proactive (overlapping past work)
- Session close — Mandatory
mem_session_summarybefore ending - After compaction — Recover state with
mem_context
Platform-Specific Notes
Windows
Make sureengram.exe is in your PATH. VS Code 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.
Troubleshooting
MCP tools not showing up
Check thatmcp.json exists and has the correct format:
Binary not found
VS Code can’t findengram command:
Extension not loading MCP
Restart VS Code after addingmcp.json:
- Open Command Palette (
Cmd+Shift+P/Ctrl+Shift+P) - Run Developer: Reload Window
Next Steps
- Learn about the Memory Protocol
- Explore MCP Tools
- Set up Git Sync for team memory sharing