ThoughtSpot
MCP server by ThoughtSpot
Ask questions of your ThoughtSpot data, get live answers and create Liveboards from your AI assistant.
Connect to ThoughtSpot
ThoughtSpot needs sign-in. Connect with its own URL:
Your client opens ThoughtSpot’s sign-in the first time you use it. The token stays between your client and ThoughtSpot.
Share this server
Opens this page, with the URL and setup steps.
mcp.tc/i/thoughtspotAbout
ThoughtSpot Spotter MCP Server connects an assistant to your ThoughtSpot instance. It provides tools for querying and retrieving relevant data, returns live answers from your own data, and can create Liveboards.
It runs as a hosted streamable HTTP endpoint with OAuth sign-in, where you enter your ThoughtSpot instance URL during authorization. A bearer-token variant is available using Authorization and X-TS-Host headers. It needs a ThoughtSpot instance with the MCP add-on (Enterprise Edition or Embedded). Add ?api-version=latest or ?api-version=YYYY-MM-DD to choose a tool version.
What you can do
- Ask natural-language questions of ThoughtSpot data
- Retrieve live answers from your own instance
- Create Liveboards
- Pick a tool version with the api-version query parameter
- Sign in with OAuth or use a bearer token
Tools
ThoughtSpot lists its tools only after you sign in, so we can’t show them here. Your client lists them once you’re connected.
Example prompts
Ask ThoughtSpot what our total sales were by region last quarter.
Create a Liveboard with the answers about monthly revenue.
Which products had the highest return rate this year?
Set up
Every client connects to agent.thoughtspot.app, and ThoughtSpot asks you to sign in the first time. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http thoughtspot https://agent.thoughtspot.app/mcp- Start Claude Code, type
/mcp, pick thoughtspot and choose Authenticate. A browser window opens for the ThoughtSpot sign-in.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Open Settings → Connectors and click Add custom connector.
- Name it ThoughtSpot and paste this URL:
https://agent.thoughtspot.app/mcp- Click Add, then Connect, and sign in when ThoughtSpot asks.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
claude.ai
- Open the connector form on claude.ai. This button fills in the name and URL for you:
Add to claude.ai (opens in a new tab)
- Check that the URL reads
https://agent.thoughtspot.app/mcpand click Add. - Click Connect and sign in when ThoughtSpot asks.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.
ChatGPT
- On chatgpt.com, open Settings → Security and login and turn on Developer mode.
- Go to
chatgpt.com/pluginsand click + to create an app for a remote MCP server. - Paste
https://agent.thoughtspot.app/mcpas the server URL and choose OAuth. ChatGPT sends you to ThoughtSpot to sign in.
Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"thoughtspot": {
"url": "https://agent.thoughtspot.app/mcp"
}
}
}Cursor shows Needs login next to the server. Click it to sign in.
VS Code
Install in VS Code (opens in a new tab)
Or from a terminal:
code --add-mcp '{"name":"thoughtspot","type":"http","url":"https://agent.thoughtspot.app/mcp"}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"thoughtspot": {
"type": "http",
"url": "https://agent.thoughtspot.app/mcp"
}
}
}VS Code asks you to sign in the first time the server starts.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"thoughtspot": {
"serverUrl": "https://agent.thoughtspot.app/mcp"
}
}
}- Refresh the MCP server list in Cascade and sign in when asked.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add thoughtspot --url https://agent.thoughtspot.app/mcp
codex mcp login thoughtspotOr edit ~/.codex/config.toml directly:
[mcp_servers.thoughtspot]
url = "https://agent.thoughtspot.app/mcp"Gemini CLI
gemini mcp add --transport http thoughtspot https://agent.thoughtspot.app/mcpThen, inside Gemini CLI, run /mcp auth thoughtspot to sign in.
This adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.
{
"mcpServers": {
"thoughtspot": {
"type": "http",
"url": "https://agent.thoughtspot.app/mcp"
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://agent.thoughtspot.app/mcp.
FAQ
Can I paste mcp.tc/i/thoughtspot into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://agent.thoughtspot.app/mcp, so your client talks to ThoughtSpot directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.
Does ThoughtSpot need an API key or a sign-in?
Yes, you need a ThoughtSpot account. The first time your client connects, it opens ThoughtSpot’s sign-in page. The token goes straight to the server’s own URL, never through mcp.tc.
Is ThoughtSpot a remote or a local server?
Remote. ThoughtSpot hosts it at https://agent.thoughtspot.app/mcp, and it speaks Streamable HTTP. There’s nothing to install.
What can ThoughtSpot do?
You can ask natural-language questions of ThoughtSpot data, retrieve live answers from your own instance and create Liveboards.
Which clients can use it?
Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.
Who wrote this page?
mcp.tc’s robot read ThoughtSpot’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
Embed
Show ThoughtSpot in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work
README badge
[](https://mcp.tc/i/thoughtspot)<a href="https://mcp.tc/i/thoughtspot"><img src="https://mcp.tc/i/thoughtspot/badge.svg" alt="ThoughtSpot on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/thoughtspot.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/thoughtspot" title="ThoughtSpot on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/thoughtspot.jsonmcp.tc isn’t affiliated with ThoughtSpot. This page was built from ThoughtSpot’s public metadata, last checked on 3 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.