@thinkingroot/mcp

Give any AI agent a living, per-user memory — by pasting one URL.

ThinkingRoot is the managed cloud for the cognition database. This connects any MCP client (Claude, Cursor, Codex, VS Code, …) to your project's brain over the hosted gateway, exposing the full tool catalog — including the Compiled Workspace tools: ask (citation-gated, refuses rather than hallucinates), search, compile, repo_map, code_traverse, code_search_entity, summaries, plus memory remember/recall.

Every answer is grounded in verbatim, byte-anchored sources. Memory is deletable and provable — not an opaque blob.

Two ways to connect

1. Hosted URL (no install)

For clients that support remote MCP servers, paste the hosted endpoint and your key — nothing to install:

URL:    https://api.thinkingroot.com/mcp
Header: Authorization: Bearer tr_sk_…

Get a tr_sk_… project key from the Console → Keys tab. That's the whole setup — the gateway authenticates the key, resolves your project's engine, and serves the tools over Streamable HTTP. (Browser clients like Claude and ChatGPT can skip the key entirely: paste the URL and sign in — the gateway runs OAuth.)

2. One-line bridge (any stdio client)

For clients that speak stdio only, this package bridges stdio ↔ the hosted Streamable HTTP endpoint. Drop it into your MCP client config:

{
  "mcpServers": {
    "thinkingroot": {
      "command": "npx",
      "args": ["-y", "@thinkingroot/mcp"],
      "env": { "TR_PROJECT_KEY": "tr_sk_…" }
    }
  }
}

• TR_PROJECT_KEY (required) — a tr_sk_… project API key.
• TR_GATEWAY_URL (optional) — defaults to https://api.thinkingroot.com.

Works in Claude Desktop, Claude Code, Cursor, Codex, Windsurf, and any client that runs a command-based MCP server.

Per-user minds

ThinkingRoot isn't one shared database — each of your end-users can have their own private, fail-closed brain (u_{userId}). To scope a hosted session to one user, mint a user-bound embed token (tr_em_…) from your backend via POST /tokens/session and present it in place of the tr_sk_ key. The gateway derives the identity from the token, so a session can never read another user's mind.

Security

• Fail-closed: without a valid tr_sk_… key the bridge exits rather than connect unauthenticated.
• The key is sent only to the hosted gateway over TLS; the underlying engine key is never exposed to the client.
• tr_pk_… publishable keys are ask/recall-scoped and domain-locked — safe for browser embeds; tr_sk_… full-scope keys belong on a server.

Links

• Docs & keys: thinkingroot.com
• SDK: @thinkingroot/sdk · CLI: thinkingroot
• Built on mcp-remote for the stdio bridge.