mcpField
T
Tableau Workbook Auditor

Tableau Workbook Auditor

Local
tableau-lineage.comData & Analytics7Updated 6w ago

About Tableau Workbook Auditor

Tableau Workbook Auditor is a local MCP server for analyzing Tableau .twb and .twbx workbooks. It provides workbook audits, semantic version comparisons, and field-level lineage while parsing workbook XML on the machine without sending files over the network.

Key features

  1. 01Audit unused fields and duplicate calculations
  2. 02Compare workbook versions semantically
  3. 03Trace field dependencies and downstream impact
  4. 04Inspect filters, worksheets, parameters, and SQL
  5. 05Build a complete lineage graph

Use cases

  1. 01Find candidate fields to remove from a workbook
  2. 02Review changes and impacts between dashboard versions
  3. 03Trace the inputs and dependents of a calculation
  4. 04Document workbook data sources and field lineage

MCP support

It exposes 11 tools to MCP clients, including audit, diff, lineage, filter, worksheet, and SQL inspection. Tools read local .twb or .twbx files; parsing is performed on the machine.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"andey0saikiran-tableau-lineage": {
"command": "npx",
"args": [
"-y",
"tableau-lineage-mcp"
]
}
}
}
Run commandnpx -y tableau-lineage-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmtableau-lineage-mcp1.0.1

Tools

11

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
pathstringYesAbsolute (or cwd-relative) path to a local Tableau workbook: .twbx or .twb

Details

From the project README

tableau-lineage-mcp

Let your AI assistant read the lineage inside Tableau workbooks without the workbook ever leaving your machine.

An MCP server that parses local Tableau workbooks (.twbx / .twb) and exposes eleven tools to Claude, Cursor and any other MCP client: a full workbook audit (unused fields, duplicate calculations, performance findings), a semantic diff between two versions, and the complete lineage of every calculated field, parameter, filter, worksheet, dashboard and stored SQL statement.

It is the same open-source extraction engine that powers tableau-lineage.com, wrapped for AI assistants. Parsing happens in-process on your machine: no upload, no server, no account. When reading a .twbx, only the workbook XML is decompressed; the bundled data extract is never touched.

What you can ask your assistant

  • "Audit ~/Downloads/Sales.twbx. What is safe to delete?"
  • "What changed between v3 and v4 of this dashboard, and what does it break?"
  • "Which fields does [Profit Ratio] depend on?"
  • "Why is this workbook slow?"
  • "Which sheets filter on Region, and what values are selected?"
  • "Write a data dictionary for this workbook."

Install

Claude Desktop (one click, no terminal)

Download the extension and double-click it. Claude Desktop installs it for you. No Node install and no config file needed, because Claude Desktop ships its own Node.

You can also drag the .mcpb onto the Claude Desktop window, or use Settings → Extensions → Advanced settings → Install Extension.

Claude Code
claude mcp add tableau-lineage -- npx -y tableau-lineage-mcp
Claude Desktop (manual, if you prefer config over the extension)

Add to claude_desktop_config.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "tableau-lineage": {
      "command": "npx",
      "args": ["-y", "tableau-lineage-mcp"]
    }
  }
}
Cursor / other MCP clients

Any client that supports stdio MCP servers works with the same command: npx -y tableau-lineage-mcp.

Requires Node.js 18+.

Tools

ToolWhat it does
audit_workbookUnused fields and parameters (graded by confidence, with reasons), duplicate calculations, and performance findings with severities and fixes
diff_workbooksSemantic diff of two versions: calculations added, removed, renamed or edited (each edit with the downstream fields it affects), plus parameters, filters, sheets, dashboards, data sources and SQL
analyze_workbookOverview: stats, data sources, calculated fields by type, parameters, raw fields
list_calculated_fieldsEvery calculation with formula, type, and direct dependencies; optional substring filter
get_fieldOne field in full detail, including everything that directly uses it
trace_dependenciesUpstream tree (down to raw columns and parameters) plus transitive downstream impact
list_parametersParameters with values, datatypes, allowed values, and which fields use them
get_lineage_graphThe complete dependency graph as nodes and edges JSON
list_sql_queriesCustom SQL (full query text), Initial SQL, stored-procedure references with parameters, and RAWSQL_* calculations, each with the connection it targets
list_filtersEvery filter, deduplicated across worksheets: field, kind, context-filter status, member selections and ranges, plus a by_worksheet breakdown
list_worksheetsEvery worksheet with the fields it uses (caption-resolved) and the filters it applies

All tools take a path to a local .twbx or .twb file. Field names are case-insensitive and brackets are optional: Profit Ratio and [profit ratio] both resolve.

Privacy Policy

Full policy: https://github.com/andey0Saikiran/tableau-lineage/blob/main/PRIVACY.md

What is collected: nothing. This server makes no network requests of any kind. It reads only the workbook paths you explicitly pass to it, parses them in memory on your machine, and returns the results to the MCP client that started it. It does not read your other files, your conversation history, or your assistant's memory, and it writes nothing to disk.

Storage and retention: none. Workbook data lives in memory for the length of the call and is discarded when the process exits. There is no server, no database and no logging.

Third parties: none. Note that the results of a tool call (field names, formulas, audit findings) are returned to the AI assistant you chose to ask, so that it can answer you; your workbook file itself is never sent anywhere. Your assistant's own privacy policy governs that conversation.

Contact: https://github.com/andey0Saikiran/tableau-lineage/issues · security reports: https://github.com/andey0Saikiran/tableau-lineage/security/advisories/new

How it works

  • The workbook is read from your local disk and parsed in the Node process. Nothing is sent anywhere.
  • Unused fields are reported as candidates with a confidence level, never as a guaranteed-safe delete list: a workbook file cannot prove a field is unreferenced everywhere. Read the reason before deleting anything.
  • For .twbx packages, only .twb XML entries are decompressed. The packaged data extract (.hyper / .tde) is skipped entirely.
  • No analytics, no telemetry, no network calls at all.

Because this package is open source, you can verify all of the above in the code.

Prefer a UI?

The same engine runs as a free web app at tableau-lineage.com: drag a .twbx in and get the audit, an interactive lineage graph, a searchable data dictionary, and a version comparison, 100% in your browser.

Development

git clone https://github.com/andey0Saikiran/tableau-lineage
cd tableau-lineage/mcp
npm install
npm test        # builds, then runs an end-to-end JSON-RPC smoke test

License

MIT © Sai Kiran Andey

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.