DEV Community: suddhasheel bhatt

I Built a Tableau Dashboard with an AI Agent. Here’s Every Step That Actually Happened.

suddhasheel bhatt — Sun, 05 Apr 2026 16:08:26 +0000

No hype. No “AI generates dashboards” vaporware. Just a real build, real commands, and a .twb file that opened in Tableau Desktop.

I’ve seen a lot of “AI + Tableau” content lately. Most of it follows the same script: dramatic demo, hand-wavy explanation, no reproducible steps. So when I came across Twilize — a Tableau MCP server you install with pip — I decided to document exactly what happened when I used it. Every tool call. Every response. Every quirk.

This is that post.

What Is Twilize, Exactly?
— — — — — — — — — — — — —

Twilize is a Python package that runs as a local MCP (Model Context Protocol) server. MCP is an open protocol, originally from Anthropic, that lets AI assistants like Claude connect to external tools through a standardised interface — the same way a USB port lets any device plug into any computer.

What Twilize adds to this is a Tableau-specific toolset: a set of MCP functions that can create workbooks, add worksheets, configure chart types, build dashboard layouts, and save validated .twb files — all from natural language instructions or direct tool calls.

It is not a chatbot that “analyses” your Tableau dashboards. It is a workbook engineering layer. The distinction matters: Twilize writes Tableau files, it doesn’t read them for insights.

Install it with:

pip install twilize

Or with bundled examples:

pip install “twilize[examples]”

More at: https://twilize.com/tableau-mcp-server/

— -

Step 1: Check What It Can Actually Do
— — — — — — — — — — — — — — — — — — — -

Before building anything, I called list_capabilities to understand Twilize’s boundary. The response was honest and precise — something I didn’t expect.

It returned three tiers:

CORE (18 capabilities): Bar, Line, Area, Pie, Map, Text charts; Hyper, Excel, MySQL, federated connections; Color, Size, Tooltip encodings; dashboard layout containers.

ADVANCED (19 capabilities): Scatterplot, Heatmap, Bubble, Dual Axis, Tree Map; Filter and Highlight actions; LOD expressions; Reference Lines; Trend Lines; Color Palettes; Dashboard Themes.

RECIPE (6 capabilities): Donut, Lollipop, Bullet, Bump, Butterfly, Calendar charts — these are composite chart types built from Tableau primitives.

UNSUPPORTED (3): Bins, Sets, Table Calculations — explicitly flagged as out of scope.

That last category is rare in AI tooling. Most systems quietly fail or hallucinate when you ask for something they can’t do. Twilize tells you upfront. That’s good engineering.

— -

Step 2: Create the Workbook
— — — — — — — — — — — — — — -

I called create_workbook with a workbook name. In under a second, it returned the full field schema — every dimension and measure available:

Dimensions: Category, City, Country/Region, Customer ID, Customer Name, Order ID, Product Name, Region, Segment, Ship Mode, State/Province, Sub-Category…

Measures: Sales, Profit, Discount, Quantity, Order Date, Ship Date…

This is the Superstore dataset — Tableau’s built-in sample data — and Twilize wired it up automatically. No connection string. No credentials. No manual field mapping. You get a ready-to-use schema in one call.

— -

Step 3: Build the First Worksheet — Revenue by Region
— — — — — — — — — — — — — — — — — — — — — — — — — — —

I added a worksheet called “Revenue by Region” and configured it as a horizontal bar chart:

Mark type: Bar
Rows: Region
Columns: SUM(Sales)
Color: Region (one colour per bar)
Sort: descending by SUM(Sales)

Here’s what I didn’t expect: on my first attempt, I passed sort_descending as a boolean (true). Twilize rejected it with a clear validation error — it expected the field name to sort by, not a boolean flag. I corrected it to sort_descending=”SUM(Sales)” and it worked.

More usefully, after I accidentally omitted the sort on an earlier attempt, Twilize responded with a RULE VIOLATION warning:

[WARNING] bar.unsorted: Bar charts must be sorted descending by the measure.
-> Add sort_descending=’SUM(Sales)’

It caught a best practice violation and told me exactly how to fix it. This is what sets Twilize apart from a simple code generator — it has Tableau-specific design rules baked in.

— -

