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.

Proof and fidelity Book a working session

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 plain words. You see what it is doing as it works, and answers come back as live tables and charts.

    Took the request in plain words

  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

It stays when Tableau goes.

Because the layer already knows all three platforms, retiring Tableau Server or Tableau Cloud doesn't break anything. The same layer keeps serving both warehouses.

During the migration
After Tableau retires
See the portal

Which Tableau dashboard would you move first?

Start there. It becomes the first thing we move, checked number by number against Tableau, and the portal it lands in stays yours.

Book a working session See it live at ai.boreon.com