Tableau Cloud

The hosted service is available to Tableau Cloud customers on any SKU, so there is no separate MCP purchase. Individual tools can still be gated: Tableau documents that Pulse Insight Briefs require Tableau+ and the full Metadata API surface requires Data Management. A tool needing an entitlement you lack returns an error when called, not at sign-in.

Not through the 23 tools Anthropic lists — every one reads, queries or downloads. Tableau's own documentation describes 13 further tools, including delete-content, publish-workbook and update-user, which are absent from that listing. Those carry admin-only gates and feature flags in Tableau's docs, so treat the read-only surface as what Anthropic lists rather than the whole product.

The connector requests 20 scopes and five end in create, including workbook create and file uploads create. That grant is broader than the 23 read tools Anthropic lists, which is worth knowing before you approve it. Tableau publishes the full scope list at its own RFC 9728 metadata endpoint, so you can read exactly what is requested before consenting.

No. Tableau documents that the server makes REST API calls as the signed-in user, so every existing per-user permission and access control is enforced automatically. The connector inherits your Tableau identity rather than widening it. A site administrator can narrow it further using the EXCLUDE_TOOLS site setting to block whole tool groups.

Not the service itself. Tableau states plainly that Cloud site administrators cannot disable the hosted MCP service. What they can do is stop it issuing tool calls against their site by setting the EXCLUDE_TOOLS variable in site settings through the REST API, listing every tool group to exclude. That is a per-site block, applied by configuration rather than an off switch.

The hosted endpoint does not. Tableau documents mcp.tableau.com as available to Tableau Cloud customers and explicitly not available for Tableau Server, directing Server customers to self-host instead. The same open-source server can be run on-premise, where the tool surface and its admin gates are yours to configure rather than Tableau's to operate.

Anthropic's directory lists 23 for the hosted endpoint. Tableau's own documentation has per-tool pages for 36, and says the hosted service offers the full catalogue subject to entitlements and permissions. The two counts disagree and Tableau's is larger, so the 23 is what Anthropic recorded rather than a ceiling the vendor states.

On the documented delete-content tool, a single call cannot delete anything. Tableau documents a two-phase design: the default preview tags the resource pending-deletion and returns metadata, and only a second call with confirm true proceeds, after the server re-verifies the tag. The gate is server-authoritative, so an agent cannot skip it by guessing arguments.