LLMs.txt: Complete documentation index for AI agents
MCP Server with Spotter 3 capabilities

MCP Server with Spotter 3 capabilities

ThoughtSpot Spotter MCP Server supports Spotter 3, which enables advanced analytics, forecasting, multi-step reasoning and analysis, and deep research capabilities. The MCP Server with Spotter 3 introduces new MCP tools, real-time streaming responses, session-based conversations, and richer interactions.

Legacy MCP Server setupMCP Server with Spotter 3

Functional differences

Limited capabilities for complex analysis and context integration.

  • Supports advanced analytics, forecasting, and deep research capabilities.

  • Supports asynchronous streaming, session-based conversations, and context integration.

Recommended for

Maintaining existing integrations only.

All new integrations

Integration pattern
Session model
Response processing

Synchronous and stateless integration pattern. Each tool call is independent. Does not support persistent sessions and requires prior context to be injected manually on every follow-up call.

Asynchronous and stateful sessions. Allows multiple follow-up questions within a session. Responses are streamed with intermediate updates, including thinking narration and clarifications. Context is retained automatically across all follow-up questions within the session.

Data source selection

Requires a separate tool call (getDataSourceSuggestions) to retrieve source suggestions.

Built into session creation. If the data_source_id is not explicitly specified in the query, the most relevant source is automatically selected based on the user’s query.

Response delivery

Returns full response in a single synchronous call.

Responses are streamed incrementally; updates are accumulated via polling.

Follow-up questions

Requires prior context on every follow-up call.

The session retains context automatically.
Optionally, the additional_context parameter can be included to inject new external context for each follow-up question or message.

API versioning support

Not available.

Supports date-based API versioning, which is identified in the MCP Server URL as ?api-version=YYYY-MM-DD.

The following figure illustrates the MCP architecture, tool calls, and workflow in the new MCP Server version:

MCP architecture new

Tool calls and workflow processing🔗

The workflow in the MCP Server with Spotter 3 typically includes the following stages:

  1. User asks a question
    A user sends a query in the chat interface to get data insights. For example, What were the total sales of Jackets and Bags in the Northeast last year?

  2. Agent calls create_analysis_session
    The agent calls create_analysis_session to establish a stateful analytical session with ThoughtSpot’s Spotter 3 engine. ThoughtSpot returns an analytical_session_id that identifies the session for all subsequent calls.
    If the user specified a data source, the agent passes it as the optional data_source_id parameter. If not specified, ThoughtSpot automatically selects the most relevant data source based on the question.

  3. Agent calls send_session_message
    The agent calls send_session_message with the analytical_session_id and the user’s question. Optionally, the agent can pass additional_context to provide external information that should influence the analysis. For example, The user’s fiscal year starts in April or The user is a manager of the West region.
    ThoughtSpot confirms receipt with a success response and begins processing the question asynchronously. The answer is not returned in this call.

  4. Agent polls get_session_updates for results
    The agent calls get_session_updates repeatedly in a loop until is_done is true. ThoughtSpot streams updates incrementally across multiple polls. The agent must accumulate updates from every poll.

  1. User generates a dashboard with the results (optional)
    The user can choose to save answers from the conversation as a ThoughtSpot dashboard. For this workflow, the agent extracts the answer_id and answer_title from each answer type update collected during polling and calls create_dashboard. The agent passes each answer_title as the title of the answer, and can add instructions for layout and style.
    SpotterViz, the ThoughtSpot dashboard designer, organizes and styles the charts and saves them as a dashboard. If the dashboard is not ready, create_dashboard returns status: "in_progress" and a task_id, and the agent polls get_dashboard_status until the status changes. When the status is completed, the response contains the dashboard_id and the dashboard_url, a direct link to the dashboard in the ThoughtSpot UI. For more information, see create_dashboard.

The other optional tool calls include:

  • User asks a follow-up question (optional)
    The user can ask a follow-up question in the same session. The agent calls send_session_message again using the same analytical_session_id. ThoughtSpot retains the full conversation context automatically. The agent returns to step 4 to poll for the follow-up response.

  • User switches to a different Org (optional)
    If the user belongs to more than one Org and connects over OAuth, the agent calls list_orgs to return all accessible Orgs and flags the Org that the user is currently logged in. When the user requests a switch, the agent calls switch_org with the target org_id. For more information, see Org switching tools.

  • Agent searches for existing content (optional)
    If the user refers to content that already exists, for example, "open the regional sales Liveboard", the agent calls search_objects with a search term and optional filters such as object type, author, tag, or verified status. search_objects returns a ranked list of matching objects with their metadata and deep links.

  • Agent reads the data behind existing content (optional)
    After search_objects returns an Answer or Liveboard, the agent can call get_data with the object_id from the result, and the result’s type as object_type, to fetch the columns and rows that the object shows. For a single visualization on a Liveboard, the agent passes the visualization_id in visualization_ids. The agent answers from the returned rows, which reflect the latest data. get_data is available only to users who have the privilege to download data. For more information, see get_data.

  • User asks for a dashboard from a description (optional)
    If the user asks for a dashboard before any analysis, or wants one recreated from another tool, the agent calls create_dashboard with instructions and no answers. SpotterViz returns status: "needs_input" with the data source it chose and its plan. The agent shows the plan to the user. After the user confirms or asks for changes, the agent calls create_dashboard again with the same task_id and the user’s reply in instructions.

  • User changes an existing dashboard (optional)
    The agent finds the dashboard GUID with search_objects, and calls modify_dashboard with the dashboard_id and the user’s change in instructions. If SpotterViz asks a question, the agent shows it to the user and calls modify_dashboard again with the same dashboard_id and task_id. For more information, see modify_dashboard.

  • User builds or edits a data model (optional)
    The agent calls create_model_session with a connection GUID for a new model, or a model GUID to edit one. The agent sends instructions with send_model_message and polls get_model_updates until is_done is true. The builder proposes a plan first, and the agent shows it to the user and waits for approval. To save, the agent calls finalize_model for a summary, and then calls it again with confirm: true after the user approves. The model builder tools are available only to users who can create or edit data models. For more information, see Model builder tools.

Additional resources🔗

© 2026 ThoughtSpot Inc. All Rights Reserved.