Claude Connector

Connect CloudThinker to Claude to read incidents, costs, code reviews, and security findings, and to start agent runs from a Claude chat

Connect CloudThinker to Claude so Claude can read your workspace and start CloudThinker agent runs. The connector is a remote Model Context Protocol (MCP) server, and only Claude clients can connect today.

Prerequisites

• A CloudThinker account with access to at least one workspace
• Claude (claude.ai or the desktop app) or Claude Code
• On a Claude Team or Enterprise plan, a Claude organization owner adds the connector first. Each member then connects on their own.

Connect Claude

The server URL is the same on every path:

https://app.cloudthinker.io/api/mcp

Claude (web and desktop)

1. Add the connector

   In Claude, go to Customize → Connectors, click Add, then Add custom connector. Team and Enterprise owners use Organization settings → Connectors instead.

2. Enter the URL

   Name it CloudThinker, paste the server URL, and click Continue. Keep the detected sign-in settings, then click Add.

3. Connect and approve

   Claude sends you to CloudThinker in your browser. Sign in, pick a workspace, and click Allow. If Claude does not start sign-in, open the connector in Customize → Connectors and choose to connect.

Claude Code

1. Add the server

   claude mcp add --transport http cloudthinker https://app.cloudthinker.io/api/mcp
   
2. Sign in

   In Claude Code, run /mcp, select cloudthinker, and follow the browser steps. Sign in, pick a workspace, and click Allow.

Success state: Claude shows CloudThinker as connected, and its tools are available in the chat.

The connector is not in Claude’s Connectors Directory yet. Add it as a custom connector with the URL above.

What you approve

The approval page names the app that is connecting and the host Claude returns to. It then shows one workspace and three permissions:

• Read incidents, costs, code reviews, automations, and security findings in this workspace
• Start CloudThinker runs that ask you before any change
• Act as you, starting in the workspace you pick here; Claude can switch to other workspaces you belong to

Sign-in uses your normal CloudThinker login, so SSO and MFA apply. If you belong to several workspaces, pick the one Claude starts in. You can ask Claude to switch later; see Switch workspaces.

When Claude Code connects from your own computer, the page adds a warning. Click Allow only if you started that connection.

What Claude can do

Claude gets 22 tools. Most only read data. Ask CloudThinker starts a run, and Switch workspace changes the workspace Claude works in.

Workspace

Tool	What it does
whoami	Shows who Claude acts as, the workspace it works in now, and the workspaces it can switch to.
switch_workspace	Moves Claude to another workspace you belong to.

Incidents

Tool	What it does
list_incidents	Lists incidents and investigations, newest first. Filter by status, severity, or text.
get_incident	Reads one incident: status, severity, latest root cause analysis, and suggested fixes.

Agent runs

Tool	What it does
ask_cloudthinker	Starts a CloudThinker agent run from your request.
get_run	Reads the status and answer of a run that Claude started.

Automations

Tool	What it does
list_automations	Lists scheduled and event-triggered automations.
get_automation	Reads one automation: instructions, triggers, schedule, and recent runs.
list_automation_runs	Lists past runs of one automation.

Review

Tool	What it does
list_code_reviews	Lists merge and pull requests that Review checked.
get_code_review	Reads one review and its findings, with file, line, and suggested fix.

Optimize

Tool	What it does
list_cost_connections	Lists the cloud billing accounts CloudThinker analyzes.
get_cost_overview	Reads spend this month, forecast, top services, and top savings.
list_cost_findings	Lists open savings findings, highest savings first.
get_cost_finding	Reads one savings finding and its analysis.
list_cost_anomalies	Lists cost spikes, largest first.

Cyber

Tool	What it does
list_security_apps	Lists apps under penetration testing.
get_security_app_coverage	Reads what a penetration test of one app can cover, and what blocks it.
get_security_finding	Reads one penetration test finding.
list_code_audit_branches	Lists repository branches under Code Audit.
get_code_audit_branch	Reads one branch’s latest audit and security findings.
get_code_audit	Reads one Code Audit run: status, outcome, and failure.

Switch workspaces

Ask Claude in plain words, for example “Which CloudThinker workspace are you using?” or “Switch to the Staging workspace”. Claude calls whoami to list your workspaces, then switch_workspace. Every later tool call reads and starts runs in the new workspace.

• You can switch only to a workspace you belong to. CloudThinker checks your membership and role on each switch and each call.
• The switch applies to the whole connection. Every Claude chat that uses this connector moves to the new workspace. Ask Claude “Which workspace are you using?” when in doubt.
• Records stay in their workspace. After a switch, Claude cannot read a run or an incident from the old workspace until it switches back.

Ask CloudThinker to investigate

ask_cloudthinker starts a normal CloudThinker agent run. It uses the connections your workspace already has.

• It returns at once. Claude gets a run ID and a link. Claude then calls get_run to read the answer when the run finishes.
• It uses credits. A run bills your workspace like a chat. See Usage.
• It always asks before a change. Runs started from Claude use Manual approval, even when the workspace uses Auto Mode. A change waits until you approve it in CloudThinker through the link. See Approval.

Example prompts

Type these in Claude after you connect.

What incidents are open in production, and what caused the latest one?

Which cost savings findings in CloudThinker are worth the most per month? Show the top five with the evidence for each.

List the code review findings from the last week with high severity, and tell me which ones are still unresolved.

Switch to my Production workspace and list the open critical incidents.

Ask CloudThinker to investigate why checkout latency rose after yesterday's deploy, and tell me what it finds.

How access is checked

Claude acts as you, in the one workspace you picked. CloudThinker checks on every call that:

• You are still a member of the workspace.
• Your role has the permission for that tool.
• The product module behind the tool is turned on.

Claude never sees more than you can see in CloudThinker.

Revoke access

Open Account settings → Connected apps in CloudThinker and revoke the Claude connection. Access ends at once. The next call fails, and Claude has to ask you to connect again.

Also remove the connector in Claude: in Customize → Connectors for Claude, or claude mcp remove cloudthinker for Claude Code.

Troubleshooting

Access to this CloudThinker workspace was removed

You are no longer a member of the workspace you connected, or the workspace is gone. Disconnect and connect again, then pick a workspace you can access.

This CloudThinker role lacks a permission

The message names the missing permission. Ask a workspace admin to grant it, or to change your role.

A run is waiting for approval

Claude reported the run as waiting. Open the link Claude gave you, then approve or reject the change in CloudThinker. Ask Claude to check the run again.

A run failed because the workspace is out of credits

Add credits or raise the workspace limit. See Usage and Credit limits. Then ask again.

The connection request is invalid or expired

The approval page expires after 10 minutes. Go back to Claude and connect again.

A tool says a module is turned off

Your administrator turned off that product module. Ask them to turn it on.

Related

Approval

How Manual mode pauses a change for your decision

Auto Mode

Why runs from Claude still ask first

Usage

How runs use credits

MCP connection

Let CloudThinker agents call your own MCP servers