Integrate your tools into Spotter via Connectors

In addition to bringing Spotter into other platforms, you can now integrate connectors to Spotter to make connections to wherever your data is stored. This allows you to do things like search Confluence or Snowflake for unstructured data to add to your analysis, or send direct messages from Spotter to Slack with your data. By connecting your third-party ecosystem (Slack, Jira, Confluence, Snowflake, Glean) directly to ThoughtSpot, you can transition from insight to execution without needing to switch tabs.

Understanding the MCP architecture

ThoughtSpot’s integration works as a two-way street. Understanding these roles is crucial for proper configuration.

  • Spotter as an MCP Host (Inbound):

    • ThoughtSpot acts as the primary interface. It hosts external tools. When you ask a question about a Slack thread or a Jira ticket, Spotter reaches out to those services to pull data in or push actions out.

  • ThoughtSpot as an MCP Server (Outbound):

    • ThoughtSpot acts as a data provider for other AI agents (like Claude or custom internal bots). These agents can “call” ThoughtSpot analytics to answer questions elsewhere in your organization. For more information, see MCP server integration.

Configuration guide

Administrators must whitelist and configure connectors before they are available to end-users.

Spotter as an MCP host is only available with Spotter 3 and must be enabled separately. Once enabled, any MCP tools enabled by the admin will be available to all users of Spotter. Each user must enable the tools for themselves from the Spotter prompt bar and authenticate.

Enable Spotter 3.0 capabilities

  1. Navigate to Admin settings > ThoughtSpot AI.

  2. In the Spotter 3 capabilities section, click Edit.

  3. Ensure Enable Connectors/MCP is set to Enabled.

  4. Click Save. Note that this may cause a brief service interruption.

Register a new connector

  1. Navigate to Admin settings > ThoughtSpot AI. Scroll to the Spotter Connectors section and click Edit.

  2. You can enable a connector from the pre-defined list or Add custom connector.

  3. When adding a connector from the pre-defined list, simply click Add.

  4. When adding a custom connector, you must provide the following details:

    • Connector Display Name: The name users will see within Spotter (for example, “Engineering Jira”).

    • MCP URL: The specific endpoint where your MCP-compliant server is hosted.

    • Authentication:

      • None

      • OAuth: Required for most enterprise apps such as Slack or Jira. You must enter the Client ID and Client Secret.

      • Bearer: Used for token-based access.

When adding a custom connector and using the OAuth authentication method, you must whitelist ThoughtSpot’s callback URL: https://oauth.thoughtspot.app/callback.

Security and privacy

  • Enterprise-Grade OAuth: Your third-party credentials are never stored by ThoughtSpot. We use secure tokens to communicate with your apps.

  • Role-Based Access: Spotter can only "see" what you have permission to see. If you don’t have access to a private Slack channel, Spotter cannot pull data from it for you.

  • Audit Logs: Admin settings allow for the monitoring of tool usage and connector health.

Was this page helpful?
×