Skip to content

Ask Tableau anything. Get it in line.

The Boreon MCP Layer sits over your Tableau Server or Tableau Cloud site and turns it into a conversation. Ask in plain words, and live tables, your own views, lineage, logs and answers arrive right inside the chat, on the LLM you choose.

  • Read-only by default
  • TSM aware
  • PII and PHI scans
  • Bring your own LLM
  • Six languages

Reading Tableau · Superstore · VizQL Data Service · read-only

Which region led sales, and which one should we watch?

West leads with $725K in sales. Central has the thinnest margin, at 7.9%, and is the region to watch.

Sales by region
RegionSalesMargin
West$725K14.9%
East$679K13.5%
Central$501K7.9%
South$392K11.9%
  • Open in Tableau
  • Publish to Tableau
  • Drill into Central
Illustration with Tableau’s Superstore sample data.

One message. A boardroom answer.

The Boreon MCP Layer gives leaders a calm place to talk with Tableau Server or Tableau Cloud. A new question no longer waits on a new dashboard.

  • Live numbers. Every figure comes from a live VizQL query against your site.
  • The whole answer. The chart, the table and the plain-words reading arrive together, in one reply.
  • The next step. Open the Tableau view, publish the result to Tableau, or drill further in.
  • Six languages. English, Japanese, German, French, Italian and Russian.

Everything happens in line

The Boreon MCP Layer reads Tableau Server or Tableau Cloud through Tableau’s own APIs, read-only, and brings each answer into the conversation.

Live data tables

Ask in plain words or paste SQL. The query runs over the VizQL Data Service and comes back as a live table in the chat.

Your own views

Your Tableau views, embedded in the conversation and signed in as you.

Pulse metrics

Tableau Pulse metrics arrive in line, with Pulse’s own Ask agent beside them.

Lineage

From Prep flow to data source to workbook, traced in line when you ask where a number comes from.

Site logs

Failed jobs, explained in plain words: which extract refresh or subscription failed, and why.

Publish to Tableau

Any table goes back to your site as a workbook, and never as a second data source. It is the one write, and it happens only when you ask.

The screen your team signs in to

One field, four presets and a conversation that remembers. Every answer ends with the next step to take.

The Data & AI Portal home screen, signed in: a welcome message, one question field and four presets, Scan for PII/PHI Risks, Check my site logs, Governance Snapshot and Sync my data sources.
The real Data & AI Portal, signed in, with the Boreon MCP Layer behind it. The four presets start a PII and PHI scan, a look at the site logs, a governance snapshot and a data source sync.

Run and govern Tableau without the guesswork

For site admins and governance teams, the Boreon MCP Layer reads what used to live in separate consoles.

  • TSM, read for you. On Tableau Server, process status on every node and the errors that matter.
  • Failed jobs, explained. Extract refreshes and subscriptions, in plain words.
  • Every workbook, governed. PII, PHI and leaked credentials, found in one question.
  • Answers from the docs. How-to answers grounded in about 3,000 pages of official Tableau help.

See governance and site operations

One layer over your whole Tableau site

The Boreon MCP Layer turns plain-words questions into reads against Tableau’s own APIs, on the LLM you choose.

  • Tableau’s own APIs. The REST API, the VizQL Data Service and the Metadata API, and TSM on Tableau Server.
  • Your people. Executives, analysts and site admins, each asking in the words they already use.
  • Your LLM underneath. Swiss-hosted open models, Claude, OpenAI or any OpenAI-compatible endpoint, chosen per task.

Every call the layer makes to Tableau is a read, except the one workbook you ask it to publish.

The rest of the Boreon MCP Layer for Tableau

Two more pages, and a team ready to answer your own question.

Questions and answers

What Tableau teams ask first.

Does it work with Tableau Server and Tableau Cloud?
Yes. The Boreon MCP Layer reads Tableau Server or Tableau Cloud through Tableau’s own APIs: the REST API, the VizQL Data Service and the Metadata API, and on Tableau Server, TSM.
Does it change anything on our site?
It reads your site read-only. The one write is a workbook you explicitly ask it to publish, and it never adds a second data source.
Who is it for?
Executives who want a straight answer, analysts who want live tables, and site admins and governance teams who want the site explained, in English, Japanese, German, French, Italian or Russian.
Which LLM does it use?
The one you choose, per task: Infomaniak’s Swiss-hosted open models such as Qwen and Gemma by default, Anthropic Claude, OpenAI, or any OpenAI-compatible https endpoint.
Where does it run?
Self-hosted on your own infrastructure as a signed offline bundle, or hosted by us in Switzerland.
Is the answer on this page real?
It is an illustration built on Tableau’s Superstore sample data. In a demo, we answer a question from your own site, live.

Ask your own Tableau, live.

Bring one question from your Tableau Server or Tableau Cloud site. The Boreon MCP Layer will answer it in line, on the model you choose.