Step 4: Add the Monthly Trend Line
— — — — — — — — — — — — — — — — — — -

Next worksheet: a line chart showing monthly sales trends, broken down by customer Segment (Consumer, Corporate, Home Office).

Mark type: Line
Columns: MONTH(Order Date)
Rows: SUM(Sales)
Color: Segment

One call. Tableau date functions (MONTH()) work natively — no special syntax, no workarounds.

— -

Step 5: Add the KPI Tile
— — — — — — — — — — — — —

Download the Medium app
Third worksheet: a text/BAN (Big Ass Number) tile showing total revenue.

Mark type: Text
Label: SUM(Sales)

This is the kind of element that’s tedious to build in Tableau manually (text table, format number, remove headers, resize…). Here it’s a single configure_chart call.

— -

Step 6: Assemble the Dashboard
— — — — — — — — — — — — — — — —

With three worksheets ready, I called add_dashboard:

Dashboard name: “Sales Performance Dashboard”
Worksheets: Total Revenue KPI → Revenue by Region → Monthly Sales Trend
Layout: vertical
Size: 1200 x 800

The result: a combined dashboard with all three views arranged in order. One call, no drag and drop, no layout wrestling.

— -

Step 7: Validate
— — — — — — — — —

Before saving, I ran validate_workbook. It found 2 minor XSD schema deviations — both informational, flagged as non-blocking. The response was clear:

“These are informational only — Tableau Desktop is the true validator and will almost certainly open this workbook without issues.”

No false confidence. It told me what it found, what it means, and what to expect. The workbook opened cleanly.

— -

Step 8: Save to Desktop
— — — — — — — — — — — — —

Final call: save_workbook with an output path.

C:\Users[username]\Desktop\Sales_Performance_Dashboard.twb

Done. A real Tableau workbook on the desktop, ready to open, with three charts and a dashboard — built entirely through MCP tool calls, without touching Tableau’s interface once.

Total time from create_workbook to saved file: under 3 minutes.

— -

What This Changes for Tableau Developers
— — — — — — — — — — — — — — — — — — — — —

If you build Tableau dashboards professionally, here’s what Twilize actually changes:

Reproducibility. Every workbook is built from a sequence of function calls. That means you can version control it, run it in CI, template it, and rebuild it identically any time. Drag-and-drop dashboards are not reproducible. Twilize workbooks are.

Best practice enforcement. The rule violation system catches common Tableau mistakes — unsorted bars, missing chart elements — before the file is saved. It’s like a linter for Tableau.

