Adobe Customer Journey Analytics
Run cross-channel reports and build segments in Adobe Customer Journey Analytics.
Ask your governed analytics a question in plain language, get a chart back.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The ThoughtSpot Spotter MCP server puts a company's governed analytics behind a chat prompt. Ask Claude, ChatGPT or any MCP-compatible agent a question about your data and it opens a session with ThoughtSpot's Spotter engine, which picks a data model, runs the query and returns a chart. Saving that chart creates a real Liveboard in your ThoughtSpot instance.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
search_objects, list_orgs and switch_org are documented for this version and absent from Anthropic's 2026-08-16 snapshot. Read the vendor's tool reference, not the listing.send_session_message accepts free text, so what the connector can reach is whatever Spotter can answer.scopes_supported in the RFC 8414 document, so there is no machine-readable grant to review or narrow.?api-version=latest accepts changes silently. ThoughtSpot warns that new versions may alter tool behaviour, input parameters and output schemas, and recommends pinning a date instead./mcp path currently serves the legacy tools. ThoughtSpot documents it as the baseline version today and says it will move later — so the same host serves two different tool sets depending on the query string.list_orgs and switch_org to OAuth connections on Org-enabled instances, and its code removes them from the tool list otherwise.Yes. ThoughtSpot documents that existing row-level and column-level security rules on tables are enforced automatically in data source responses, so an agent sees only what the signed-in user could see in ThoughtSpot itself. Creating a chart or Liveboard needs more than read access — ThoughtSpot requires data download and content creation privileges on top.
Anthropic's directory snapshot lists five, and ThoughtSpot's own reference documents eight for the same version. The three extras are `search_objects`, `list_orgs` and `switch_org`. The count is also misleading in a second way: `send_session_message` takes a free-text question, so the real reach is whatever Spotter itself can answer, not five fixed operations.
It creates a ThoughtSpot Liveboard from answers generated during an analysis session, and returns a dashboard identifier plus a direct link into the ThoughtSpot UI. ThoughtSpot's verification steps tell you to check that a Liveboard was added to your instance. It is a real saved object in your workspace, not a rendering local to the chat.
It pins your connection to whatever the newest published tool set is, rather than to a fixed one. ThoughtSpot documents date-based versioning and recommends pinning to a specific date instead, warning that new versions may change tool behaviour, input parameters or output schemas. With `latest`, that change arrives without anyone editing your client configuration.
Yes. ThoughtSpot documents the Spotter MCP Server as an add-on to ThoughtSpot Enterprise Edition or ThoughtSpot Embedded, and directs buyers to a sales representative. There is a version floor too: the instance must run release 10.11.0.cl or later, and 26.2.0.cl or later for the Spotter 3 tool set that the `latest` endpoint serves.
Yes, on OAuth connections to Org-enabled instances. ThoughtSpot documents `list_orgs` to enumerate reachable Orgs and `switch_org` to change the active one without re-authenticating. The switch is durable: ThoughtSpot states it persists across all your active sessions and resets only on re-authentication or prolonged inactivity, which is broader than a single chat.
The endpoint is OAuth-gated and rejects every unauthenticated request. We confirmed this on 2026-08-19: an anonymous handshake returned HTTP 401 with a Bearer challenge. ThoughtSpot's troubleshooting adds three other causes for a 401 or 403 — a misconfigured endpoint or host, an expired user session, and insufficient privileges to view data or create content.
documentation URL adds a #_add_mcp_server_to_the_mcp_clients_config fragment that no longer exists on the page) · retrieved 2026-08-19.md suffix) · retrieved 2026-08-19developers.thoughtspot.com/robots.txt returns 404, so no crawl policy and no Content-Signal axes are published; agent.thoughtspot.app/robots.txt also returns 404 · retrieved 2026-08-19POST to https://agent.thoughtspot.app/mcp?api-version=latest returns HTTP 401 with www-authenticate: Bearer realm="OAuth", error="invalid_token" · retrieved 2026-08-19scopes_supported field) · retrieved 2026-08-19Connect ThoughtSpot Spotter once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.