Integrate SpotterCode with your IDE

Table of Contents

Before you begin
Authentication
- OAuth and SAML authentication
- Bearer token authentication
Integrate SpotterCode with Cursor
- Using one-click installation
- Using the mcp.json file
Integrate SpotterCode with Claude
Integrate SpotterCode with Visual Studio Code
- Configuring MCP Server endpoint for documentation retrieval only
Verify the integration
Additional resources

This guide walks you through the process of adding SpotterCode to your AI-native IDE.

Before you begin🔗

Ensure that your IDE is AI-native and supports chat sessions with AI models.
Ensure that you have the necessary permissions to configure Model Context Protocol (MCP) servers in your IDE.
Ensure that the latest version of Node.js is installed in your environment. This is required for building embedding code with the SDK.
Ensure that you have access to a ThoughtSpot instance and can view the objects and resources that you want to embed or access via the REST API.

Authentication🔗

Starting with August 2026, the SpotterCode MCP Server endpoint requires you to authenticate with a ThoughtSpot instance. This allows SpotterCode to perform authenticated user operations using ThoughtSpot REST APIs.

SpotterCode supports two authentication mechanisms:

OAuth and SAML authentication
Bearer token authentication

OAuth and SAML authentication🔗

This is the primary authentication flow for developers connecting an MCP client interactively.

