Claude Desktop

Claude Desktop’s Connectors UI is the smoothest path to connecting Engram. It’s a paste-the-URL-and-sign-in flow with no config files and no API keys to copy. For background on what’s happening under the hood, 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.

Setup

Open the Add Engram connector page. It launches Claude’s connector setup with Engram’s name and URL already filled in. These settings flow into both the desktop app and claude.ai.

Prefer to do it manually? Go to claude.ai/customize/connectors and press the + button to add a custom connector.
Fill in the two fields, then click Add. Both come prefilled if you opened the modal from the link above; otherwise enter them yourself.

Name: anything you want, for example:
```
Engram
```
Remote MCP server URL:
```
https://mcp.engram.page
```
A browser authorization window opens. See First-run auth for what to expect.
Review the requested permissions on the scope screen and approve.
Tell Claude how to use it so it reaches for Engram automatically.
Try it to confirm the connector works.

First-run auth

The first time you connect, Claude Desktop automatically opens a browser window asking you to sign in to Engram. Sign in, tick the permissions you want to grant, and click Approve. The browser hands you back to Claude Desktop automatically. No copy-pasting tokens, no environment variables. It’s the same kind of sign-in flow you’d use for connecting any app to Google, Dropbox, or GitHub.

If you’d rather skip the browser flow (headless, scripted, or shared-vault setups), you can authenticate with an API key instead. See MCP Config → API Key Authentication.

Tell Claude how to use it

Adding the connector is half the job. Claude won’t reach for Engram unless you tell it to. Drop a short instruction into Claude’s global preferences so every conversation knows to use Engram as memory.

Open claude.ai/settings/general.
Find the What personal preferences should Claude consider in responses? field (the global instructions box).
Paste this snippet. Keep it on its own line so it stays in scope for every conversation:

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.

Now Claude reaches for Engram automatically when it needs to look something up or save something you’ve shared.

Try it

Once connected and the global prompt is in place, the connector appears in your sidebar. Try asking:

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.
Read my note titled 'Q3 planning' and pull out the action items.
Show me the frontmatter and outgoing links of 'project-ideas.md'.
Draft a new note titled 'Sync with design, May 21' in my 'Meeting notes' folder with today's takeaways.
Append a 'Decisions' section to 'roadmap.md' with these three items.
List the top-level folders in my vault.
Move everything in 'inbox' that mentions 'Q4' into 'Q4-planning'.

Claude calls Engram’s search (or get_note, write_note, etc.) tool, pulls back results, and answers in-context.

Scopes granted

Claude Desktop requests the mcp scope on the approval screen. That’s a single grant that covers the full MCP tool surface against your vault. Granular per-action scopes (read-only, no-delete, etc.) are on the roadmap. See Scopes for details and the revocation flow.

Troubleshooting (Claude Desktop specific)

The authorization window never opens. Make sure Claude Desktop is on the latest version and that no popup blocker is active.
“Connector failed to load.” Confirm the MCP URL is reachable. Paste it into a browser tab. If you see a structured response page rather than an error, the connection is fine and the issue is on Claude Desktop’s side. Restart it and try again.

For cross-client failures (auth refused, scope errors, sync gaps), see Troubleshooting.

Revocation

Disconnecting takes effect from either side. Pick whichever is handy:

Through the Claude app: open Settings → Connectors, find Engram, and choose Disconnect.

Through Claude on the web: go to claude.ai/customize/connectors, click the Engram connector, and choose Disconnect.

Through Engram: go to app.engram.page/settings/connections and disconnect the session.

Either way, the OAuth token is invalidated server-side, and Claude Desktop will need to re-authenticate to reconnect.

Next steps

MCPProtocol overview.

ScopesPick the minimum permissions.

All integrationsPick a different client.