Skip to main content

Connect Tableau to Claude Code

Give Claude Code governed access to Tableau’s 26 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Tableau to Claude Code in four steps

Admins approve the server once. Everyone in Claude Code then gets it through the same governed connection.

  1. 1

    Add Tableau to Runlayer

    Tableau isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Claude Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Claude Code, and an Anthropic org install also reaches Claude Code. With direct tool listing turned on for your deployment, Tableau’s 26 tools show up in Claude Code’s own tool list (supported Claude Code versions).

    Claude Code setup guide
  3. 3

    Sign in to Tableau

    Sign in the way Tableau requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Tableau from Claude Code

    Tableau’s approved tools appear in Claude Code. Every call is checked against policy and recorded.

Tools

26 Tableau tools in Claude Code

Runlayer policy decides which of these Claude Code users can call.

  • Download workbook

    Downloads workbook content as a TWB (application/xml) or TWBX (application/octet-stream) file.

  • Generate pulse insight brief

    Generate a concise insight brief for Pulse Metrics using Tableau REST API.

  • Generate pulse metric value insight bundle

    Generate an insight bundle for the current aggregated value for Pulse Metric using Tableau REST API.

  • Get custom view data

    Retrieves comma-separated value (CSV) data for a Tableau Custom View (saved/personalized view state), including the user's filters.

  • Get custom view image

    Retrieves an image of the specified custom view in a published viz.

  • Get datasource metadata

    Retrieves metadata for a specified datasource by taking the basic, high level, metadata results from Tableau's VizQL Data Service and enriches them with additional context provided by Tableau's…

  • Get view

    Retrieves information about the specified view, including upstream datasources, workbook information, project details, owner, tags, and usage statistics.

  • Get view data

    Retrieves data for the specified view in a Tableau workbook, including the user's filters.

See all 26 Tableau tools

Control

What Runlayer can see and stop in Claude Code

Some controls apply to every client at the gateway. Others depend on what Claude Code exposes to Runlayer.

  • Gateway policy (available)

    Every Tableau call from Claude Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude Code as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude Code prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • OTLP telemetry (available)

    Claude Code can export OpenTelemetry logs to Runlayer for observe-only session reconstruction.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Claude Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Claude Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in Claude Code and pass the rest through.

In Claude Code

  • When a tool fails, Runlayer records the error but cannot hide it.

Frequently asked questions

Connect more

Find another combination