When your MCP client connects to the https://spottercode.thoughtspot.app/mcp endpoint for the first time, a dialog appears requesting your ThoughtSpot instance URL.
Enter your ThoughtSpot instance URL (for example, https://your-org.thoughtspot.cloud).
You are redirected to the ThoughtSpot SAML login flow for your instance.
After successful login, SpotterCode obtains a bearer token for your session and stores the session information securely.
Subsequent MCP requests from your IDE agent use the session token automatically and you will not be prompted to log in again until the session expires.

Note	The session token is stored in a secure backend store. Contact your ThoughtSpot administrator if you encounter repeated authentication prompts.

Bearer token authentication🔗

For programmatic or CI/CD scenarios where an MCP client cannot perform an interactive login, SpotterCode accepts a bearer token directly using a dedicated MCP Server endpoint: https://spottercode.thoughtspot.app/bearer/mcp.

In your MCP client configuration, pass the following headers:

Authorization: Bearer <token>, where <token> is a valid ThoughtSpot bearer token obtained from the ThoughtSpot REST API.
x-ts-host: <host>, where <host> is the full URL of your ThoughtSpot instance (for example, https://your-org.thoughtspot.cloud).

SpotterCode extracts and validates the token and host from these headers, then injects the authentication context into each MCP tool request.

For example, to add SpotterCode to Claude Code using the bearer token endpoint:

claude mcp add --transport http SpotterCode \
  https://spottercode.thoughtspot.app/bearer/mcp \
  -H "Authorization: Bearer <token>" \
  -H "x-ts-host: https://your-org.thoughtspot.cloud"

Note	To obtain a bearer token, use the ThoughtSpot REST API v2 authentication endpoints or trusted authentication. For more information, see Trusted authentication.

Integrate SpotterCode with Cursor🔗

You can add the SpotterCode MCP Server URL to Cursor using the one-click installation link or the mcp.json file.

Using one-click installation🔗

Via Cursor Marketplace

SpotterCode is available as an official plugin in the Cursor Marketplace. To install SpotterCode from the Cursor Marketplace:

Go to Cursor Marketplace.
Ensure that you are signed in, and then click Add to Cursor → Add Plugin.
To view the plugin in Cursor, click View in Editor.

Via installation link

Copy the following link and open it in Cursor:

cursor://anysphere.cursor-deeplink/mcp/install?name=SpotterCode&config=eyJ1cmwiOiJodHRwczovL3Nwb3R0ZXJjb2RlLnRob3VnaHRzcG90LmFwcC9tY3AifQ==
Cursor opens the MCP server installation page to add SpotterCode.
Click Install.

Using the mcp.json file🔗

Cursor also allows you to integrate SpotterCode by adding the MCP server URL in the mcp.json file. To add the URL:

Go to Cursor Settings > Tools and MCP. Cursor opens the mcp.json file.

Add the SpotterCode MCP Server URL as a remote MCP server.

{
  "mcpServers": {
    "SpotterCode": {
      "url": "https://spottercode.thoughtspot.app/mcp"
    }
  }
}

Click Save and close the mcp.json file.
In Cursor Settings > Tools and MCP, click Connect. You will be prompted to provide the URL of your ThoughtSpot instance and complete authentication. If the authentication is successful, the SpotterCode MCP server makes its tools available for AI models in Cursor.

Integrate SpotterCode with Claude🔗

If your Claude account includes access to Claude AI (web chat), you can add SpotterCode as a remote MCP connector. Connectors added in Claude AI automatically sync to Claude Code without any additional configuration.

For the Claude Code-only setup, you must manually point Claude Code to the SpotterCode MCP server via CLI.

Claude AI integration🔗

To add SpotterCode as a custom connector:

Go to Customize > Connectors
Click the + icon and select Add custom connector.
Enter the SpotterCode MCP server URL.
Click Add.
When prompted for authentication, specify the URL of your ThoughtSpot instance and complete authentication.

Claude Code-only setup🔗

To enable SpotterCode in Claude Code, add the MCP server URL using the following claude mcp add command in the Claude Code CLI.

claude mcp add --transport http SpotterCode https://spottercode.thoughtspot.app/mcp

When prompted for authentication, specify the URL of your ThoughtSpot instance and complete authentication.

Claude Desktop integration🔗

If you are using Claude Desktop, add the URL directly to the Claude configuration JSON file:

{
  "mcpServers": {
    "SpotterCode": {
      "url": "https://spottercode.thoughtspot.app/mcp"
    }
  }
}

When prompted for authentication, specify the URL of your ThoughtSpot instance and complete authentication.

Claude Cowork integration🔗

If you are using Claude Cowork with Claude AI or Claude Desktop, verify whether the SpotterCode MCP connector is enabled for Claude Cowork. If it’s not enabled, add the SpotterCode MCP server:

Open Claude Cowork in either Claude AI or the Claude Desktop app.
Navigate to Settings > Connectors > Customize.
If SpotterCode is already available in your organization’s list of connectors, select the SpotterCode connector. If it’s not available:
1. Click the + icon and select Add custom connector.
2. Add the SpotterCode MCP server URL: https://spottercode.thoughtspot.app/mcp.
When prompted for authentication, specify the URL of your ThoughtSpot instance and complete authentication.

Integrate SpotterCode with Visual Studio Code🔗

Although you can configure the MCP server in Visual Studio Code, to start a chat session with the AI agent, you’ll need GitHub Copilot or a similar extension.

To add the SpotterCode MCP Server to Visual Studio Code, use the Extensions view or the MCP: Add Server command via the Command Palette. Alternatively, directly edit the mcp.json file in your workspace configuration.

{
  "servers": {
    "SpotterCode": {
      "url": "https://spottercode.thoughtspot.app/mcp",
      "type": "http"
    }
  }
}

When prompted for authentication, specify the URL of your ThoughtSpot instance and complete authentication.

After you add the MCP server URL, the SpotterCode MCP server is available in the Extensions view.

Configuring MCP Server endpoint for documentation retrieval only🔗

If you only need documentation and REST API reference retrieval, use the following unauthenticated MCP Server URL: https://spottercode.thoughtspot.app/mcp/docs.

This endpoint provides access to the get-rest-api-reference and get-developer-docs-reference skills only. The run-ts-workflow skill is not available through this endpoint.

To use this endpoint in your IDE, replace the authenticated MCP server URL in your configuration:

For Cursor (mcp.json)

{
  "mcpServers": {
    "SpotterCode": {
      "url": "https://spottercode.thoughtspot.app/mcp/docs"
    }
  }
}

For Claude Code (CLI)

claude mcp add --transport http SpotterCode https://spottercode.thoughtspot.app/mcp/docs

For Visual Studio Code (mcp.json)

{
  "servers": {
    "SpotterCode": {
      "url": "https://spottercode.thoughtspot.app/mcp/docs",
      "type": "http"
    }
  }
}

Verify the integration🔗

To verify the integration:

Open your application project in your IDE.

If the integration is successful, you’ll see SpotterCode in the MCP servers list.
Verify the available SpotterCode skills.

Initiate a chat session and ask a question related to ThoughtSpot embedding, REST APIs, or the SDKs.

In the following example, a chat session with Cursor AI is initiated with the prompt, "I want to embed a ThoughtSpot Liveboard in my React application. Use the available tools to get this information and generate the embed code". Notice how the AI agent uses the SpotterCode skills to get the required information:
Verify that the AI agent is able to discover SpotterCode skills and is using these skills to generate a response.
Review the response returned for your prompt and verify the results.

The following example shows how Cursor AI scaffolds the embed code using the SpotterCode skills. Notice that the AI agent identifies and lists the minimum configuration settings, such as the ThoughtSpot host URL, Liveboard ID, and authentication attributes, required to complete the embedding.
When you are prompted to provide additional information, specify these details to continue with the embedding as shown in the following example:
Try additional prompts such as adding custom styles, hiding UI menu actions, and more.

Additional resources🔗

For prompt examples, see Prompt examples and best practices.
For troubleshooting tips and workarounds, refer to the Troubleshooting section.
For more information about adding MCP servers to Claude Code, see Claude Code Documentation.
For information about configuring MCP servers in Cursor, refer to the Cursor Documentation.
For more information about configuring MCP servers in Visual Studio Code, refer to Visual Studio Code Documentation.