Tableau Scribe
Auto-documentation and metric dictionary engine for Tableau, powered by MCP.
Tableau Scribe connects to your Tableau Cloud or Server environment via the Tableau MCP and generates polished, audience-ready documentation from live views and datasources — no screenshots, no manual data entry, no copy-paste.
What It Does
Tableau Scribe operates in two modes:
Mode 1: Auto-Doc Generator
Point it at any published Tableau view and receive structured dashboard documentation covering purpose, key metrics, filters, usage guidance, and a lightweight design health summary. The skill fetches the rendered image, view metadata, workbook context, and datasource schema automatically.
Mode 2: Metric Definition Builder
Point it at any published datasource and receive a metric dictionary with plain-language definitions, directionality, business context, and field classifications. Designed so business users can understand what each metric means without opening Tableau.
Key Features
- Two depth levels — Brief (1-page reference card) or Detailed (full documentation, about 1.5-3 pages for a dashboard and 3-5 for a metric dictionary)
- Three output formats —
.docx(Word), on-screen (inline markdown), or.md(downloadable file) - Zero-upload workflow — No screenshots needed; MCP pulls the view image and metadata directly
- Graceful degradation — If a non-essential API call fails (timeout, restricted datasource), Scribe still produces what it can and explains gaps in a bottom note. If the session has expired or you can't access the view itself, it stops and says so
- Inline detection — If you specify format or depth in your request ("give me a brief Word doc"), Scribe skips the questions and goes straight to work
- Stale metadata detection — Flags when datasource schema and rendered view are out of sync
- Execution time transparency — Tells you upfront how long to expect (~15s brief, ~30-60s detailed)
Prerequisites
- Claude Desktop with agent mode enabled (Cowork)
- Tableau MCP configured and authenticated against your Tableau Cloud or Server site
- Permissions — Your Tableau user needs at least Viewer access to the views/datasources you want to document
Usage
Trigger Tableau Scribe with natural language:
Document this dashboard: [view name or URL]
Generate a metric dictionary for [datasource name]
/tableau-scribe
Example Prompts
| Prompt | Mode | What Happens |
|---|---|---|
| "Document the Sales Overview dashboard as a Word doc" | Auto-Doc | Detects .docx format, asks depth, generates documentation |
| "Give me a brief metric dictionary for the Segment Consumption datasource" | Metric Builder | Detects brief depth, asks format, generates dictionary |
| "Write detailed documentation for this view on screen" | Auto-Doc | Skips both questions (format + depth detected), proceeds immediately |
| "Tableau scribe — document everything about my Data Cloud dashboard" | Auto-Doc | Detects detailed depth, asks format |
Output Structure
Auto-Doc (Brief)
A single-page quick reference: purpose, top metrics with directionality, filters, a short how-to-read note, and caveats.
Auto-Doc (Detailed)
Seven sections: Purpose & Audience, Key Metrics (with definitions, business meaning, and directionality), Filters & Interactivity, How to Use This Dashboard, Data & Refresh, Design Health Summary, and Glossary.
Metric Dictionary (Brief)
Table-based one-liners: measures and calculated fields, one row each with definition and direction. Parameters are Detailed, all-fields scope only.
Metric Dictionary (Detailed)
Full field-level documentation: primary measures with business context and typical ranges, calculated fields with plain-language logic explanations, dimensions with cardinality, date fields with granularity, parameters (name and purpose where the metadata gives them), and field relationship notes. Formulas, parameter values and defaults, and refresh schedules are not available through the Tableau MCP and are marked for confirmation.
Skill Ecosystem
Tableau Scribe is designed to work alongside other Tableau MCP skills:
Blueprint ──→ Build ──→ Scribe ──→ VizCritique
(design) (create) (document) (evaluate)
| Skill | Relationship |
|---|---|
| Tableau Dashboard Blueprint | Designs the dashboard → Scribe documents what was built |
| Tableau Calc Engine | Writes calculations → Scribe explains them in plain language |
| Tableau Auto-Query | Provides sample data → Scribe uses it to enrich metric definitions |
| VizCritique Pro | Full scored evaluation → Scribe includes only a lightweight health summary and defers to VizCritique for depth |
Error Handling Philosophy
Scribe does not abort because one non-essential API call failed. Instead:
- It produces documentation from whatever data is available (graceful degradation across 5 priority levels)
- It places a bottom note at the end of the document explaining what was unavailable and why — keeping the documentation body clean
- It marks individual fields with "(inferred)" or "(not currently visible)" when specific items can't be confirmed
This means a restricted datasource or a timed-out query still gives you documentation. If your session has expired or you can't access the view or workbook itself, Scribe stops and tells you, rather than producing guesswork.
Author
Adam Mico — Built for the Tableau MCP ecosystem.
License
This skill is provided as-is for use within the Claude Desktop agent environment. See your organization's Tableau MCP licensing for API access terms.