ThinkingRoot Docs
Integrations

Integrations

The ways your tools and code connect to a ThinkingRoot project.

There are three ways in and out of a project, all fronted by the gateway and authenticated with a tr_sk_… key:

MCP

Connect AI tools (Claude Code, Cursor, Codex…) over Model Context Protocol.

Build an integration

Wire any HTTP API in as a Root Function — credentials from the Secrets vault, egress-gated fetch.

Clients & SDKs

REST, the root CLI, and where the open-source SDKs live.

Framework adapters

Drop your brain into React, the Vercel AI SDK, or LangChain — recall, ground, and remember with provenance.

Which one do I want?

  • You're an AI tool / agent → MCP. You get tools (ask, search, compile, branch ops) plus any connectors you've installed.
  • You're writing application code → the REST API through the gateway's /engine proxy.
  • You're at a terminal or scripting → the root CLI.
  • You want to pull in an external system → connectors.

Multi-tenant SaaS

Serve many of your own end-users under one project — isolated memory, per-user metering, and fair rate limits.

MCP

How ThinkingRoot exposes your project over the Model Context Protocol.

On this page

Which one do I want?