@thoughtspot/mcp-server

ThoughtSpot MCP Server

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.

If you do not have a Thoughtspot account, create one for free here.

Learn more about ThoughtSpot.

Join our Discord to get support.

Table of Contents

• MCP Client Configuration
• Features
  • Supported transports
• Contributing
  • Local Development
  • Endpoints
• Configuration
• Stdio support (fallback)
  • How to obtain a TS_AUTH_TOKEN
• Troubleshooting

MCP Client Configuration

To configure this MCP server in your MCP client (such as Claude Desktop, Windsurf, Cursor, etc.), add the following configuration to your MCP client settings:

{
  "mcpServers": {
    "ThoughtSpot": {
      "command": "npx",
      "args": [
         "mcp-remote",
         "https://agent.thoughtspot.app/sse"
      ]
    }
  }
}

See the Troubleshooting section for any errors.

Features

• OAuth Authentication: Access your data, as yourself.
• Tools:
  • 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.
  • createLiveboard: Create a liveboard from a list of answers.
• MCP Resources:
  • datasources: List of ThoughtSpot Data models the user has access to.

Supported transports

• SSE /sse
• Streamed HTTP /mcp

Contributing

Local Development

• Install dependencies:

  npm install
  

• Set up environment variables:
  • Copy .dev.vars and fill in your ThoughtSpot instance URL and access token.
• Start the development server:

  npm run dev
  

Endpoints

• /mcp: MCP HTTP Streaming endpoint
• /sse: Server-sent events for MCP
• /api: MCP tools exposed as HTTP endpoints
• /authorize, /token, /register: OAuth endpoints

Configuration

• wrangler.jsonc: Configure bindings, secrets, and compatibility.

Stdio support (fallback)

If you are unable to use the remote MCP server due to connectivity restrictions on your Thoughtspot instance. You could use the stdio local transport using the npm package.

Here is how to configure stdio with MCP Client:

{
  "mcpServers": {
    "ThoughtSpot": {
      "command": "npx",
      "args": [
         "@thoughtspot/mcp-server"
      ],
      "env": {
         "TS_INSTANCE": "<your Thoughtspot Instance URL>",
         "TS_AUTH_TOKEN": "<ThoughtSpot Access Token>"
      }
    }
  }
}

How to obtain a TS_AUTH_TOKEN ?

• Go to ThoughtSpot => Develop => Rest Playground v2.0
• Authentication => Get Full access token
• Scroll down and expand the "body"
• Add your "username" and "password".
• Put whatever "validity_time" you want the token to be.
• Click on "Try it out" on the bottom right.
• You should get a token in the response, thats the bearer token.

Alternative way to get TS_AUTH_TOKEN

• Login to the ThoughtSpot instance as you would normally.
• Opem in a new tab this URL:
  • https://your-ts-instance/api/rest/2.0/auth/session/token
• You will see a JSON response, copy the "token" value (without the quotes).
• This is the token you could use.

Troubleshooting

Oauth errors due to CORS/SAML.

Make sure to add the following entries in your ThoughtSpot instance:

CORS

• Go to ThoughtSpot => Develop => Security settings
• Click "Edit"
• Add "agent.thoughtspot.app" to the the "CORS whitelisted domains".

SAML (need to be Admin)

• Go to ThoughtSpot => Develop
• Go to "All Orgs" Tab on the left panel if there is one.
• Click "Security settings"
• Click "Edit"
• Add "agent.thoughtspot.app" to the the "SAML redirect domains".

MCP Server, © ThoughtSpot, Inc. 2025