Skip to main content
Prerequisite: Install the engram binary first via Homebrew or binary download.
VS Code supports MCP servers natively in its chat panel (Copilot agent mode). This works with any AI agent running inside VS Code — Copilot, Claude Code extension, or any other MCP-compatible chat provider. Commit to source control so the whole team gets Engram automatically. Create .vscode/mcp.json in your project:
1

Install engram binary

2

Create workspace MCP config

Create .vscode/mcp.json:
3

Commit to git

4

Restart VS Code

Reload the window or restart VS Code.

Option B: User Profile (Global)

Available across all workspaces, but not committed to git.
1

Open Command Palette

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux)
2

Run MCP: Open User Configuration

Type “MCP: Open User Configuration” and select it
3

Add engram server

Add to the opened mcp.json:
4

Save and restart

Save the file and reload VS Code.

User MCP Config Paths

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.
If you’re using the Claude Code extension inside VS Code, follow the Claude Code setup instructions instead. The .claude/settings.json config works whether you use Claude Code as:
  • A standalone CLI
  • A VS Code extension
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: Paste the Memory Protocol from DOCS.md into this file.

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_summary before ending
  • After compaction — Recover state with mem_context
Minimal version for VS Code instructions:

Platform-Specific Notes

Windows

Make sure engram.exe is in your PATH. VS Code resolves MCP commands from the system PATH. Check:
If not found, add the directory containing engram.exe to your PATH.

macOS

If you installed via Homebrew, engram is automatically in PATH:

Linux

If you installed via Homebrew:
If you downloaded a binary, move it to /usr/local/bin or add its directory to PATH.

Troubleshooting

MCP tools not showing up

Check that mcp.json exists and has the correct format:

Binary not found

VS Code can’t find engram command:
If missing, install via Homebrew or binary download.

Extension not loading MCP

Restart VS Code after adding mcp.json:
  1. Open Command Palette (Cmd+Shift+P / Ctrl+Shift+P)
  2. Run Developer: Reload Window

Next Steps