Skip to content

Boreon MCP Layer

One semantic MCP layer over all three.

The layer connects to your Tableau Server or Tableau Cloud site, Databricks and Snowflake through their own APIs. It learns how your Tableau fields map to warehouse columns and keeps that map current. It only writes when you ask, and every write is logged.

Ask Tableau Anything

One layer over your whole Tableau environment.

People ask in natural language. The Boreon MCP Layer turns each question into reads against Tableau's own APIs and brings the answer back into the chat. The model underneath is yours to choose.

Your people

  • Executives
  • Analysts
  • Site admins
  • In six languages

Boreon MCP Layer

  • Natural-language chat
  • Answers in line
  • Governance scans
  • Site operations

Your LLM: Swiss-hosted, Claude, OpenAI or your endpoint

Tableau Server or Tableau Cloud

  • REST API
  • VizQL Data Service
  • Metadata API
  • TSM, on Tableau Server

Publish, the one write

One layer that speaks every platform.

The layer reads each side through its own APIs and keeps a map of how Tableau fields line up with warehouse columns. It only writes when you ask, and it logs every write.

Tableau

  • Tableau Server or Tableau Cloud, your own site
  • Workbooks and dashboards (.twb / .twbx)
  • Published data sources (.tds)
  • Tableau Prep flows (.tfl)
  • VizQL Data Service and the Metadata API
  • PAT, JWT or a central service account

Boreon MCP Layer

Behind the Data & AI Portal

Databricks

  • Your workspace and Unity Catalog
  • Unity Catalog tables and SQL warehouses
  • AI/BI dashboards, with Genie built in
  • Materialized views from Prep flows
  • Statement Execution API for every query
  • PAT, OAuth or a service principal

Snowflake

  • Your account, databases and roles
  • Databases, schemas and virtual warehouses
  • Streamlit in Snowflake apps
  • Dynamic tables from Prep flows
  • SQL API for every query
  • Key pair, OAuth or a PAT

Six engines behind one chat.

Migrate DBX Platform Latency Calls & Uptime to Databricks

  1. Agentic chat

    Ask in natural language. You see what it is doing as it works, and answers come back as live tables and charts.

    Took the request in natural language

  2. Semantic layer

    Tableau fields mapped to Databricks and Snowflake columns once, then kept current.

    Matched Tableau fields to Databricks columns

  3. Lineage

    Traces every dashboard back through its data source and Prep flow to the column.

    Found the Prep flow behind the workbook

  4. Migration engine

    Plans the move of each workbook, dashboard and Prep flow from Tableau Server or Tableau Cloud, then carries it out.

    Built the view first, then the dashboard

  5. Fidelity engine

    Checks the warehouse's numbers against Tableau's, row by row, through the VizQL Data Service.

    41 of 41 rows match Tableau

  6. Governance

    Read-only until you say otherwise. Your SSO roles carry through, and every write is logged.

    Every write logged under your SSO roles

Your LLM, Your Rules

Each task on its own model.

The platform routes four kinds of work separately. Keys are encrypted at rest, and every routing change is audited.

ClaudeAnthropicGPTOpenAIAnyYour endpoint
Chat
Drafts
Escalation
Classify
Illustration · sample data

The Portal That Stays

For everyone from analysts to executives.

People who have never written SQL get live tables and charts by asking. And because the layer knows Tableau, Databricks and Snowflake, the portal comes with you when you move from Tableau Server to Tableau Cloud, and keeps answering from all three.

People see what they are allowed to see.

SSO roles carry through to both warehouses, and the layer is read-only until you ask it to write. Every write is logged.

Signed in through your SSO

Which region had the most failed calls last week?

RegionFailed calls
eu-central 97Not in this role
Illustration · sample data

Einstein Trust Layer

Five protections, on every call.

The Einstein Trust Layer sits between the Boreon MCP Layer and the model. Every call takes the same path, in the same order, every time.

What you see

How did Maria Keller's territory do last quarter?

Maria Keller's territory grew 12%, led by two renewals.

Einstein Trust Layer

  1. Grounded
  2. Masked
  3. Zero data retention
  4. Toxicity checked
  5. Audited

What the model sees

How did [PERSON_1]'s territory do last quarter? + 14 records you may see

[PERSON_1]'s territory grew 12%, led by two renewals.

Once it answers, the model keeps none of it.

Illustration · sample data
  1. 01

    Grounded in what you may see

    The prompt is grounded in your org's data, and only in the records the person asking is allowed to see.

  2. 02

    Personal data masked

    Names, email addresses and other personal details become placeholders before the prompt reaches a model.

  3. 03

    The model keeps nothing

    Zero data retention: the model provider stores none of the prompt and none of the answer.

  4. 04

    Toxicity checked

    Every answer is scored for toxicity on its way back, before anyone reads it.

  5. 05

    Audited in Data 360

    The whole exchange is written to an audit trail in Data 360, so it can be reviewed later.

Agentforce Agent

When a question needs Tableau, Agentforce asks ours.

Your people talk to Agentforce inside Salesforce. When the answer lives in Tableau, the agent asks the Boreon MCP Layer, which reads your Tableau Server or Tableau Cloud site and does the Tableau Next work.

Where It Lives

Every piece stays on your side.

Outside your cloud

Your Azure VNet or AWS VPC · private subnet

Boreon MCP ServerYour central LLM portal

Your platforms

Hover or tap any part to trace what it talks to.

  • WAF edge

    Caddy with OWASP Coraza rules in front of everything.

  • MCP server

    Chat, migrations and fidelity checks in one set of containers.

  • Postgres + pgvector

    Knowledge, the audit trail and secrets, behind your firewall.

  • Your OpenAI keys

    Azure OpenAI or OpenAI, on your own keys and your own account.

  • Your storage

    Backups land in your own S3 or Blob storage.

  • Your SSO

    Entra ID, Okta or any OIDC provider. Roles carry through to both warehouses.

The same layer, every step of the way.

The layer already knows Tableau, Databricks and Snowflake. When you move from Tableau Server to Tableau Cloud, it comes with you: the same questions, the same semantic model, and Databricks and Snowflake still feeding Tableau.

Today, on Tableau Server
After the move to Tableau Cloud

Which Tableau dashboard would you start with?

Start there. We'll put the layer over it and answer its questions in natural language, and if you ever want it on another platform too, every number is checked against Tableau first.