Skip to main content
Tableau The Tableau connector exposes the full Tableau platform (REST API 3.x, Metadata GraphQL, VizQL Data Service and Pulse) to your Prisme.ai workspaces. It can be consumed two ways: as a remote MCP server that Agent Creator agents call as tools, or as a Builder app whose instructions (Tableau.<operation>) you call directly from DSUL. It runs in the tenant app-instance context: you install the app in your own workspace, which stores the Tableau credential. You enter the server and a Tableau Personal Access Token (PAT) in the connector’s Configuration app; the connector exchanges it server-side for a short-lived X-Tableau-Auth session token, so credentials are never exposed to the agent. Agents are identified by the capability Scope and gated by a per-workspace authorized-agents allowlist.

Content & Permissions

Browse, publish, download and govern projects, workbooks, views, datasources and Prep flows. Manage tags, permissions and revisions site-wide.

Pulse & Subscriptions

Manage Tableau Pulse metrics and definitions, retrieve BAN insights, and orchestrate email and Pulse subscriptions for end-users.

Metadata & VizQL Queries

Run arbitrary Metadata API GraphQL queries, search assets, walk workbook/datasource lineage and query published datasources via VizQL Data Service.

Who is this for?

This connector is used by three different roles. Jump to the section that matches yours; each one is self-contained.

Agent builder

You build agents in Agent Creator and want them to use Tableau. → Agent builder tab.

Platform admin

You run the platform and want to know what one-time setup Tableau needs. → Platform admin setup accordion below.

Workspace builder

You write Builder automations (DSUL) that call Tableau.<operation> directly. → Workspace builder tab.

Prerequisites

  • A Tableau Cloud site or a Tableau Server installation reachable from Prisme.ai.
  • A Personal Access Token (PAT) created on the target site under My Account Settings → Personal Access Tokens. You need its name and its secret (the secret is shown only once, at creation).
  • The PAT belongs to a Tableau user; that user must exist on the site and own the rights you want to expose (the connector acts as that user).
  • The site contentUrl if you are not on the Default site (the segment after /site/ in the browser URL).
  • Optionally, the REST API version to target (defaults to 3.21; pin only if your Tableau Server release requires it).
No platform-level credential is required. Tableau uses the per-workspace credential model: each workspace enters its own Personal Access Token in the connector’s configuration app, which stores it in the workspace secrets, and the connector resolves it server-side. There is no shared platform key, no central OAuth client, and no per-user OAuth flow to register.

Declare the capability in AI Governance (optional)

To let agent builders pick Tableau from the capability catalog instead of pasting an MCP endpoint URL by hand, declare it once as a named capability.
1

Open AI Governance > Capabilities

Create (or edit) a Tableau capability.
2

Point it at the MCP endpoint

Set the capability’s MCP server URL to the MCP endpoint of the workspace running the connector (shown in the configuration app, Agents tab), and set its Scope to:
The agent_id in the scope lets the connector identify and authorize the calling agent.
3

Make it available to agent builders

Once created, the capability appears in the capability picker for agent builders in your organization. Access to the catalog follows your organization’s existing roles; there is no per-capability role grant for this connector.
Declaring the capability makes the connector discoverable; it does not authorize a specific agent. Per-agent gating remains the configuration app’s Authorized agents allowlist, and the Tableau credentials still live in the workspace that owns the app instance the capability points at. Each workspace that installs Tableau supplies its own PAT; there is no OAuth auth-config JSON to attach in Governance.
The connector’s configuration app also offers an Add to catalog button (Agents tab, Capabilities catalog section) that publishes the capability to the organization-wide Capabilities catalog for you. It requires catalog write rights in your organization.

Agent builder

Goal: let an agent you build in Agent Creator query and act on Tableau through MCP tools.
Before an agent can call the connector, a Workspace builder must have installed and configured the Tableau app in a workspace (see the Workspace builder tab) so a credential and an MCP endpoint exist. The Platform admin setup accordion above is optional (it only publishes a reusable capability).
The Tableau credential is resolved server-side from the workspace secrets, never exposed to the agent. Your agent is identified by the agent_id that Agent Creator injects through the capability Scope, and that agent must appear in the connector’s authorized-agents allowlist (managed in the configuration app).
1

Install and configure Tableau in a workspace

Follow the Workspace builder tab: install Tableau in your workspace, open its Configuration app, fill the server and Personal Access Token in the Authentication tab, then select Test connection.
2

Allowlist your agent

