AI Integrations

Claude, Cursor, ChatGPT, and other AI assistants connect to your vault over OAuth. Each connection is a deliberate grant you can revoke any time. They all use MCP (the Model Context Protocol) under the hood. Pick your client below; the setup is the same shape across all of them.

What you get

Semantic + full-text search across your whole vault from inside the AI client
Read individual notes so Claude can pull a note and reason over its contents
Draft and edit notes directly into your vault (when you grant write scopes)
Folder operations (list, create, reorganize)
OAuth-authorized with explicit grant per client, revocable any time from your Engram account; granular per-action scopes are on the roadmap
OAuth out of the box. Sign-in flow, nothing to copy-paste
Or use an API key for headless / programmatic access and unique vault-sharing setups

Pick your client

Chat assistants

Claude DesktopAnthropic's desktop app. Connectors UI with OAuth, no config files.

ChatGPTCustom Connectors via Developer Mode. Plus / Pro / Team / Enterprise on web.

Open WebUISelf-hosted chat UI. Native Streamable HTTP MCP, OAuth or API key.

LobeChatPlugin-based MCP. Web + Desktop. Bearer-token auth.

Coding agents

Claude CodeAnthropic's CLI agent. claude mcp add, OAuth on first call.

CursorDrop a mcp.json, restart, OAuth fires on first tool call.

WindsurfCascade agent. Single mcp_config.json, hit Refresh.

GitHub CopilotVS Code agent mode. .vscode/mcp.json, works on the free Copilot tier.

ClineVS Code MCP Servers panel. API key in headers.

ContinueYAML-driven config, Agent mode only.

OpenCodeCLI agent. Native OAuth + DCR via opencode.json.

Developer / API

Grok (xAI API)Server-side Remote MCP Tools via the xAI SDK. For developers, not the Grok app.

Custom MCP clientHTTP + OAuth handshake (or API key) for your own SDK, or any client not listed above (Zed, JetBrains plugins, etc.).