Tableau Workbook Auditor vs Kibana
A side-by-side look at the Tableau Workbook Auditor and Kibana MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Tableau Workbook Auditor for data visualization work as a local process; choose Kibana 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?
Choose 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.
Choose Kibana when
- You need dedicated capabilities in the Data Visualization domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
KIBANA_URL, KIBANA_API_KEY, KIBANA_USERNAME, KIBANA_PASSWORD, KIBANA_COOKIES. - You want tools like
get_status, execute_kb_api, search_kibana_api_paths.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Visualization | Data Visualization |
| Quality signal | 60/100 · Good | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | KIBANA_URLKIBANA_API_KEYKIBANA_USERNAMEKIBANA_PASSWORDKIBANA_COOKIES |
| Verified owner | Community listing | Community listing |
| GitHub stars | 7 | 84 |
| Directory activity | 2 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 11 | 16 |
| Full listing | View Tableau Workbook Auditor | View Kibana |
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.
Kibana tools 16
get_statusGet Kibana server status with multi-space supportexecute_kb_apiExecute a custom API request for Kibana with multi-space support. RETRY SAFETY: this tool can reach any write endpoint. A POST retried after a timeout or dropped response can create a duplicate — prefer a caller-chosen stable id (or the vl_* tool for that object type, which documents the safe pattern) over letting the server auto-generate one.search_kibana_api_pathsSearch Kibana API endpoints by keywordlist_all_kibana_api_pathsList all Kibana API endpoints as a resource listget_kibana_api_detailGet details for a specific Kibana API endpointget_available_spacesGet all available Kibana spaces with current contextvl_search_saved_objectsSearch for Kibana saved objects using Elasticsearch query syntax. This is a universal tool that can search across all saved object types (dashboard, visualization, index-pattern, search, config, lens, map, tag, canvas-workpad, canvas-element, etc.). IMPORTANT: You must specify the 'types' parameter - it is required by the Kibana API. PERFORMANCE TIPS: Always use 'fields' parameter to specify only needed fields (e.g., ['title', 'description']) for faster responses. Use 'perPage' 5-20 for optimal speed. PAGINATION: To get all results, make multiple requests with incrementing 'page' numbers (page=1, page=2, etc.) until you receive fewer results than 'perPage'. Don't stop at the first page - iterate through all pages for complete data. Returns formatted saved object information including type, title, description, and timestamps.vl_get_saved_objectGet a single Kibana saved object by type and ID. This is a universal tool that can retrieve any type of saved object (dashboard, visualization, index-pattern, search, config, lens, map, tag, canvas-workpad, canvas-element, etc.) by its exact type and ID. Use this when you know the specific object you want to retrieve. PERFORMANCE: This is much faster than searching when you have the exact type and ID.vl_bulk_delete_saved_objectsBulk delete multiple Kibana saved objects by type and ID. This is a destructive operation that permanently removes saved objects (dashboard, visualization, index-pattern, search, config, lens, map, tag, canvas-workpad, canvas-element, etc.). WARNING: Deleted objects cannot be recovered. Use with caution. IMPORTANT: Objects that exist in multiple namespaces require the 'force' parameter to be deleted.vl_create_saved_objectCreate a new Kibana saved object (dashboard, visualization, index-pattern, search, config, lens, map, tag, canvas-workpad, canvas-element, etc.). This is a universal tool that can create any type of saved object by specifying the type and attributes. Each object type has specific attribute requirements. IMPORTANT: The 'title' field is required for most object types. Complex fields like panelsJSON, visState should be JSON strings.vl_update_saved_objectUpdate a single Kibana saved object by type and ID. This performs a partial update - only the specified attributes will be changed, other attributes remain unchanged. Supports all saved object types (dashboard, visualization, index-pattern, search, config, lens, map, tag, canvas-workpad, canvas-element, etc.). IMPORTANT: Use version parameter for optimistic concurrency control to prevent conflicts.vl_bulk_update_saved_objectsUpdate multiple Kibana saved objects in a single operation. Each object can be of different types and will be partially updated (only specified attributes changed). Supports all saved object types (dashboard, visualization, index-pattern, search, config, lens, map, tag, canvas-workpad, canvas-element, etc.). PERFORMANCE: More efficient than multiple single updates. Each object can have individual version control.- +4 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": {
"tableau-workbook-auditor": {
"command": "npx",
"args": [
"-y",
"tableau-lineage-mcp"
]
}
}
}
Kibana
{
"mcpServers": {
"kibana": {
"command": "npx",
"args": [
"-y",
"@tocharianou/mcp-server-kibana"
],
"env": {
"KIBANA_URL": "YOUR_KIBANA_URL_HERE",
"KIBANA_API_KEY": "YOUR_KIBANA_API_KEY_HERE",
"KIBANA_USERNAME": "YOUR_KIBANA_USERNAME_HERE",
"KIBANA_PASSWORD": "YOUR_KIBANA_PASSWORD_HERE",
"KIBANA_COOKIES": "YOUR_KIBANA_COOKIES_HERE"
}
}
}
}
Frequently asked questions
Tableau Workbook Auditor is categorized under Data Visualization and uses a local stdio subprocess. Kibana belongs to Data Visualization and uses a local stdio subprocess. Pick Tableau Workbook Auditor for data visualization work and Kibana 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. Kibana is listed as free. Auth: api key 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 kibana 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. Kibana has 69/100 (Great) with 4 views, 0 installs and 84 GitHub stars.