Connect your AI tool
Point Claude Code, Claude Desktop, Cursor, or Codex at your project over MCP.
Your project speaks MCP (Model Context Protocol), so any MCP-capable AI tool can read from — and act on — your cognition graph. The fastest way to get the exact config is the Console's MCP & Agents tab, which generates a copy-paste block for each client.
Get a project API key
In the API Keys tab, create a key. It looks like tr_sk_… and is shown in
full once — copy it now. This key identifies your project to the gateway;
all MCP traffic authenticates with it as a bearer token.
Copy the config for your client
Open MCP & Agents, pick your client, and copy the generated block. The
shapes are below — substitute the MCP URL shown in the tab for <MCP_URL>
and your key for tr_sk_….
File: ~/.config/claude-code/mcp.json
{
"mcpServers": {
"thinkingroot": {
"transport": {
"type": "sse",
"url": "<MCP_URL>",
"headers": { "Authorization": "Bearer tr_sk_…" }
}
}
}
}File: ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"thinkingroot": {
"command": "npx",
"args": ["-y", "mcp-remote", "<MCP_URL>", "--header", "Authorization:${TR_AUTH}"],
"env": { "TR_AUTH": "Bearer tr_sk_…" }
}
}
}Claude Desktop speaks stdio, so it runs mcp-remote (the standard remote-MCP
bridge) to connect to your project's SSE endpoint. The bearer token is passed
through the TR_AUTH env var rather than inline, because mcp-remote
mis-handles a space inside a --header value.
Cursor → Settings → MCP → New:
Name: thinkingroot
Type: SSE
URL: <MCP_URL>
Headers:
Authorization: Bearer tr_sk_…File: ~/.codex/mcp.toml
[servers.thinkingroot]
url = "<MCP_URL>"
headers = { Authorization = "Bearer tr_sk_…" }Restart the client and verify
Restart your AI tool so it loads the new server. It should list ThinkingRoot's tools (ask, search, compile, branch operations, and any connectors you've installed). Ask it a question your graph covers — the answer comes back grounded in your claims.
How auth works
The engine's own MCP endpoint is unauthenticated and loopback-only. The gateway
sits in front: it authenticates your tr_sk_… key, resolves your project's
engine, injects the engine's internal key, and relays the MCP stream. Your
tr_sk_… key never reaches the engine, and the engine is never exposed
directly. See MCP integration for the transport
details.