Thoughtspot

app.thoughtspotPublished by thoughtspot.appOfficial publisherv1.0.1Updated Nov 2, 2026

MCP Server for ThoughtSpot - provides OAuth authentication and tools for querying data

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Remote ThoughtSpot MCP server that lets an assistant query your ThoughtSpot instance and return live answers from your own data via OAuth.

What you can do
  • Query data in a connected ThoughtSpot instance and retrieve relevant results
  • Return live answers drawn from your own ThoughtSpot data
  • Authenticate through an OAuth flow against the ThoughtSpot instance you specify
  • Support manual OAuth client registration for hosts without dynamic client registration
When to use it
Use it when your organization already runs ThoughtSpot and you want an assistant to ask questions of that data and get live answers instead of static exports.
Requirements
A remote MCP endpoint reached over streamable HTTP with OAuth required; an Authorization bearer token (optionally carrying the ts-host as token@ts-host) or a separate X-TS-Host header naming your ThoughtSpot instance URL; a ThoughtSpot account and instance. Some hosts need a manually registered OAuth client ID and secret.
Before you install
The Authorization header carries a bearer token, and manual registration produces an OAuth client secret; keep both private. The generated client details are shown only once and cannot be retrieved later. Queries send your questions and instance details to ThoughtSpot's hosted service, so review its privacy statement before connecting production data.

Installation

In SourceWeft

  1. Open Thoughtspot in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.thoughtspot%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "thoughtspot": {
      "type": "http",
      "url": "https://agent.thoughtspot.app/mcp"
    }
  }
}

README

[ThoughtSpot]


ThoughtSpot MCP Server
[MCP Server] [Static Badge] [GitHub branch check runs] [Coverage Status] [Discord: ThoughtSpot]

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.

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:

json
{"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 /authorize rejects 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

  1. Install dependencies:
    sh
    npm install
  2. Set up environment variables:
    • Copy .dev.vars and 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 like http://myserver.com:8787), also add OAUTH_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.
  3. Start the development server:
    sh
    npm run dev

Adding New Tools

When adding new MCP tools to the server:

  1. Define schemas and tools in src/servers/tool-definitions.ts
  2. Implement handlers in src/servers/mcp-server.ts
  3. 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 beta version entry
  4. Add tests for new tools and version configurations
  5. 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

Source: README.md at commit 6a418e7

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.