ThoughtSpot MCP server
Commit Nov 14, 2026Connects an AI client to a ThoughtSpot instance so it can query live business data and return answers.
Also known as thoughtspot/mcp-server
- Stars
- 35
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.0.1
- Last commit
- Nov 14, 2026
- License
- —
What is ThoughtSpot MCP?
ThoughtSpot connects an AI client to a ThoughtSpot instance so it can query live business data and return answers.
Summary generated from the project's README
About ThoughtSpot MCP server
Querying live business data from a ThoughtSpot instance through an AI client is what this server enables. It provides a bridge for users of ChatGPT or Claude to retrieve real-time answers directly from their proprietary datasets. The server handles secure authentication and connects to specific ThoughtSpot environments to pull relevant information.
Developers can set up the connection using manual client registration, which requires an OAuth Client Id and OAuth Client Secret. For those managing multiple domains, the server supports restricting access to specific instances via the INSTANCE_ALLOWLIST_BY_HOST environment variable. This ensures that only approved ThoughtSpot URLs are accessible through designated hostnames.
Local development requires setting up environment variables like the ThoughtSpot instance URL and an access token. The server architecture is built to support versioned tool definitions, allowing for the controlled rollout of new capabilities through a version registry.
What you can do with it
- 1Retrieve live business answersAsk an AI client to pull real-time data insights from your company's ThoughtSpot environment.
- 2Connect AI clients to dataIntegrate ThoughtSpot with platforms like Claude or ChatGPT using OAuth credentials.
- 3Restrict data access by domainLimit which ThoughtSpot instances can be accessed when serving multiple custom domains.
Written from the project's README. Every use case is checked against a quote from it.
How to install ThoughtSpot MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall ThoughtSpot MCP in Claude Code
$ claude mcp add --transport http mcp-server https://agent.thoughtspot.app/mcpInstall ThoughtSpot MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"url": "https://agent.thoughtspot.app/mcp"
}
}
}Install ThoughtSpot MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp-server": {
"type": "http",
"url": "https://agent.thoughtspot.app/mcp"
}
}
}Install ThoughtSpot MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp-server","type":"http","url":"https://agent.thoughtspot.app/mcp"}'Install ThoughtSpot MCP in Codex
$ codex mcp add mcp-server --url https://agent.thoughtspot.app/mcpInstall ThoughtSpot MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-server] url = "https://agent.thoughtspot.app/mcp"
Install ThoughtSpot MCP in Gemini CLI
$ gemini mcp add -s user --transport http mcp-server https://agent.thoughtspot.app/mcpInstall ThoughtSpot MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server": {
"url": "https://agent.thoughtspot.app/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablethoughtspot/mcp-server is public and reachablegithub.com/thoughtspot/mcp-server ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-13github.com/thoughtspot/mcp-server ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubThoughtSpot MCP Server
ThoughtSpot Spotter MCP Server provides a set of tools for querying and retrieving relevant data from your ThoughtSpot instance. Spotter connects to your ThoughtSpot instance, handles authentication securely, and returns live answers from your own data.
- ThoughtSpot Spotter MCP Server documentation
- Create a free ThoughtSpot account
- What is ThoughtSpot?
- Get support on Discord
- Privacy statement
Table of Contents
Manual client registration
For MCP hosts which do not(yet) support Dynamic client registration, or they require statically adding Oauth Client Id etc. Go to this page, to register a new client and copy the details over. The most relevant values are Oauth Client Id and Oauth Client Secret which should be added when adding ThoughtSpot as an MCP connector in the MCP client (ChatGPT/Claude etc). The generated client details are only available when they are generated and are NOT available later for reference.
Associate with a ThoughtSpot instance
Manual client registration also allows to associate with a specific ThoughtSpot instance, so that your users do not have to enter the Thoughtspot instance URL when doing the authorization flow. While registering the Oauth client add ThoughtSpot URL to the appropriate value.
Restrict instances per domain
When the Worker serves several custom domains, you can limit which ThoughtSpot instances each domain accepts with the INSTANCE_ALLOWLIST_BY_HOST environment variable. Its value is a JSON object that maps a hostname to its allowed instance URLs:
{"mcp.example.com": ["https://instance-a.thoughtspot.cloud", "https://instance-b.thoughtspot.cloud"]}
On a listed hostname:
- The authorization page shows a dropdown of the allowed instances instead of a free-text field.
POST /authorizerejects any other instance with a 400.- MCP requests (
/mcp,/sse,/token/*,/bearer/*) for any other instance get a 403.
Hostnames that aren't listed behave as before. If the value is not valid JSON, the server rejects requests with a 500 instead of lifting the restriction.
Contributing
Local Development
- Install dependencies:
npm install - Set up environment variables:
- Copy
.dev.varsand fill in your ThoughtSpot instance URL and access token. - To test OAuth over plain HTTP on a host other than
localhost(for example a hosts-file alias likehttp://myserver.com:8787), also addOAUTH_ALLOW_INSECURE_DEV_COOKIE=true. Browsers otherwise drop the OAuth binding cookie on such hosts and the flow fails with a 403. Never set this in a deployed environment.
- Copy
- Start the development server:
npm run dev
Adding New Tools
When adding new MCP tools to the server:
- Define schemas and tools in
src/servers/tool-definitions.ts - Implement handlers in
src/servers/mcp-server.ts - Update version registry in
src/servers/version-registry.ts:- Add new tools to appropriate version(s) in
VERSION_REGISTRY - For new stable features, update
DEFAULT_VERSION - For beta features, add to the
betaversion entry
- Add new tools to appropriate version(s) in
- Add tests for new tools and version configurations
- Update documentation in README.md
Important: The version registry controls which tools are available in each API version. Make sure to add new tools to the correct version configuration to ensure they're accessible to users.
MCP Server, © ThoughtSpot, Inc. 2026
ThoughtSpot MCP questions
How do I add ThoughtSpot MCP to Claude Code?
Run claude mcp add --transport http mcp-server https://agent.thoughtspot.app/mcp in your terminal. Add --scope user to make it available in every project.
How do I add ThoughtSpot MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How does the ThoughtSpot MCP server handle authentication?
It uses OAuth to connect to your ThoughtSpot instance and handles authentication securely. Clients without dynamic registration can register a client manually and supply the OAuth client ID and secret.
What can I do with the ThoughtSpot MCP server?
It provides tools for querying and retrieving relevant data from your ThoughtSpot instance. Answers come from your own live data.
Can I associate the MCP client with a specific ThoughtSpot instance?
Yes. Manual client registration lets you set the ThoughtSpot URL so users don't have to enter the instance URL during authorization.
How do I register the ThoughtSpot MCP server manually?
Go to the ThoughtSpot clients page, register a new client, and copy the OAuth Client Id and Client Secret into your MCP client. The details are shown only once.