Tableau Graphql MCP vs Amcharts5
A side-by-side look at the Tableau Graphql MCP and Amcharts5 MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Tableau Graphql MCP for data visualization work as a local process; choose Amcharts5 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 Graphql MCP when
- You need dedicated capabilities in the Data Visualization domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TABLEAU_SERVER, TABLEAU_SITE_CONTENT_URL, TABLEAU_PAT_NAME, TABLEAU_PAT_SECRET, TABLEAU_AUTH_TOKEN, TABLEAU_COOKIE, TABLEAU_TIMEOUT, TABLEAU_API_VERSION. - You want tools like
graphql_query, introspect_schema, lineage_examples.
Choose Amcharts5 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
list_chart_types, get_chart_reference, get_core_reference.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Visualization | Data Visualization |
| Quality signal | 57/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | TABLEAU_SERVERTABLEAU_SITE_CONTENT_URLTABLEAU_PAT_NAMETABLEAU_PAT_SECRETTABLEAU_AUTH_TOKENTABLEAU_COOKIETABLEAU_TIMEOUTTABLEAU_API_VERSION | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 8 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 7 | 12 |
| Full listing | View Tableau Graphql MCP | View Amcharts5 |
Tools & capabilities
Tableau Graphql MCP tools 7
graphql_queryRun ANY read-only GraphQL query against the Tableau Metadata API. This is the general-purpose tool; use it for any lineage question. Returns {"data": ..., "errors": ...}. The Metadata API is a GraphQL graph of Tableau content (workbooks, sheets, dashboards, datasources, fields) and, with the Data Management add-on, physical assets (databases, tables, columns) and their upstream/downstream lineage. How to write a correct query: - Filters are EXACT and case-sensitive: `filter: {name: "X"}` or `filter: {nameWithin: ["X","Y"]}` (nameWithin is the only multi/OR match; there is NO substring or regex). - Every list field has a `<name>Connection` variant with `first`/`offset`/`after` + `pageInfo` (page size max 1000). Keep one query under ~20,000 nodes; narrow filters and page. - Fields is an interface; branch with `__typename` and inline fragments (`... on ColumnField { columns { name } }`, `... on CalculatedField { formula }`). - Reach a field's owning workbook via `datasource { ... on EmbeddedDatasource { workbook { name } } }`. - `downstream*` fields (downstreamWorkbooks/Owners, external tables/columns) need Data Management (Tableau Catalog) and are often empty otherwise; then resolve via core lineage (referencedByFields -> sheets -> workbook), or just call the `where_used` tool. Entry points include: workbooks, sheets, dashboards, publishedDatasources, embeddedDatasources, fields, columnFields, calculatedFields, columns, databaseTables, customSQLTables, databases, flows, tableauUsers, dataQualityWarnings. Call `lineage_examples` for ready-made query templates and a schema cheat-sheet, or `introspect_schema` to inspect any type's exact fields. Read-only: mutation and subscription operations are rejected. If a query exceeds the ~20,000-node limit, the response is flagged with `partial_results: true` and a `warning` (it does NOT auto-page an arbitrary query) so you never mistake a truncated result for a complete one.introspect_schemaIntrospect the live Metadata API GraphQL schema (introspection is enabled). With no argument: returns every Query entry point (with its args) and the full list of type names. With `type_name` (e.g. "Column", "Workbook", "DatabaseTable", "CalculatedField"): returns that type's fields, their result types, and args, so you can write a correct query against exactly what this server exposes.lineage_examplesReturn a schema cheat-sheet and a library of curated lineage questions with their correct GraphQL queries (+ example variables). Read this before composing a `graphql_query`. Categories: impact, provenance, calc, datasource, search, inventory, governance, ownership. Pass one to filter; omit to get them all. Each example has: question, graphql, variables, notes.where_usedFind which workbooks (and published datasources) USE the given names, the common 'where is this used / impact analysis' question, resolved robustly. `names` are EXACT, case-sensitive names of any of: a Snowflake/DB column, a Tableau field or alias, or a database table. Pass several to check them in one call. Results group by workbook, showing how each matched (column / field / whole table, with schema and source table) and which worksheets use it. This uses CORE lineage (referencedByFields -> field.sheets -> workbook, and field.datasource -> workbook), so it works even without the Data Management add-on where `downstreamWorkbooks` is empty. For other shapes of question, use `graphql_query`.impact_analysisFull transitive (MULTI-HOP) downstream impact of a column, field, or table. Returns every field that directly OR indirectly depends on it, and all affected sheets, dashboards, workbooks, plus the de-duplicated set of OWNERS to notify before a change. This is the "what breaks if I change/drop this?" tool. Unlike `where_used` (one core-lineage hop), it follows the whole dependency chain — a calc built on a calc built on the column is included. `name` is exact and case-sensitive. Workbooks are derived from downstream sheets/dashboards (the flat downstreamWorkbooks edge is unreliable). If it returns nothing on a site without Data Management, the transitive lineage may not be indexed there — use `where_used` for the direct references.search_contentFind content whose NAME contains `term` (case-insensitive SUBSTRING). Use this when you only know part of a name, since every other tool and the Metadata API filter are exact-match. Searches workbooks, published datasources, and database tables by default. Pass `types` to choose from: "workbook", "datasource", "table", "field", "column". Returns matches grouped by type. It pages through content client-side, so on a very large site it scans the first ~1200 of each type and says so in `note`; once you know the exact name, prefer `graphql_query` or `where_used`.server_infoReport the connected Tableau environment: server URL, site, product & REST API version, which Metadata API endpoint is in use, the auth method, and whether external-asset (Data Management / Catalog) lineage appears available. Good first call to confirm the connection and understand what lineage depth to expect.
Amcharts5 tools 12
list_chart_typesList all amCharts 5 chart types with their categories and reference file namesget_chart_referenceGet the full reference documentation for a specific amCharts 5 chart type. Use list_chart_types first to see available types.get_core_referenceGet the core amCharts 5 reference (SKILL.md) — covers setup, colors, themes, legends, tooltips, events, data, adapters, disposal, and common pitfalls. Read this first before any chart-specific reference.search_docsSearch the curated amCharts 5 skill docs (SKILL.md + chart references) for a keyword or topic, returning matching sections ranked by relevance. NOTE: by default this scans ONLY the skill layer. The per-class API reference and per-setting DEFAULTS (e.g. tooltip background cornerRadius, axis tick `visible` default, cursor line strokeDasharray) live in the extended docs — pass scope:'all' here (which also searches the code examples), or use search_all / get_api_reference / get_doc, to reach them.get_sectionGet the FULL text of one section of a doc by heading — use it to expand a truncated search_docs / search_all result. `file` accepts the source label exactly as search results print it ('skill/SKILL.md', 'skill/xy', 'extended/charts/xy-chart/cursor', 'reference/xycursor') as well as a bare skill file name ('SKILL', 'xy', 'map').get_quick_startGet a quick-start template for a specific chart type — a minimal working example ready to customize.search_allSearch across ALL amCharts 5 content: skill references, full documentation, and code examples. Use this for broad searches across everything.get_docGet a full documentation page — an extended doc by path, or a skill file by 'skill/<name>'. Accepts the source label exactly as search_docs / search_all print it. Use search_all first to find the right path.get_api_referenceGet the per-class API reference for an amCharts 5 class — the class page PLUS its settings table (with DEFAULTS) and, optionally, its private/read-only settings. This is the authoritative source for exact setting names and default values (e.g. tooltip background cornerRadius, axis tick `visible` default). Pass a class name in any casing, e.g. 'XYCursor', 'Tooltip', 'PieSeries', 'AxisRendererX'.list_examplesList all available amCharts 5 code examples, optionally filtered by category.get_exampleGet the full code for a specific amCharts 5 example/demo. Use list_examples or search_all to find the path.list_geodataList amCharts 5 geodata (map) files with each one's CDN path, script global name and ES module import: world maps, continents, every country map, regional packs (US states and counties, Canada, Mexico) and the US congressional-district packs, which are versioned per Congress (congressional120 = 120th Congress is the newest). Also the data/countries2 and lang/* helper files. Use it before writing map code instead of guessing a file or global name.
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 Graphql MCP
{
"mcpServers": {
"tableau-graphql-mcp": {
"command": "uvx",
"args": [
"tableau-graphql-mcp"
],
"env": {
"TABLEAU_SERVER": "YOUR_TABLEAU_SERVER_HERE",
"TABLEAU_SITE_CONTENT_URL": "YOUR_TABLEAU_SITE_CONTENT_URL_HERE",
"TABLEAU_PAT_NAME": "YOUR_TABLEAU_PAT_NAME_HERE",
"TABLEAU_PAT_SECRET": "YOUR_TABLEAU_PAT_SECRET_HERE",
"TABLEAU_AUTH_TOKEN": "YOUR_TABLEAU_AUTH_TOKEN_HERE",
"TABLEAU_COOKIE": "YOUR_TABLEAU_COOKIE_HERE",
"TABLEAU_TIMEOUT": "YOUR_TABLEAU_TIMEOUT_HERE",
"TABLEAU_API_VERSION": "YOUR_TABLEAU_API_VERSION_HERE"
}
}
}
}
Amcharts5
{
"mcpServers": {
"amcharts5": {
"command": "npx",
"args": [
"-y",
"@amcharts/amcharts5-mcp"
]
}
}
}
Frequently asked questions
Tableau Graphql MCP is categorized under Data Visualization and uses a local stdio subprocess. Amcharts5 belongs to Data Visualization and uses a local stdio subprocess. Pick Tableau Graphql MCP for data visualization work and Amcharts5 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 Graphql MCP has no declared pricing — check the project's own site. Amcharts5 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-graphql-mcp and amcharts5 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Tableau Graphql MCP has a quality signal of 57/100 (Good) with 2 views, 0 installs and 1 GitHub stars. Amcharts5 has 65/100 (Great) with 0 views, 0 installs and 8 GitHub stars.