Claude Code

Claude Code’s claude mcp add CLI handles the config edit for you and keeps the registration scoped per project or per user. OAuth runs in your browser the first time you call an Engram tool. For protocol background, see MCP.

Prerequisites

Before you start, confirm:

• You have an Engram account at app.engram.page.
• At least one vault is synced. Open the Obsidian plugin or the web app and confirm notes have synced within the last day.
• You can sign in via browser. The MCP auth flow opens a browser window.

Endpoint

https://mcp.engram.page/api/mcp

Setup

1. Register Engram with the Claude Code CLI.

claude mcp add --transport http --scope user engram https://mcp.engram.page/api/mcp

--scope user makes Engram available across every project. Use --scope project instead to limit Engram to the current repo’s .mcp.json.

Prefer to hand-edit? Add the block below to ~/.claude.json (user-scoped) or .mcp.json at the project root:

{
  "mcpServers": {
    "engram": {
      "url": "https://mcp.engram.page/api/mcp"
    }
  }
}

2. Reload. Exit your current Claude Code session and re-run claude. Run claude mcp list to confirm Engram is registered. It should appear with status △ needs authentication.

First-run auth

Claude Code doesn’t auto-prompt for OAuth. In a fresh session, run /mcp, select engram, then choose Authenticate. Your browser opens to sign in to Engram and approve the connection. Claude Code stores the token and reuses it from there on. The grant is the full mcp scope. Granular per-action scopes are on the roadmap.

Tell Claude how to use it

Append the snippet below to ~/.claude/CLAUDE.md, Claude Code’s user-level instructions file. It applies to every project. Per-repo overrides go in a project-level CLAUDE.md at the repo root.

Engram holds my personal notes — treat it as your long-term memory of me. Search it when a question depends on context I might have shared before. Before saving or updating a note, ask first.

Try it

Once registered and authenticated, ask Claude:

• Search my vault for notes about the engineering interview process and summarize the top three.
• Find anything I wrote about embeddings in the last month.

Claude calls Engram’s search (or get_note, write_note, etc.) tool, pulls back results, and answers in-context. If the tool fires, you’re set.

Troubleshooting (Claude Code specific)

• claude mcp list shows engram missing. The command ran in a different scope than expected. Check both ~/.claude.json (user) and .mcp.json (project) for the entry, then re-run claude mcp add with the right --scope flag.
• /mcp doesn’t list engram in the picker. You didn’t exit and re-launch the CLI after claude mcp add. Restart claude.
• Authenticate option does nothing, or the browser never opens. A headless or remote session can’t open a browser. Run Claude Code on a host with a desktop browser, or use an API key in the config block (see MCP Config → API Key Authentication).

For cross-client failures, see Troubleshooting.

Revocation

To disconnect Claude Code from Engram:

1. In Claude Code, find the connector or MCP server entry and remove it.
2. In Engram, open your account → API Keys & Sessions and revoke the matching session.
3. The OAuth token is invalidated server-side. Claude Code will need to re-authenticate to reconnect.

You can also drop the registration locally with claude mcp remove engram. That removes the config entry but leaves the server-side token live until you revoke it in Engram.

Next steps

MCP Protocol overview.

Scopes What the grant covers.

All integrations Pick a different client.