Connect Engram to your AI

Engram is a remote MCP server. Every client below connects to the same URL, signs you in with OAuth, and then reads and writes the notes in your vault. Nothing to install, and Obsidian does not need to be open.

https://mcp.engram.page

The server speaks Streamable HTTP and authenticates with OAuth 2.1. Clients register themselves automatically, so you never copy a client ID or secret.

Before you start

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.
• If you plan to use an API key instead of OAuth: API keys need Pro. OAuth sign-in works on every tier, including Free, and is the recommended path. Free and Starter cannot create or use API keys.

Claude (web and desktop)

1. Open claude.ai/customize/connectors. Settings made here apply to both claude.ai and the desktop app.
2. Click +, then Add custom connector.
3. Enter Engram as the name and https://mcp.engram.page as the remote MCP server URL. Leave Advanced settings empty.
4. Click Add, then Connect, and approve the sign-in window.

Claude’s Free plan allows one custom connector. Full walkthrough: Claude Desktop.

ChatGPT

Custom connectors live behind ChatGPT’s Developer mode, on the web app, on eligible paid plans. On a Business or Enterprise workspace an admin has to allow it first.

1. Go to Settings → Apps → Advanced settings and turn on Developer mode.
2. Back in Settings → Apps, click Create app.
3. Name it Engram, set the MCP server URL to https://mcp.engram.page, and choose OAuth for authentication.
4. Click Scan Tools and wait for it to finish.
5. Click Create and approve the sign-in window.
6. In a chat, pick Engram from the tools menu in the composer.

On a Business workspace, the app lands in Workspace settings → Apps → Drafts until an admin publishes it.

Full walkthrough: ChatGPT.

Grok

Grok has no connector directory listing for Engram. You add it as a custom connector by URL.

1. Open grok.com/connectors.
2. Click New Connector, then Custom.
3. Paste https://mcp.engram.page and complete the sign-in.

Building on the xAI API instead of the Grok app? See Grok (xAI API).

Cursor

Add Engram to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

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

Fully quit and reopen Cursor. The sign-in window opens the first time the agent calls an Engram tool. Full walkthrough: Cursor.

VS Code

VS Code reads MCP servers in Copilot Chat’s Agent mode. Run MCP: Add Server from the Command Palette, or add this to .vscode/mcp.json:

{
  "servers": {
    "engram": {
      "type": "http",
      "url": "https://mcp.engram.page"
    }
  }
}

Click the Auth code-lens above the engram entry to sign in. Full walkthrough: GitHub Copilot.

Claude Code

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

Restart claude, run /mcp, pick engram, and choose Authenticate. Add --scope user to make Engram available in every project. Full walkthrough: Claude Code.

Any MCP client

If your client supports remote MCP servers, give it:

• URL: https://mcp.engram.page
• Transport: Streamable HTTP
• Auth: OAuth. Engram publishes its authorization server metadata and accepts Dynamic Client Registration, so a compliant client needs nothing else.

A client that cannot run a browser sign-in can send an Engram API key as a Bearer header instead. API keys need Pro. Config shapes for both are in MCP Config.

First sign-in

The first time you connect, the client 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 the client 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.

Check it works

Ask your AI something only your notes can answer, for example:

What value did I set for POOL_SIZE in my deploy notes?

If it answers from your vault, you are connected. If not, see Troubleshooting.

Disconnect

Remove the connector in your AI client, then revoke its session in app.engram.page/settings/connections.