ThoughtSpot Spotter
Ask your company's governed analytics a question in natural language and get a chart back. Session-based, not request/response: one tool carries free-text questions to ThoughtSpot's Spotter engine. Row-level and column-level security are documented as enforced automatically.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect ThoughtSpot Spotter via MCP
https://agent.thoughtspot.app/mcp?api-version=latestWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
ThoughtSpot Spotter Tools & Capabilities (5)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The directory tool list is three short.
search_objects,list_orgsandswitch_orgare documented for this version and absent from Anthropic's 2026-08-16 snapshot. Read the vendor's tool reference, not the listing. - The tool count does not bound the surface.
send_session_messageaccepts free text, so what the connector can reach is whatever Spotter can answer. - No scopes are published. There is no RFC 9728 descriptor in any path form and no
scopes_supportedin the RFC 8414 document, so there is no machine-readable grant to review or narrow. ?api-version=latestaccepts changes silently. ThoughtSpot warns that new versions may alter tool behaviour, input parameters and output schemas, and recommends pinning a date instead.- The bare
/mcppath currently serves the legacy tools. ThoughtSpot documents it as the baseline version today and says it will move later — so the same host serves two different tool sets depending on the query string. - RLS and CLS enforcement is documented, not observed by us. ThoughtSpot states it applies automatically in data source responses; the gated endpoint meant we could not test it.
- Writing needs privileges beyond reading. Data download and content creation privileges are required to build charts or Liveboards from a session.
- Org tools are conditional. ThoughtSpot restricts
list_orgsandswitch_orgto OAuth connections on Org-enabled instances, and its code removes them from the tool list otherwise. - An Org switch outlives the conversation. ThoughtSpot states the active Org persists across all your active sessions and resets only on re-authentication or prolonged inactivity.
- Sessions expire. ThoughtSpot documents re-authentication after 14 days idle, and possible sign-out if the instance is unreachable when a token renews.
- Third-party cookie blocking can break sign-in. ThoughtSpot lists this as a known limitation, because the flow relies on a browser cookie from your cluster.
- It is a paid add-on. Enterprise Edition or Embedded only, with a version floor of 10.11.0.cl — 26.2.0.cl for the Spotter 3 tools.
- We could not read schemas or annotations from the wire. The endpoint returns 401 to an anonymous handshake. Every annotation quoted here is from ThoughtSpot's published source, and the running server could differ from it.
Frequently asked questions
Does the ThoughtSpot Spotter MCP server respect row-level security?
Yes. ThoughtSpot documents that existing row-level and column-level security rules on tables are enforced automatically in data source responses, so an agent sees only what the signed-in user could see in ThoughtSpot itself. Creating a chart or Liveboard needs more than read access — ThoughtSpot requires data download and content creation privileges on top.
How many tools does the ThoughtSpot Spotter MCP server have?
Anthropic's directory snapshot lists five, and ThoughtSpot's own reference documents eight for the same version. The three extras are `search_objects`, `list_orgs` and `switch_org`. The count is also misleading in a second way: `send_session_message` takes a free-text question, so the real reach is whatever Spotter itself can answer, not five fixed operations.
What does the create_dashboard tool actually create in ThoughtSpot?
It creates a ThoughtSpot Liveboard from answers generated during an analysis session, and returns a dashboard identifier plus a direct link into the ThoughtSpot UI. ThoughtSpot's verification steps tell you to check that a Liveboard was added to your instance. It is a real saved object in your workspace, not a rendering local to the chat.
What does api-version=latest do on the ThoughtSpot MCP URL?
It pins your connection to whatever the newest published tool set is, rather than to a fixed one. ThoughtSpot documents date-based versioning and recommends pinning to a specific date instead, warning that new versions may change tool behaviour, input parameters or output schemas. With `latest`, that change arrives without anyone editing your client configuration.
Do I need a paid ThoughtSpot plan to use the Spotter MCP server?
Yes. ThoughtSpot documents the Spotter MCP Server as an add-on to ThoughtSpot Enterprise Edition or ThoughtSpot Embedded, and directs buyers to a sales representative. There is a version floor too: the instance must run release 10.11.0.cl or later, and 26.2.0.cl or later for the Spotter 3 tool set that the `latest` endpoint serves.
Can an agent switch between ThoughtSpot Orgs mid-conversation?
Yes, on OAuth connections to Org-enabled instances. ThoughtSpot documents `list_orgs` to enumerate reachable Orgs and `switch_org` to change the active one without re-authenticating. The switch is durable: ThoughtSpot states it persists across all your active sessions and resets only on re-authentication or prolonged inactivity, which is broader than a single chat.
Why does the ThoughtSpot MCP server return 401 to my client?
The endpoint is OAuth-gated and rejects every unauthenticated request. We confirmed this on 2026-08-19: an anonymous handshake returned HTTP 401 with a Bearer challenge. ThoughtSpot's troubleshooting adds three other causes for a 401 or 403 — a misconfigured endpoint or host, an expired user session, and insufficient privileges to view data or create content.
Sources
- ThoughtSpot Spotter MCP Server integration — https://developers.thoughtspot.com/docs/mcp-integration (fetched 2026-08-19; the directory's
documentationURL adds a#_add_mcp_server_to_the_mcp_clients_configfragment that no longer exists on the page) · retrieved 2026-08-19 - MCP tool reference (Spotter 3) — https://developers.thoughtspot.com/docs/mcp-tool-reference-spotter3 (fetched 2026-08-19 as Markdown via the
.mdsuffix) · retrieved 2026-08-19 - MCP tool reference (legacy version) — https://developers.thoughtspot.com/docs/mcp-tool-reference-legacy (fetched 2026-08-19) · retrieved 2026-08-19
- MCP Server with Spotter 3 capabilities — https://developers.thoughtspot.com/docs/mcp-server-spotter3 (fetched 2026-08-19) · retrieved 2026-08-19
- Legacy MCP Server architecture and tools — https://developers.thoughtspot.com/docs/mcp-server-legacy (fetched 2026-08-19) · retrieved 2026-08-19
- Connecting MCP Server to clients — https://developers.thoughtspot.com/docs/connect-mcp-server-to-clients (fetched 2026-08-19) · retrieved 2026-08-19
- Integrating MCP Server in a custom application or chatbot — https://developers.thoughtspot.com/docs/custom-chatbot-integration-mcp (fetched 2026-08-19) · retrieved 2026-08-19
- ThoughtSpot Spotter MCP Server changelog — https://developers.thoughtspot.com/docs/mcp-server-changelog (fetched 2026-08-19) · retrieved 2026-08-19
- ThoughtSpot developer docs machine index — https://developers.thoughtspot.com/docs/llms.txt (fetched 2026-08-19).
developers.thoughtspot.com/robots.txtreturns 404, so no crawl policy and noContent-Signalaxes are published;agent.thoughtspot.app/robots.txtalso returns 404 · retrieved 2026-08-19 - ThoughtSpot MCP Server source, tool definitions and annotations — https://github.com/thoughtspot/mcp-server/blob/main/src/servers/tool-definitions.ts (fetched 2026-08-19) · retrieved 2026-08-19
- ThoughtSpot MCP Server source, version registry — https://github.com/thoughtspot/mcp-server/blob/main/src/servers/version-registry.ts (fetched 2026-08-19) · retrieved 2026-08-19
- Live anonymous probe — 2026-08-19:
POSTtohttps://agent.thoughtspot.app/mcp?api-version=latestreturns HTTP 401 withwww-authenticate: Bearer realm="OAuth", error="invalid_token"· retrieved 2026-08-19 - Live RFC 9728 check — all three protected-resource path forms probed 2026-08-19: root and path-append return 404, path-insert returns the endpoint's 401 challenge. No descriptor is published · retrieved 2026-08-19
- Live RFC 8414 authorization-server metadata — https://agent.thoughtspot.app/.well-known/oauth-authorization-server (fetched 2026-08-19; no
scopes_supportedfield) · retrieved 2026-08-19 - Anthropic connector directory — https://claude.ai/directory/576048a9-f4be-43c6-8cdb-787897c49b03 (snapshot 2026-08-16) · retrieved 2026-08-16
- ThoughtSpot support — mailto:helpdesk@thoughtspot.com · Privacy — https://www.thoughtspot.com/privacy-statement
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Data & Research
- Developer
- ThoughtSpot Spotter
- Tools
- 5
- Domain
- agent.thoughtspot.app
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.