Skip to main content
You sign in with your ThinkOut account, the same one you use in the app, and the assistant only sees the workspaces you gave it access to. Clients that cannot sign in can send an MCP key instead.

Claude

1

Open connector settings

In Claude, go to Customize → Connectors, press + and choose Add custom connector.
2

Add the server

Name it ThinkOut, enter the address https://mcp.thinkout.io and press Add. Leave the advanced settings empty.
3

Sign in

Press Connect next to ThinkOut and authorise with your ThinkOut account.
4

Enable it in a chat

In a conversation, open the + menu, choose Connectors and make sure ThinkOut is turned on.
On Team and Enterprise plans, an owner adds the connector under Organization settings → Connectors → Add → Custom → Web. Members then find it under Customize → Connectors and press Connect.

Claude Code

Open the terminal and insert:
Then run /mcp and complete the sign-in in your browser.

Codex

Open the terminal and insert:

Gemini CLI

Add the server to ~/.gemini/settings.json:
Then run /mcp auth thinkout.
On Gemini Enterprise, the administrator has to request client credentials from the ThinkOut team first.

ChatGPT

1

Turn on developer mode

In ChatGPT on the web, go to Settings → Security and login and turn on Developer mode.
2

Add the plugin

Open Plugins, press +, name it ThinkOut, give it a short description, enter the address https://mcp.thinkout.io and choose OAuth as the authentication.
3

Sign in

Create it, review the tools ChatGPT found, and authorise with your ThinkOut account.
4

Enable it in a chat

In a conversation, open the + menu, choose Developer mode and tick ThinkOut. A saved plugin is off until you enable it in the chat.
Developer mode needs a paid plan and is web only. On Business and Enterprise workspaces, an administrator has to allow custom MCP connectors first, under Workspace Settings → Permissions & Roles → Connected Data.

Other clients

Any MCP-compatible client that supports Streamable HTTP can connect at the address https://mcp.thinkout.io, either by signing in or by sending an MCP key as a bearer token.

MCP key

Some clients cannot run the interactive sign-in. Those can authenticate directly instead: create an MCP key in ThinkOut under My account, and send it in the Authorization header.
In a client that takes its own configuration file:
An MCP key belongs to the account rather than to a person, so it reaches every workspace in the account, not only the ones you can open yourself. It keeps working until you regenerate or revoke it. Sign in instead wherever the client supports it.