In the configuration app, open the Agents tab and tick your agent under Authorized agents, or enable Allow all agents (disables selection + verification).
3

Add the MCP capability to your agent

Next to your agent, select Install capability: it adds the Tableau capability to the agent with the right endpoint and Scope, and adds the agent to the allowlist. To wire it by hand instead, add a capability pointing at the MCP endpoint shown in the same tab, and set its Scope to:
Without agent_id in the Scope, every call is rejected with an explicit “agent could not be identified” message.If a Platform admin has published a Tableau capability in the catalog (see the accordion above), pick it instead; the endpoint and Scope are already wired.
4

Use it

Ask the agent a Tableau question. It calls the relevant tool (workbooks, views, vizqlData, …) and grounds its answer on the result.

Brief the agent in its system prompt

Wiring the capability is not enough: the agent must know the tools exist and when to use them. Copy-pasteable starter:
Refine the trigger keywords (site names, project names, business domains, typical user phrasings) so the agent reliably picks up the right intent in your context.
Legacy AI Knowledge agents (no native MCP picker): add the connector under Advanced > Tools > MCP and paste the MCP endpoint URL shown in the configuration app (Agents tab).

Available Tools

The Tableau MCP follows a dispatcher pattern: each tool exposes multiple operations selected by an action argument. The argument list per action is documented in the tool’s own description.

Sites & Users

Content (Projects, Workbooks, Views)

Datasources & Flows

Scheduling, Jobs & Refresh Tasks

Subscriptions, Webhooks & Favorites

Tableau Pulse

Metadata & VizQL Data Service

Output Formats

Every tool accepts an outputFormat argument that controls the MCP response shape:
  • verbose (default): human-readable text for LLM consumption.
  • structured: machine-readable JSON in structuredContent.
  • both: both text and structured content.
Binary outputs (workbook/view image, PDF, PowerPoint, crosstab Excel, file downloads) cannot be returned inline. The connector instead returns metadata; call get and share the webpageUrl, or use views/getData and vizqlData for the underlying data.

Tool Details

workbooks

views

datasources

metadata

vizqlData

pulseSubscriptions


Security

The answers that hold for every connector (agent access, shared knowledge bases, credentials, models, egress) are on Connector security. This section lists what is specific to Tableau. The connector exposes administrative operations (sites, users, groups, permissions, schedules, webhooks, deletions): with the Viewer site role, Tableau refuses them. A personal access token allows a single active session, so any other sign-in with the same token ends the connector’s session: create a token used by the connector only.

Error Handling

Common Issues

“Tableau is not configured for this workspace”: The workspace has no saved server or credential (the message lists the missing fields). A workspace administrator opens the Configuration app, fills the Authentication tab, then selects Save authentication and Test connection. “Tableau signin failed (401)”: The Personal Access Token was rejected by Tableau, or the cached session was revoked. A Tableau PAT allows only one active session, so a parallel sign-in (a script, another tool) invalidates it. Dedicate the PAT to the connector, re-enter the secret in the configuration app, or retry; the connector forces a fresh sign-in on a 401. “Tableau access token rejected”: The Session token (X-Tableau-Auth) method is selected and the session token has expired or is invalid. Paste a new session token in the configuration app, or switch to Personal Access Token (recommended). “This agent is not authorized to use this connector”: The calling agent is not in the allowlist. A workspace administrator opens the configuration app, Agents tab, and ticks this agent under Authorized agents (or enables Allow all agents). “The calling agent could not be identified, so it cannot be authorized”: The MCP capability does not declare the agent scope. Set the capability Scope to context_id,agent_id (or use Install capability in the configuration app), then allow the agent in the Agents tab. “Site not found” / wrong site: Check Site (content URL, optional) in the configuration app. On Tableau Cloud it is the segment after /site/ in the browser URL; on Tableau Server’s Default site, leave it empty. Tableau Server-only operation on Tableau Cloud: Several site- and schedule-management actions (sites.create, sites.update, schedules.create, …) are only available on Tableau Server and return 403 on Tableau Cloud. Check the Tableau REST API reference for the current allow-list. VizQL queryDatasource returns 403 "API access permission": A Tableau administrator must grant API Access on the published datasource before the VizQL Data Service can query it.

External Resources

Tableau REST API Reference

Official documentation for the Tableau REST API 3.x, Metadata API, VizQL Data Service and Pulse.

Tool Agents

Learn how Agent Creator agents consume MCP tools and capabilities in Prisme.ai.