ThoughtSpot MCP Server

The ThoughtSpot MCP Server. The thoughtspot mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.

What it actually does

The ThoughtSpot MCP Server provides secure OAuth-based authentication and a set of tools for querying and retrieving relevant data from your ThoughtSpot instance. It's a remote server hosted on Cloudflare.

• OAuth Authentication — Access your data, as yourself
• Dynamic Client Registration (DCR) support
• Any MCP host is allowed. Let's make the world fact driven
• ping: Test connectivity and authentication
• getRelevantQuestions: Get relevant data questions from ThoughtSpot analytics based on a user query
• getAnswer: Get the answer to a specific question from ThoughtSpot analytics

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• Troubleshooting — Make sure to add the following entries in your ThoughtSpot instance:
• Endpoints — The ThoughtSpot MCP Server supports API versioning to access different tool sets. You can specify the version using the api-version query parameter

Configuration

You will need 3 environment variables: TS_AUTH_TOKEN, OPENAI_API_KEY, ANTHROPIC_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the thoughtspot mcp server does with a few real requests.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. ThoughtSpot's toolset — Troubleshooting, Endpoints — is a fair guide to whether it matches your workflow. It is maintained by thoughtspot; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against ThoughtSpot's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.