Model Context Protocol server for Rollbar
Nothing to run from here
Biztory Tableau Knowledge is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
97/100
trust score
4
downloads a day
local
runs on your machine
165
downloads in 30d
What it does
Search, explore and enrich the Tableau Knowledge graph, and port it to Apache Ossie (OSI).
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'TABLEAU_SERVER=${TABLEAU_SERVER}' --env 'TABLEAU_SITE_CONTENT_URL=${TABLEAU_SITE_CONTENT_URL}' --env 'TABLEAU_PAT_NAME=${TABLEAU_PAT_NAME}' --env 'TABLEAU_PAT_SECRET=${TABLEAU_PAT_SECRET}' --transport stdio biztory-tableau-knowledge-mcp '--' uvx biztory-tableau-knowledge-mcp
# 2 — ask your agent for something these tools do
# server_info, search_nodes, get_node and 20 more
It needs TABLEAU_SERVER, TABLEAU_SITE_CONTENT_URL, TABLEAU_PAT_NAME, TABLEAU_PAT_SECRET: this reads them from your environment, so export them first.
Biztory Tableau Knowledge costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Biztory Tableau Knowledge as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads TABLEAU_SERVER (https://<pod>.online.tableau.com (Tableau Knowledge is a Tableau Cloud feature)), TABLEAU_SITE_CONTENT_URL (Site content-url slug (the part after /#/site/)), TABLEAU_PAT_NAME (Personal Access Token name), TABLEAU_PAT_SECRET (Personal Access Token secret (the whole string)) from your environment each time it starts the server, so the value stays out of its config: export them in your shell profile (macOS, Linux), or run setx TABLEAU_SERVER …, setx TABLEAU_SITE_CONTENT_URL …, setx TABLEAU_PAT_NAME …, setx TABLEAU_PAT_SECRET … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'TABLEAU_SERVER=${TABLEAU_SERVER}' --env 'TABLEAU_SITE_CONTENT_URL=${TABLEAU_SITE_CONTENT_URL}' --env 'TABLEAU_PAT_NAME=${TABLEAU_PAT_NAME}' --env 'TABLEAU_PAT_SECRET=${TABLEAU_PAT_SECRET}' --transport stdio biztory-tableau-knowledge-mcp '--' uvx biztory-tableau-knowledge-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: TABLEAU_SERVER — https://<pod>.online.tableau.com (Tableau Knowledge is a Tableau Cloud feature); TABLEAU_SITE_CONTENT_URL — Site content-url slug (the part after /#/site/); TABLEAU_PAT_NAME — Personal Access Token name; TABLEAU_PAT_SECRET — Personal Access Token secret (the whole string). You set them in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
23 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Report the connected Tableau site and its knowledge graphs: server URL, site, product version, auth method, whether Tableau Knowledge is available, and every graph (id, name, status, is_primary). Good first call: it confirms the connection and gives the graph ids the other tools accept as…
Takes no parameters.
Find graph nodes by MEANING (semantic search), not exact name: "revenue" can match a field named "Net Sales". Returns ranked matches with a 0-1 score; when a semantic statement matched, it is shown under the node's semantic_statements.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| node_type | string | no | — |
| scope_id | string | no | — |
| limit | integer | no | — |
| threshold | number | no | — |
| graph_id | string | no | — |
Get one node with its properties, its semantic statements (the business context attached to it), and the child nodes it points to (connected_nodes, each with the edge type).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| node | string | yes | — |
| include_children | boolean | no | — |
| graph_id | string | no | — |
List the edges around one node, each with its direction (outgoing/incoming) and the node on the other end. One hop only; use lineage for the wider neighborhood.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| node | string | yes | — |
| edge_type | string | no | — |
| direction | string | no | — |
| graph_id | string | no | — |
The lineage neighborhood of a node: every node reachable within 10 steps, upstream AND downstream, along lineage/dependency edges (LINEAGE, DEPENDS_ON), e.g. a data source and the workbooks built on it. Answers "where does this come from?" and "what uses it?".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| node | string | yes | — |
| graph_id | string | no | — |
What breaks if this changes: every asset that depends on the node, directly OR transitively (up to 10 steps, following DEPENDS_ON), e.g. the calcs, sheets, dashboards and workbooks downstream of a column. The node itself is not included.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| node | string | yes | — |
| graph_id | string | no | — |
List the published data sources and workbooks connected to the knowledge graph, i.e. what the graph has been built from. node_type "PDS" or "WORKBOOK" narrows it; omit for both.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| node_type | string | no | — |
| graph_id | string | no | — |
List semantic contexts: the business statements (definitions, rules, caveats) attached to the graph. Includes user-managed (SEMANTIC_CONTEXT, editable) and Tableau-managed (SEMANTIC_CONTEXT_EXTERNAL, read-only) contexts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| node | string | no | — |
| is_global | boolean | no | — |
| graph_id | string | no | — |
Graph-health report: a 0-100 health_score, coverage metrics (e.g. how many nodes carry semantic context), graph stats, and concrete improvement suggestions (each with severity, recommended_action and the target node ids), grouped by category and topic.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pds_id | string | no | — |
| severity | string | no | — |
| suggestion_type | string | no | — |
| limit | integer | no | — |
| graph_id | string | no | — |
WRITE: attach business context (one or more statements, 5-1000 characters each) to the knowledge graph, e.g. "Net Sales excludes returns and is reported in EUR."
| Parameter | Type | Required | Notes |
|---|---|---|---|
| statements | array | yes | — |
| target_node_id | string | no | — |
| is_global | boolean | no | — |
| name | string | no | — |
| graph_id | string | no | — |
WRITE: change a user-managed semantic context (ctx_id, e.g. "semctx:<uuid>"). Only what you pass changes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ctx_id | string | yes | — |
| statements | array | no | — |
| name | string | no | — |
| attach_to | string | no | — |
| make_global | boolean | no | — |
| graph_id | string | no | — |
WRITE: delete a user-managed semantic context and its statements. Only semantic contexts created through Tableau Knowledge can be deleted; ids of other nodes are ignored, and Tableau-managed (SEMANTIC_CONTEXT_EXTERNAL) contexts are refused.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ctx_id | string | yes | — |
| graph_id | string | no | — |
Export a published data source's semantic model to Apache Ossie (formerly OSI) YAML, the vendor-neutral format that Snowflake, dbt, Power BI, Databricks, Tableau Next and other tools convert from. Returns ossie (the YAML text, to save as file_name), summary, validation and losses (what…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| datasource | string | yes | — |
| include_hidden | boolean | no | — |
| default_aggregation_metrics | boolean | no | — |
| graph_id | string | no | — |
Validate an Apache Ossie (formerly OSI) model, given as YAML or JSON text, against the official JSON Schema (0.2.0.dev0, bundled) and the spec's semantic rules: duplicate names, keys and relationship columns that are not declared fields, unknown datasets, qualified names in dataset-scoped metrics.…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document | string | yes | — |
| model_name | string | no | — |
Bring the business meaning of an Apache Ossie (formerly OSI) model into Tableau Knowledge as semantic contexts. WRITES only when apply is true; by default it returns the PLAN.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document | string | yes | — |
| target_datasource_id | string | no | — |
| model_name | string | no | — |
| apply | boolean | no | — |
| include_definitions | boolean | no | — |
| scope | string | no | — |
| graph_id | string | no | — |
Reference for Apache Ossie (formerly Open Semantic Interchange, OSI), the open standard for semantic models: what it is and its versions, the object model and rules, expressions and dialects, how Tableau maps onto it, relationships, ai_context, extensions, validation, the converters for other…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | — |
Check a Tableau Business Preferences file (the "# rule" lines Tableau's agent reads before it answers) so every line is one the agent will actually follow. Call it with no text first to get the rulebook: format, limits, wording rules, workbook preparation and how to test.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | no | — |
| target | string | no | — |
| product | string | no | — |
| graph_id | string | no | — |
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Biztory Tableau Knowledge or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 97 / 100
Release 0.4.0 · scanned 5 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score97
Findings0 threat · 1 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digest58070423be2723bd609bb9d98bf0b75205e29dd61a78e42cf9048615bce3db74
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (23 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| server_info | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| search_nodes | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_node | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_edges | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| lineage | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| impact_analysis | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_sources | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| search_semantic_contexts | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| graph_health | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| create_semantic_context | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| update_semantic_context | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| delete_semantic_context | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| create_semantic_context_from_document | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| add_sources | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| remove_sources | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| create_graph | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| update_graph | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| ask_tableau_agent | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| export_to_ossie | external-sinkuntrusted-input | external-sink: keyword "export_to"; untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| validate_ossie | no tags | |
| import_from_ossie | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| ossie_guide | no tags | |
| check_business_preferences | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest58070423be2723bd
Scanned2026-11-05
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.4.0. Pin a release below and the command asks for exactly that one.
0.4.0
4 Nov 2026
latestNo release note was published with this version.
0.3.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Biztory Tableau Knowledge can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.