Tableau MCP Integration
Tableau's open-source and hosted MCP options, their stated status, and how to choose tool groups and permissions for AI clients.
People already ask questions of dashboards; with MCP they can ask an AI client to find the right workbook, explain a view or summarise a Pulse metric. Tableau publishes its own MCP server in two forms. This page explains both, quotes the stated status carefully, and sets out how we would control which tools are available.
The business use case
- Business users find the right published view and get a plain-language summary instead of browsing projects.
- Analysts inspect data sources and workbook metadata from an IDE or AI client.
- Administrators answer content and usage questions faster.
What Tableau offers
Tableau MCP options, as documented
| Option | How it runs | Authentication | Platforms |
|---|---|---|---|
| Tableau MCP (open source) | Self-hosted, over stdio or HTTP; npm @tableau/mcp-server; Apache-2.0; "Tableau Supported" badge | Personal access token (PAT) | Tableau Cloud and Tableau Server |
| Hosted Tableau MCP | https://mcp.tableau.com | OAuth 2.1, per user | Tableau Cloud only, on any SKU; Server customers must self-host |
| Tableau Next server (analytics/tableau-next) | Salesforce-hosted MCP | Salesforce Hosted MCP authentication | Semantic models, KPIs and analytics questions; no status label stated |
Tool groups and controls
Hosted Tableau MCP organises tools into groups: admin-insights, authoring, content, content-exploration, datasource, flow, insights, jobs, knowledge, mcp-apps, project, pulse, tasks, token-management, users, view and workbook. The authoring and token-management groups suggest write tools exist. Pulse Insight Briefs and Knowledge require Tableau+.
Admins can block tool groups with the EXCLUDE_TOOLS site setting, but cannot disable the hosted service. That makes the exclusion list your main control on Tableau Cloud, so set it before users connect.
Vendor server first
Tableau's server belongs to Tableau, and we evaluate it first. We only propose a GeekMidst adapter for gaps, for example combining Tableau answers with CRM context in one tool, and none exists today. The tool policy below is a proposed design; we validate the APIs, edition and permissions for each implementation.
Proposed tool-group policy
| Tool group | Purpose | Read/write | Approval needed |
|---|---|---|---|
| content-exploration, view, workbook | Find and describe published content | Treated as read; validated per tool | No |
| datasource | Inspect data source metadata | Treated as read; validated per tool | No |
| pulse, insights | Summarise metrics | Treated as read; validated per tool | No |
| authoring | Create or change content | Likely write; validated per tool | Excluded at first; later with owner approval |
| token-management, users | Manage tokens and users | May include writes; validated per tool | Excluded via EXCLUDE_TOOLS |
| admin-insights, jobs, tasks, flow | Admin and operations | Mixed | Admin group only, reviewed separately |
Authentication and access control
- Hosted: OAuth 2.1 per user, so each person sees what their Tableau permissions allow. This is the simplest secure option for Tableau Cloud.
- Self-hosted: the server authenticates with a PAT. Keep the PAT in server-side configuration, scope it to a dedicated user with minimal site role, rotate it, and never paste it into a chat. A shared PAT means every caller acts as that one user, so prefer hosted where you can.
- HTTP self-hosting: run it behind your own authentication; the MCP spec expects HTTP servers that support auth to follow its OAuth rules.
Privacy, limits and auditability
Views can show row-level data. Decide which projects an AI client may reach, and check with your legal adviser on the data protection rules that apply to you. Our sources state no MCP rate limits, so check Tableau's limits. For audit, per-user OAuth keeps activity attributable to the person; with a self-hosted PAT, add logging in the host.
Errors, environments and testing
Test against a non-production site or project first. Confirm that excluded groups do not appear in tools/list, that users without access are refused, and that failures report a reason. The MCP Inspector CLI can list tools and call them with test arguments.
Licensing
Hosted Tableau MCP is for Tableau Cloud on any SKU; Pulse Insight Briefs and Knowledge need Tableau+. Tableau Next is sold standalone, in the Tableau+ bundle, or included in certain Salesforce editions (Core, Advanced, Max).
Available today vs proposed
| Item | Status |
|---|---|
| Tableau MCP (open source, self-hosted) | Published by Tableau; no release stage stated |
| Hosted Tableau MCP | GA likely but not confirmed (conflicting Tableau page) |
| Tableau Next hosted server | Documented by Salesforce; no status label |
| GeekMidst tool-group policy and adapter | Proposed design |
Related
Tableau and CRM Analytics consulting
Analytics design and adoption
→Analytics and reporting architecture
How analytics fits the stack
→Tableau
Product overview
→MCP integration overview
All vendor servers and their status
→Questions we hear
Is hosted Tableau MCP generally available?
Can we use hosted Tableau MCP with Tableau Server?
Can we switch hosted Tableau MCP off?
Does Tableau Next use the same server?
Sources
Choose the right Tableau MCP set-up
Tell us how your teams use Tableau today. We can recommend hosted or self-hosted, and an exclusion list to start with.
