Connect Tableau to Claude Code

Let Claude refresh extracts and publish workbooks in Tableau. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Tableau to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Tableau, you add a Tableau MCP server: a small hosted service that exposes Tableau's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Tableau account. No API keys pasted into config files.

claude mcp add --transport http tableau https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Tableau once connected?

Full read-write Tableau access lets Claude trigger extract refreshes, publish and move workbooks and data sources, manage projects, and update content permissions and ownership, all within the site roles you grant. The dashboard upkeep and content admin that used to mean clicking through Tableau Cloud or Server happens where your analytics already live.

Trigger an extract refresh for a published data source after you approve it
Publish or overwrite a workbook into a specified project
Move a workbook or data source between projects and reassign ownership
Create or update a project and set its default permissions
Grant or revoke a group's permissions on a workbook once you confirm
Inspect a site's workbooks, views, and refresh schedules to plan a change

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Tableau access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Tableau API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Tableau changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Tableau connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Tableau connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Tableau account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Tableau's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Tableau?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Tableau account it signs in with. Revoking access is one click in Tableau.

More on the Tableau connector

Tableau connector for claude.ai Microsoft Power BI + Claude Code BigQuery + Claude Code Snowflake + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us