Tableau Workbook Auditor vs Semiotic

A side-by-side look at the Tableau Workbook Auditor and Semiotic MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Tableau Workbook Auditor logoTableau Workbook AuditorData Visualization · Local subprocess (stdio)Local-only Tableau .twbx audit: lineage, unused fields, duplicate calcs, SQL, version diffs60GoodAuth: not declaredSemiotic logoSemioticData Visualization · Local subprocess (stdio)React data visualization MCP server with 30+ chart types. 5 tools: suggest charts for a dataset, render validated React configs to SVG, diagnose configuration anti-patterns, get component schemas, and report issues.71GreatAuth: no auth required

Verdict: choose Tableau Workbook Auditor for data visualization work as a local process; choose Semiotic for data visualization as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Tableau Workbook Auditor logoChoose Tableau Workbook Auditor when

  • You need dedicated capabilities in the Data Visualization domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like analyze_workbook, list_calculated_fields, get_field.
Explore Tableau Workbook Auditor

Semiotic logoChoose Semiotic when

  • You need dedicated capabilities in the Data Visualization domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like renderChart, renderInteractiveChart, getSchema.
Explore Semiotic

Feature & specification comparison

Rows where the two servers differ are marked.

SpecTableau Workbook Auditor logoTableau Workbook AuditorSemiotic logoSemiotic
CategoryData VisualizationData Visualization
Quality signal60/100 · Good71/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars72,716
Directory activity 2 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
Tools1118

Tools & capabilities

Tableau Workbook Auditor tools 11

  • analyze_workbookParse a local Tableau workbook (.twbx or .twb) and return an overview: field counts, datasources, calculated-field names by type, parameter names, and raw fields. Parsing happens locally; the file is never uploaded. Start here, then use the other tools for details.
  • list_calculated_fieldsList every calculated field in the workbook with its formula, type (calculated / LOD / table calc), datasource, and what it directly depends on. Optionally filter by a case-insensitive substring of the field name or formula.
  • get_fieldFull detail for a single field by name (brackets optional, case-insensitive): formula, type, direct dependencies, and every field that directly uses it.
  • trace_dependenciesTrace what a field is built from (upstream, recursive tree down to raw columns and parameters) and everything that would be affected if it changed (downstream, transitive). The impact-analysis tool: use before editing a calculation.
  • list_parametersList every parameter in the workbook: current value, datatype, allowed values, and which calculated fields use each one.
  • get_lineage_graphThe complete dependency graph as JSON: one node per field/parameter (with type) and one directed edge per dependency (source feeds target). Suitable for rendering or graph analysis.
  • list_sql_queriesExtract every SQL statement the workbook contains: Custom SQL relations (with the full query text), Initial SQL run when a connection opens, stored-procedure references with their parameters, and RAWSQL_* calculated fields. Each entry names the datasource and the database connection (class, server, dbname) it targets. Note: queries Tableau auto-generates at runtime for live connections are not stored in the file, so they cannot be extracted.
  • list_filtersEvery filter in the workbook, deduplicated across worksheets: the field it acts on (caption-resolved), filter kind (categorical / quantitative / relative-date), whether it is a context filter, which worksheets use it, selected member values when stored, and quantitative ranges. Includes a by_worksheet grouping and the distinct list of fields driving any filter. Data-source filters are marked "(data source filter)".
  • list_worksheetsEvery worksheet in the workbook with the fields it uses (caption-resolved, from its datasource dependencies) and the filters it applies (field, kind, context status). The per-sheet view of the workbook: use it to answer "what does this sheet depend on?" or "where is this field actually displayed?".
  • diff_workbooksSemantic diff between two Tableau workbooks: calculations added, removed, renamed or edited (with the downstream fields each edit affects), plus changed parameters, filters, worksheets, dashboards, data sources and stored SQL. Formula reformatting is ignored, and a field that disappears while an identical formula appears under a new name is reported as a rename. Use this for release notes, code review of a workbook change, or answering "what changed and what does it break?".
  • audit_workbookFind what is wrong with a workbook: fields and parameters nothing uses (each with a confidence level and the reason), duplicate calculations (identical formulas under different names, and the more dangerous same-name-different-formula case), and performance findings (heavy LODs, nested calculations, deep calculation chains, non-fixed dashboard sizing, live connections, and more). Use it before a cleanup, a migration, or a workbook review. Unused fields are reported with confidence rather than as certainties, because a field can be referenced in ways a file cannot show.

Semiotic tools 18

  • renderChartRender a Semiotic chart to static SVG. Supports the components returned by `getSchema` that are marked `[renderable]`. Pass `{ component: "LineChart", props: { data: [...], xAccessor: "x", yAccessor: "y" } }`. Returns SVG string plus a "Render evidence" JSON block (mark counts by scene type, resolv…
  • renderInteractiveChartRender a static-data chart as a ChatGPT Apps widget. Uses the same Semiotic server render path as `renderChart`, then hydrates an iframe UI with fit, zoom, data, hover, and render-evidence controls.
  • getSchemaReturn the prop schema for a specific component. Pass `{ component: "LineChart" }` to get its props, or omit `component` to list the complete schema-backed catalog. Components marked `[renderable]` are available through `renderChart`; realtime charts require a browser/live environment.
  • suggestChartSample-row recommender. Pass `{ data: [{...}, ...] }` with 1–5 sample objects plus optional broad intent/capability filters.
  • suggestChartsCapability-based recommender for bounded row data. Returns ranked chart suggestions with scores, reasons, caveats, import paths, and ready-to-use props.
  • suggestStreamChartsRecommend streaming charts from a schema (shape, key, throughput). Returns `{ suggestions, excluded, stretchSuggestions }`.
  • suggestStreamDashboardCompose a multi-panel dashboard from stream schemas and an audience layout policy.
  • suggestDashboardBuild a multi-panel dashboard suggestion that covers distinct analytical intents.
  • suggestStretchChartsRecommend audience-literacy stretch picks from an `AudienceProfile`.
  • repairChartConfigCheck whether a requested chart fits a dataset and return ranked alternatives when it does not.
  • interrogateChartReturn a statistical summary and chart-aware context for answering natural-language questions with optional annotations.
  • diagnoseConfigCheck a chart configuration for common problems — empty data, bad dimensions, missing accessors, wrong data shape, and more. Returns a human-readable diagnostic report with actionable fixes.
  • +6 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Tableau Workbook Auditor

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "tableau-workbook-auditor": {
      "command": "npx",
      "args": [
        "-y",
        "tableau-lineage-mcp"
      ]
    }
  }
}

Semiotic

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "nteract-semiotic": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "semiotic",
        "semiotic-mcp"
      ]
    }
  }
}

Frequently asked questions

Tableau Workbook Auditor is categorized under Data Visualization and uses a local stdio subprocess. Semiotic belongs to Data Visualization and uses a local stdio subprocess. Pick Tableau Workbook Auditor for data visualization work and Semiotic for data visualization.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Tableau Workbook Auditor has no declared pricing — check the project's own site. Semiotic is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add tableau-workbook-auditor and nteract-semiotic as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Tableau Workbook Auditor has a quality signal of 60/100 (Good) with 2 views, 0 installs and 7 GitHub stars. Semiotic has 71/100 (Great) with 6 views, 0 installs and 2,716 GitHub stars.