Log inSubmit server
Tableau Workbook Auditor logo

Tableau Workbook Auditor

Audit Tableau .twbx files locally for lineage, unused fields, duplicates, SQL, performance issues, and semantic version changes.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Tableau Workbook Auditor

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "tableau-workbook-auditor": {
      "command": "npx",
      "args": [
        "-y",
        "tableau-lineage-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 11 tools correctly (8d ago).

Overview

Tableau Workbook Auditor MCP server analyzes Tableau .twbx workbooks directly from local disk. It parses workbook XML to expose lineage, calculated fields, filters, dashboards, data sources, stored SQL, audit findings, and semantic differences between versions. Use it when an AI assistant needs to inspect workbook structure without Tableau, an account, or uploading sensitive files. The packaged extract is not decompressed, so analysis is limited to metadata stored in the workbook.

Use cases

  • Audit inherited Tableau workbooks
  • Trace calculated-field dependencies
  • Compare workbook versions semantically
  • Find unused fields and duplicate calculations
  • Extract stored SQL and workbook metadata

Key features

  • Local .twbx XML analysis
  • Calculated-field lineage tracing
  • Unused-field and duplicate-calculation audits
  • Static performance linting
  • Semantic workbook version diffs
  • Filter, dashboard, provenance, and SQL inspection

Tools11

What Tableau Workbook Auditor lets your agent do. Expand a tool for its parameters.

Verified live~1.7k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

5/5 checks healthy over the last 36d

What it can do

From the 11 tools this server returned when we ran it; 11 declare their own safety hints.

Read-only tools · 11
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age105 days
Maintainers1

Observed 2026-10-16 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 1d ago via OSV.dev · tableau-lineage-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars7Stargazers on the source repository.
npm downloads205Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed11Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Tableau Workbook Auditor works

What Tableau Workbook Auditor does

The Tableau Workbook Auditor MCP server lets MCP-compatible AI assistants inspect Tableau .twbx files stored on the local machine. It exposes the workbook’s structure and dependencies rather than querying Tableau Server, Tableau Cloud, or the packaged data extract.

The analysis covers calculated fields, raw fields, parameters, worksheets, data sources, filters, dashboards, connection details, refresh history when recorded, and SQL stored in the workbook. It also identifies possible unused fields, duplicate calculations, and static performance concerns. Findings about unused content are reported as candidates with confidence levels because the workbook file cannot prove that a field is never referenced outside the material it contains.

How it works

The Tableau Workbook Auditor MCP server receives a local workbook path through the MCP tool interface. Its engine unzips only the .twb XML entry from the .twbx package, parses that XML, and builds a model of workbook metadata and dependencies. The packaged extract is never decompressed or inspected.

The model supports dependency graphs, searchable formula and worksheet information, decoded filter details, dashboard layouts, data provenance, stored SQL, and audit rules. Version comparison operates on parsed workbook models rather than raw package files. It can identify added, removed, renamed, or edited calculations and show downstream fields affected by a calculation change. It also compares parameters, filters, worksheets, dashboards, data sources, and SQL.

Setup and configuration

Install the MCP package with Node and npx:

Terminal
npx -y tableau-workbook-auditor-mcp

The README also provides a Claude Desktop extension that can be downloaded and opened without a terminal or separate Node setup. For Claude Code, the documented plugin commands add the MCP package and its skill. Cursor and other MCP clients can register the server with an MCP command configuration.

No Tableau installation, Tableau license, account, backend, cookies, or environment variables are required by the documented setup. Processing remains local, so the .twbx file is not uploaded.

Tools and capabilities

The documented MCP interface includes tools for:

  • Analyzing and auditing a workbook.
  • Comparing workbook versions with a semantic diff.
  • Listing calculated fields and retrieving an individual field.
  • Tracing dependencies between fields and worksheets.
  • Listing parameters.
  • Inspecting filters, dashboards, provenance, and stored SQL through the workbook model.

The same parsed model can produce interactive HTML, Markdown, CSV, and JSON exports in the browser-based application. The HTML report is self-contained and can be used offline; the CSV contains field usage information, while JSON contains the complete model and audit results.

Limitations and notes

The Tableau Workbook Auditor MCP server works with information present in the workbook package. Runtime-generated queries from live connections are not stored in .twbx files and are therefore outside its scope. It does not inspect packaged extract rows, even when those extracts are included in the file.

Workbooks up to 500 MB are supported by the browser application because only the XML is decompressed. Static performance checks flag likely issues such as complex LOD expressions, long calculations, excessive quick filters, missing context filters, live connections, fixed-size dashboard settings, dense dashboards, and orphan worksheets; these are lint findings rather than runtime measurements.

Unused-field results are candidates graded as unused, likely-unused, or referenced-in-comment. A field can appear unused in the workbook model without being conclusively dead in every possible Tableau workflow.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Tableau Workbook Auditor

Tableau Workbook Auditor is an MCP server that connects AI assistants to Tableau .twbx files on your local disk. Its main tools analyze and audit workbooks, compare versions, list and inspect calculated fields, trace dependencies, inspect parameters, and retrieve filters, dashboards, provenance, and stored SQL without uploading the workbook.

Install it with npx using `npx -y tableau-workbook-auditor-mcp`. Claude Desktop users can instead download and open the provided extension, while Claude Code users can install the documented marketplace plugin.

Yes, Tableau Workbook Auditor works with Cursor through an MCP command configuration. The documented command is `claude mcp add tableau-lineage -- npx -y tableau-lineage-mcp`, and the server reads workbooks from local disk.

No, it does not inspect packaged extract rows. The engine decompresses only the workbook XML, so it can analyze metadata, formulas, dependencies, and stored SQL but not the data contained in an extract.

Yes, it can compare up to five versions of the same dashboard with a semantic diff. The comparison reports calculation changes and downstream impact, along with changes to parameters, filters, worksheets, dashboards, data sources, and SQL.

Related MCP servers

All in Data Visualization All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTableau Workbook Auditor AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/tableau-workbook-auditor?style=directory)](https://allmcps.com/mcp/tableau-workbook-auditor)
HTML Embed
<a href="https://allmcps.com/mcp/tableau-workbook-auditor"><img src="https://allmcps.com/api/badge/tableau-workbook-auditor?style=directory" alt="Tableau Workbook Auditor on AllMCPs" /></a>