Connect your AI tool
Point Claude Code, Claude Desktop, Cursor, Codex, or any AI tool at ThinkingMemory over MCP.
Your project speaks MCP (Model Context Protocol), so Claude, Cursor, Codex — any AI tool — can use ThinkingMemory: remember, recall, and ask from your real sources.
The fastest way — one command
npx thinkingroot connectIt signs you in, lets you pick your tools, and wires each one. It also installs
the memory skill (so the agent recalls automatically) and slash commands
(/recall, /remember, /context, /forget) for manual control. One brain,
every tool.
You don’t need to write code
Run one command, restart the tool, ask a question. ThinkingMemory answers from what you taught — with citations when it can.
Manual setup (per client)
Prefer to configure by hand? Every tool uses the same npx bridge
(@thinkingroot/mcp) — it connects to your project, injects your key, and adds
the slash commands. First grab a tr_sk_… key from the API Keys tab.
Use the bridge, not a bare URL
Most clients can’t yet connect to a plain hosted MCP URL (they attempt
Streamable-HTTP + OAuth and fail). The npx @thinkingroot/mcp bridge is the
reliable path everywhere — that’s what connect writes for you.
File: .mcp.json (project) or ~/.claude.json (global)
Claude Code
json
{
"mcpServers": {
"thinkingroot": {
"command": "npx",
"args": ["-y", "@thinkingroot/mcp"],
"env": { "TR_PROJECT_KEY": "tr_sk_…" }
}
}
}File: ~/Library/Application Support/Claude/claude_desktop_config.json
Claude Desktop
json
{
"mcpServers": {
"thinkingroot": {
"command": "npx",
"args": ["-y", "@thinkingroot/mcp"],
"env": { "TR_PROJECT_KEY": "tr_sk_…" }
}
}
}File: ~/.cursor/mcp.json
Cursor
json
{
"mcpServers": {
"thinkingroot": {
"command": "npx",
"args": ["-y", "@thinkingroot/mcp"],
"env": { "TR_PROJECT_KEY": "tr_sk_…" }
}
}
}File: ~/.codex/config.toml
Codex
toml
[mcp_servers.thinkingroot]
command = "npx"
args = ["-y", "@thinkingroot/mcp"]
[mcp_servers.thinkingroot.env]
TR_PROJECT_KEY = "tr_sk_…"Restart and verify
Restart your AI tool so it loads the new server. It should list ThinkingRoot
tools (ask, recall, remember, search, and any
connectors you’ve installed), and the / menu shows
the slash commands. Ask something you’ve already taught — the answer should come
from ThinkingMemory, with citations.
How auth works
The engine’s own MCP endpoint is loopback-only. The bridge connects to the
gateway, which checks your tr_sk_… key, finds your project’s ThinkingMemory,
and relays the stream. Your key never reaches the engine; the engine is never
exposed directly. See MCP integration.