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.

Audience: 3ngram users who connected an MCP client but do not see tools, cannot authenticate, or see the AI route requests to the wrong memory system.

​
Quick checks

Use the hosted MCP URL exactly: 
https://mcp.3ngram.ai/mcp
Then verify:
  1. You are signed into the same 3ngram account you expect to use.
  2. The client shows a connected 3ngram MCP server or app.
  3. You start a new chat after adding the server.
  4. You explicitly invoke 3ngram with @3ngram, /3ngram, 3ngram:, or “in 3ngram”.

​
”I do not have access to that tool”

The client did not bind the MCP server into the current chat. Fix:
  1. Open the client’s MCP, app, or connector settings.
  2. Remove the 3ngram entry.
  3. Add it again using https://mcp.3ngram.ai/mcp.
  4. Complete the browser login.
  5. Start a new chat and try 3ngram: What tools do you have available?

​
Login opens but does not complete

OAuth can fail if the browser tab is stale or the client callback expired. Fix:
  1. Close the OAuth browser tab.
  2. Return to the client settings page.
  3. Click reconnect, authenticate, or create the app again.
  4. Complete the login immediately.
If this repeats, sign out of 3ngram in the browser, sign back in, and retry the client connection.

​
The AI saves to native memory instead of 3ngram

Use an explicit route:
“@3ngram Remember that the launch checklist lives in the team repo.”
“3ngram: Save this as a decision: we will use OAuth for MCP login.”
You can also add a custom instruction: 
When I mention memories, commitments, decisions, blockers, briefings, or debriefs,
use the 3ngram MCP tools. Route memory operations to 3ngram, not built-in memory.

​
Claude.ai or Claude Desktop does not show 3ngram

Claude Desktop should pick up Claude.ai connector configuration when you are signed into the same Claude account. Fix:
  1. Confirm 3ngram is connected in Claude.ai → Settings → Connectors.
  2. Restart Claude Desktop.
  3. Start a new chat.
  4. If it still does not appear, remove and re-add the connector in Claude.ai.

​
Claude Code does not show 3ngram

Check the registration: 
claude mcp list
If 3ngram is missing, add it: 
claude mcp add --transport http 3ngram https://mcp.3ngram.ai/mcp
Then run /mcp, select 3ngram, and authenticate.

​
Codex does not show 3ngram

Check the registration: 
codex mcp list
If 3ngram is missing, add it: 
codex mcp add 3ngram --url https://mcp.3ngram.ai/mcp
Start a new Codex session after adding the server.

​
Cursor does not start OAuth

Cursor setup is still pending final verification. The expected config is: 
{
  "mcpServers": {
    "3ngram": {
      "url": "https://mcp.3ngram.ai/mcp",
      "type": "Streamable HTTP"
    }
  }
}
After saving mcp.json, restart Cursor and check the MCP server list again.

​
When to update this doc

Update this page when a client changes its MCP setup UI, when 3ngram is accepted into a client directory, or when Cursor verification is completed.

3ngram MCP

Client-specific setup steps.

Quick start

First account, first client, first memory.