Claude ThoughtSpot Spotter connectorWhat Claude can do in your ThoughtSpot Spotter account.
The Claude ThoughtSpot Spotter connector exposes 5 tools: 4 read, 1 write, 0 undocumented. Four open a session with ThoughtSpot's analytics agent, pass it your questions and collect its answers; the fifth saves those answers as a dashboard.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once ThoughtSpot Spotter is connected
Your numbers live in ThoughtSpot and your questions already go to Claude. With this connector, Claude hands the question to Spotter, ThoughtSpot's analytics agent, which works on your data models under your own permissions. You follow the answer in the chat, ask a follow-up, and can keep the result inside ThoughtSpot.
A numbers question without opening the app. Ask an analytical question in plain language: create_analysis_session opens the session and picks the data source if you did not name one, send_session_message passes the question, and get_session_updates brings the answer back as it streams in.
Dig deeper in the same session. ThoughtSpot describes sessions as conversational: a follow-up goes into the open session once the previous answer is complete.
Keep what matters. If you ask, create_dashboard gathers the session's answers into a ThoughtSpot dashboard and returns a direct link.
What Claude does not do here: it sees no more data than you do, since ThoughtSpot's row-level and column-level security rules apply automatically. It cannot build a dashboard if your profile lacks content creation rights, and it watches nothing in the background. We have no n8n, Make or Zapier page for ThoughtSpot; the Integrations hub lists the platforms we cover.
The vocabulary in one minute
The Claude terms you will meet on this page.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can use it while answering you.
- Tool
- A named action the connector opens to Claude. Claude picks which ones to call on its own; the directory sheet lists them.
- Authorization
- ThoughtSpot's own sign-in screen, where you hand Claude the access it will use afterwards. Granted once, per person.
- Approval
- The confirmation Claude waits for before an action that changes the account, such as creating a dashboard, shown when it matters.
- MCP
- The open standard connectors are built on: it is what lets an assistant like Claude hold a conversation with ThoughtSpot.
Connecting ThoughtSpot Spotter to Claude
- 01
Find the connector
Open Claude's settings, go through Customize and then Connectors, and look for ThoughtSpot Spotter. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization before each member connects.
- 02
Sign in to ThoughtSpot
Click Connect on its row, then sign in through the window ThoughtSpot opens. You need access to a ThoughtSpot instance., which the publisher lists as a prerequisite.
- 03
Review the authorization screen
Read ThoughtSpot's authorization screen before accepting: it is ThoughtSpot, not Claude, that sets what the access covers. From then on Claude works with your ThoughtSpot permissions and nothing beyond them.
The 5 tools in the Claude ThoughtSpot Spotter connector
ThoughtSpot Spotter gives Claude 5 tools: 4 that read your account, 1 that change something in it.
Five tools, all described by ThoughtSpot in its developer reference. Four are for querying your data; only one, create_dashboard, is described as creating content, a dashboard. The documentation does not say whether opening a session or sending a question leaves anything behind in ThoughtSpot: we class them as lookups because they ask questions, with no guarantee beyond that. Names stay exactly as Claude shows them.
- 4 read
- 1 write
What Claude looks up (4)
4 toolsFour tools that check the connection, ask Spotter questions and collect the answers.
check_connectivity
A basic health check: Claude confirms that the ThoughtSpot service is up and responding before it opens an analysis session.
create_analysis_session
The required first step: Claude starts a session with ThoughtSpot's analytics agent. If you do not name a data source, ThoughtSpot selects the most relevant one for your question.
send_session_message
Inside the open session, Claude passes your question or follow-up in plain language. The answer does not come back here but through the next tool.
get_session_updates
Claude checks the session repeatedly until the answer is complete, because Spotter delivers it in pieces, reasoning steps included, and every piece has to be put together.
What Claude creates (1)
1 toolOne tool that saves answers as a dashboard in ThoughtSpot. No source describes a dedicated confirmation, so the general rule applies.
create_dashboard
Approval: see the ruleClaude gathers answers produced during the analysis into a new ThoughtSpot dashboard and returns its ID along with a direct link to it in ThoughtSpot.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on your account. Here a single action changes ThoughtSpot: creating a dashboard, which the publisher's walkthrough presents as the user's choice.
No source describes a confirmation specific to create_dashboard, so the general rule applies. Claude works with your ThoughtSpot permissions and nothing more; the publisher states that row-level and column-level security rules apply to answers automatically. On Team and Enterprise, workspace owners can limit what a connector may do for the whole organization, for example keeping questions open and closing creation, and nobody can override that from their own account.
Which plans the connector is on
Plan availability is not published anywhere connector by connector: none of the 819 sheets in the official directory shows it.
The general rule is public. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile; on Team and Enterprise, an Owner or Primary Owner enables them for the organization before anyone connects. For ThoughtSpot Spotter's current status, check its sheet in the official directory, which is the only place that shows it.
Where the ThoughtSpot Spotter connector stops
A connector is not an automation. Claude calls these tools while it is answering you, and no alert goes out on its own when a metric moves.
The tool list on the sheet is an observed floor, not a guarantee. The directory's verification badge is not a security audit, and Anthropic notes that it does not choose the tools a publisher exposes. Only ThoughtSpot documents this connector, in its developer documentation; no Claude help article covers it. The publisher flags the following limits there, each one tied to sign-in, sessions or the instance behind them.
Need help connecting ThoughtSpot Spotter to Claude?
A person reads every message.