Schema migration. This is the killer use case. When your database schema changes and field names break across 30 worksheets, Twilize’s workbook migration tool (https://twilize.com/workbook-migration/) remaps everything automatically using fuzzy field matching. A half-day manual task becomes a 2-minute automated one.

Workbook generation at scale. If you maintain a library of dashboards built on the same data model, Twilize can generate and update them programmatically. No more copy-paste-modify cycles across similar dashboards.

— -

Connecting Twilize to Claude Desktop
— — — — — — — — — — — — — — — — — — —

To use Twilize as an MCP server with Claude, add this to your Claude Desktop config file:

On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%\Claude\claude_desktop_config.json

{
“mcpServers”: {
“twilize”: {
“command”: “python”,
“args”: [“-m”, “twilize.mcp_server”]
}
}
}

Restart Claude Desktop. Then just describe the dashboard you want in plain English and Claude handles the rest through Twilize’s MCP tools.

The TREX extension file (for embedding Twilize directly in Tableau dashboards) is available at: https://twilize.com/tableau-trex-extension/

— -

The Bigger Picture: Tableau AI Agents in 2026
— — — — — — — — — — — — — — — — — — — — — — — -

Tableau launched on the premise that non-technical users shouldn’t need SQL to explore data. Drag and drop was the simplification.

In 2026, that simplification is happening again — but this time for dashboard building itself. Salesforce’s own Tableau Agent (their Einstein-powered AI layer) is evidence that even the platform vendor sees natural language as the future interface.

What Twilize offers that Tableau Agent doesn’t: file-level control, local operation, MCP compatibility with any AI tool, and a programmable API that works in scripts, pipelines, and CI workflows — not just inside the Tableau Cloud UI.

The tableau AI agent category is real, it’s here, and the .twb file sitting on my desktop right now is proof.

— -

Get Started
— — — — — —

Install: pip install twilize
MCP Server setup: https://twilize.com/tableau-mcp-server/
TREX Extension: https://twilize.com/tableau-trex-extension/
Workbook Migration tool: https://twilize.com/workbook-migration/
Workbook Generator: https://twilize.com/tableau-workbook-generator/
Video walkthrough: https://www.youtube.com/watch?v=7HvQ8IXrJ0E
Full site: https://twilize.com

— -

Have questions about setting up Twilize with Claude or Cursor? Drop them in the comments — happy to walk through specific use cases.

The AI Agent That Builds Tableau Dashboards for You — Meet Twilize

suddhasheel bhatt — Fri, 27 Mar 2026 04:13:06 +0000

You describe the dashboard. The AI builds the file. You open it in Tableau Desktop and it’s done.

If you’ve ever spent an afternoon rebuilding a Tableau dashboard because the underlying data source changed, or waited on an analyst to create “just one more chart,” or tried to explain to a developer exactly how you want a layout to look — this article is for you.

Twilize lets AI agents — including Claude, Cursor, and VSCode — build complete, ready-to-open Tableau workbook files (.twb and .twbx) from scratch, automatically. No clicking. No dragging. No formatting. The AI generates a real Tableau file that you open directly in Tableau Desktop.

It may be the world’s first AI agent purpose-built for Tableau workbook generation.

Why Tableau Dashboard Creation Is Still Broken
Tableau is powerful. But anyone who works with it regularly knows the hidden time tax:

Every new dashboard means starting from scratch, manually configuring charts, wiring up data sources, arranging layouts, and formatting everything to match brand standards. Multiply that across a team, across quarterly updates, across business units asking for “basically the same dashboard but for their region” — and the hours add up fast.

The promise of AI-assisted analytics has mostly delivered chat interfaces that talk about your data. Twilize does something different: it builds the actual Tableau file.

What Twilize Actually Does
At its core, Twilize is two things:

An MCP (Model Context Protocol) server that connects directly to AI tools like Claude Desktop, Cursor IDE, and VSCode. This means you can describe a dashboard to Claude in plain English and Claude uses Twilize under the hood to construct the actual workbook file — chart types, layouts, calculated fields, interactions, and all.

A tableau desktop based extension a .trex file than can create no click dashboards in .twb/.twbx format

The output in both cases is the same: a real .twb or .twbx file that opens directly in Tableau Desktop, fully formed.

The Workflow in Plain English
Here’s how a typical Twilize session works when used with an AI assistant like Claude:

You connect Twilize to your AI tool of choice (one config file change — see setup below).
You describe what you want: “Build me a sales overview dashboard with a bar chart of revenue by category, a pie chart showing customer segments, and a KPI card showing total profit.”
The AI calls Twilize’s tools behind the scenes — adding worksheets, configuring chart types, wiring up fields, building the dashboard layout.
Twilize generates and validates the .twb file.
You open it in Tableau Desktop. It’s ready.
The entire process that used to take an analyst two to four hours can happen in minutes.

What Kinds of Dashboards Can It Build?
Twilize supports a broad range of chart types and dashboard patterns out of the box:

Core charts — the stable, reliable building blocks: Bar charts, Line charts, Area charts, Pie charts, Maps, Text/KPI cards.

Advanced patterns — supported for more complex analytical needs: Scatterplots, Heatmaps, Tree Maps, Bubble Charts, Dual-Axis compositions, Table Calculations (running sums, rankings, window aggregations), KPI difference badges, Donut charts, and rich-text label cards.

Showcase recipes — high-impact visual patterns for executive and presentation dashboards: Lollipop charts, Butterfly (diverging bar) charts, Bullet charts, Calendar heatmaps, and Bump charts.

Beyond charts, Twilize handles the things that usually eat up the most analyst time: calculated fields, parameters for what-if analysis, dashboard filter and highlight actions, and multi-pane layout composition.

The Feature That Will Save Your Team the Most Time: Workbook Migration
Here’s one of Twilize’s most underappreciated capabilities, and probably the one with the highest immediate business value.

Write on Medium
The problem: You have a Tableau dashboard that works beautifully — but the underlying data source has changed. Maybe it’s a new Excel file with slightly different column names. Maybe it’s a database that was restructured. Maybe you’re rolling out a localized version for another market. Normally, this means manually remapping every field in every worksheet. On a complex dashboard, that’s a half-day task prone to errors.

Twilize’s solution: An automated workbook migration workflow. You point Twilize at the existing .twb workbook and the new data source, and it:

Scans the new data source and maps its columns.
Inventories every field the existing workbook uses.
Proposes a field-by-field mapping between old and new (using fuzzy matching).
Shows you a preview of what will change before touching anything.
Writes the migrated workbook, plus a JSON audit report of every field mapping decision.
If any mappings are uncertain, it pauses and asks for human confirmation before proceeding. The output is three files: the migrated .twb, a migration_report.json with the status of every field, and a field_mapping.json for audit trails.

For teams that manage dashboards across regions, business units, or fiscal year data refreshes — this single feature could save dozens of hours per year.

Built-In Quality Control
One thing that distinguishes Twilize from a “generate and hope” tool is its built-in validation layer. Before any workbook is saved, Twilize automatically checks the XML structure for fatal errors and warns about potential issues. It also supports full schema validation against the official Tableau TWB XSD specification (version 2026.1) — the same structural standard Tableau itself publishes.

This matters for enterprise contexts where bad workbooks waste analyst time and erode trust in automated tooling. Twilize won’t quietly hand you a broken file.

Setting It Up: Simpler Than You’d Expect
Getting Twilize connected to Claude Desktop takes about two minutes. Install it with a single pip command, then add one entry to your Claude configuration file:

json

{
"mcpServers": {
"twilize": {
"command": "uvx",
"args": ["twilize"]
}
}
}
The same one-line command works for Cursor IDE, VSCode, and Claude Code. After that, your AI assistant has the full power of Twilize available as a set of tools it can call on demand — no additional setup, no API keys for Twilize itself.

Who Should Be Paying Attention to This?
Tableau developers and analysts who spend significant time rebuilding similar dashboards for different teams, regions, or reporting cycles. Twilize turns that work into a repeatable, automatable workflow.

BI managers and data team leads looking to standardize dashboard templates across their organization. With Twilize, you can define a “golden template” and generate compliant variants programmatically — with validation built in.

Business users who know what they want to see but don’t have the Tableau skills to build it. If you can describe a dashboard to an AI assistant, Twilize can build it.

Developers building data products who want to generate Tableau content as part of an automated pipeline — think: automatically generating client-specific dashboards from a SaaS platform, or building Tableau reports as part of a data delivery workflow.

What Makes Twilize Different from Tableau’s Own AI Features
Tableau has invested heavily in its own AI capabilities (Tableau Agent, powered by Salesforce’s Einstein Trust Layer). It’s excellent for interactive, in-product exploration — asking questions, getting chart suggestions, adjusting visualizations in the browser.

But Tableau’s AI operates inside the Tableau interface. It requires a licensed Tableau Cloud or Tableau Server session. It doesn’t generate standalone workbook files you can version-control, share, or deploy programmatically. And it can’t automate workflows that need to run without a human in the loop.

Twilize operates entirely outside Tableau. It generates static .twb/.twbx files that work with Tableau Desktop, Server, and Online — no special license tier required. This makes it complementary to Tableau's native AI, not a replacement: use Twilize to build the workbook, use Tableau's AI to explore it.

The Bigger Picture: Why This Matters Now
The emergence of MCP (Model Context Protocol) as a standard for connecting AI models to external tools is changing what’s possible in enterprise software. Twilize is one of the first serious examples of MCP being applied to a major BI platform — and it’s a preview of what’s coming.

As more tools expose MCP interfaces, AI assistants will be able to operate across your entire data stack: pulling from databases, generating Tableau workbooks, pushing to Slack, updating records in Salesforce — all from a single natural language instruction. Twilize is an early but technically grounded step in that direction for the Tableau ecosystem.

The dashboard bottleneck is a solvable problem. Twilize is starting to solve it.

Have you tried Twilize? Building on top of it? I’d love to hear what use cases you’re exploring — drop a comment below.

Tags: Tableau, Business Intelligence, AI Agents, Data Visualization, MCP, Claude, Dashboard Automation, Data Analytics, Low-Code, Open Source