Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.3ngram.ai/llms.txt

Use this file to discover all available pages before exploring further.

3ngram connects to AI tools via the Model Context Protocol (MCP). Each client connects to the same workspace, so memories saved in one tool show up in the others. Use this URL in every MCP client: 
https://mcp.3ngram.ai/mcp
We are working on adding 3ngram to the Claude and ChatGPT directories for one-click install. We will email users when those listings are live.

​
How client sync works

Some clients reuse MCP configuration across signed-in surfaces. For example, adding 3ngram in Claude.ai makes it available in Claude Desktop when you are signed into the same Claude account. CLI tools such as Claude Code and Codex may use user-level or project-level config depending on the command you run. If 3ngram does not appear in a specific tool, add the same MCP URL there directly. 3ngram uses OAuth with Dynamic Client Registration (DCR). You do not need a static client ID, client secret, API key, or bearer token in your MCP client config.
If you are testing with a demo account, use a private browser window or a separate client profile. MCP writes go to whichever 3ngram account completed OAuth, and most clients do not show that account before every tool call.

​
Claude.ai

  1. Open Claude connector settings, or go to Customize → Connectors from Claude settings.
  2. Click Add custom connector.
  3. Fill in:
    • Name: 3ngram
    • Remote MCP server URL: https://mcp.3ngram.ai/mcp
  4. Leave advanced OAuth client fields blank.
  5. Click Add.
  6. Complete the 3ngram login when Claude opens the OAuth flow.
After connecting, start a new chat and use @3ngram or 3ngram: when you want Claude to call 3ngram tools.

​
Claude Desktop

Claude Desktop uses the same connector configuration as Claude.ai when you are signed into the same account.
  1. Add 3ngram in Claude.ai.
  2. Open or restart Claude Desktop.
  3. Start a new chat and check that 3ngram appears in the connector/tool menu.
If it does not appear, remove and re-add the connector from Claude.ai.

​
ChatGPT

  1. Open Settings → Apps. In newer workspaces this may appear as Settings → Apps & Connectors.
  2. Open Advanced settings and enable developer mode if Create app is hidden.
  3. Choose Create app.
  4. Fill in:
    • Name: 3ngram
    • MCP server URL: https://mcp.3ngram.ai/mcp
    • Authentication: OAuth
  5. Create the app.
  6. Complete the 3ngram login when ChatGPT opens the OAuth flow.
Use /3ngram or @3ngram in a chat to route requests to 3ngram.

​
Codex CLI

Register the hosted MCP server: 
codex mcp add 3ngram --url https://mcp.3ngram.ai/mcp
If Codex does not start OAuth automatically, run: 
codex mcp login 3ngram
You can confirm the server is present with: 
codex mcp list
Then start a Codex session and ask it to use 3ngram:
“3ngram: Search my memories for OAuth setup notes.”
If your Codex version does not support codex mcp add --url, add the entry manually in ~/.codex/config.toml and then run codex mcp login 3ngram: 
[mcp_servers.3ngram]
url = "https://mcp.3ngram.ai/mcp"
For remote dev boxes or locked-down callback ports, set mcp_oauth_callback_port or mcp_oauth_callback_url in the same config file.

​
Claude Code

Choose one setup path.

​
Option A: install the 3ngram plugin

Use the plugin when you want MCP plus the Claude Code briefing, capture, and sync hooks: 
claude --plugin-dir /path/to/engram/claude-code-plugin
Then run /mcp, select 3ngram, and complete the browser login.

​
Option B: MCP-only setup

Register only the hosted MCP server: 
claude mcp add --transport http 3ngram https://mcp.3ngram.ai/mcp
Then authenticate: 
/mcp
Select 3ngram and complete the browser login. By default, Claude Code stores this as a local registration. Add --scope user if you want the registration available across your projects, or --scope project if you want it committed to the project’s .mcp.json.

​
Cursor

Cursor supports remote MCP servers through mcp.json.
Cursor setup is pending final directory-capture verification. Use the configuration below as the current expected setup, and check client troubleshooting if Cursor does not start the OAuth flow.
  1. Open Settings (Cmd/Ctrl+Shift+J) → Features → Model Context Protocol.
  2. Open mcp.json. Use ~/.cursor/mcp.json for a global setup or .cursor/mcp.json inside a project for a project-only setup.
  3. Add a 3ngram entry under mcpServers: 
    {
  "mcpServers": {
    "3ngram": {
      "url": "https://mcp.3ngram.ai/mcp"
    }
  }
}
  4. Save the file and restart Cursor if the server does not appear.
  5. If Cursor prompts for OAuth, sign in to 3ngram and approve access.
Cursor’s OAuth callback is cursor://anysphere.cursor-mcp/oauth/callback, which 3ngram allows for DCR-created clients.

​
Windsurf

Windsurf exposes MCP tools through Cascade.
Windsurf setup is pending final directory-capture verification. Use the configuration below as the current expected setup.
  1. Open Windsurf Settings → Cascade → MCP Servers, or click the MCPs icon in the Cascade panel.
  2. Open the raw mcp_config.json file. The Windsurf editor path is usually ~/.codeium/windsurf/mcp_config.json.
  3. Add a 3ngram entry under mcpServers: 
    {
  "mcpServers": {
    "3ngram": {
      "serverUrl": "https://mcp.3ngram.ai/mcp"
    }
  }
}
  4. Save the file.
  5. Refresh MCP servers in Cascade.
  6. If Windsurf prompts for OAuth, sign in to 3ngram and approve access.
If your organization manages Windsurf, an admin may need to enable MCP access or whitelist the 3ngram server ID.

​
Verify the connection

In any connected client, try:
“3ngram: Remember that I connected this client today.”
Then ask:
“3ngram: Search my memories for connected this client.”
For a fuller verification pass, also try:
“3ngram: Run my briefing.”
If the assistant says it does not have access to 3ngram tools, reopen the client’s MCP settings and reconnect. More recovery steps live in client troubleshooting.

​
Platform support

FeatureClaude.aiClaude DesktopChatGPTCodex CLIClaude CodeCursorWindsurf
MCP toolsYesYesYesYesYesExpectedExpected
OAuth loginYesYesYesYesYesExpectedExpected
Dynamic Client RegistrationYesYesYesYesYesExpectedExpected
Prompt templatesYesYesVia custom instructionsYesYesExpectedExpected
Automatic hook captureNoNoNoNoPlugin onlyNoNo

Quick start

Sign up, connect one client, and save your first memory.

Client troubleshooting

Fix connection, OAuth, and tool-routing problems.