Skip to main content

MCP Configuration for Site Administrators

This page is a guide for Tableau site and server administrators who are responsible for securing and governing a Tableau MCP deployment, and for customizing MCP guardrails for your organization. It brings together the configuration surfaces most relevant to administrators and explains how they layer together.

The guidance here applies to both ways of running Tableau MCP:

  • Hosted Tableau MCP — the managed service that runs on every Tableau Cloud pod at https://mcp.tableau.com. Tableau operates the server, so you do not set environment variables. Your governance lever is Site Settings, applied per-site via the REST API.
  • Self-hosted — a server you deploy and operate yourself (for example, a fork of the repo or a self-hosted enterprise deployment). You own environment variables as your baseline, and can additionally delegate configuration through Site Settings and Request Overrides.

If you are looking for the full catalog of every setting, see Environment Variables. This page focuses on the subset that administrators typically own.

info

The quickest way to tell which surfaces apply to you: if you connect clients to https://mcp.tableau.com, you are on the hosted service and configure it through Site Settings. If you run the server yourself at a URL you own, you are self-hosted and configure it primarily through environment variables. See How configuration layers together for the order of precedence.

How configuration layers together​

Tableau MCP resolves configuration from several sources. When the same variable is set in more than one place, the higher-precedence source wins (highest to lowest):

  1. Request overrides — per-request, via the x-tableau-mcp-config HTTP header (only for the HTTP transport, self-hosted deployments). See Request Overrides.
  2. Site settings — per-site, applied to every user authenticated to that site. See Site Settings.
  3. Environment variables — server-wide defaults set by the administrator who runs the server (self-hosted only).

Self-hosted: environment variables are your baseline. Site settings and request overrides only apply to variables you have explicitly marked as overridable, so you remain in control of what can be changed downstream.

Hosted Tableau MCP: Tableau owns the environment variables and the runtime, so you cannot set or see them. Site Settings are the surface you control — they let you govern the hosted service for each of your sites without deploying anything. The rest of this page calls out, per topic, whether a control is available on the hosted service or only when self-hosting.

Environment parameters (self-hosted)​

note

This section applies only to self-hosted deployments. On the hosted service, Tableau sets these values for you; skip ahead to Governing the hosted service with Site Settings.

Environment variables (often supplied via a .env file, container environment, or your process manager) are the primary way administrators configure a deployment. The variables below are the ones administrators most commonly need to set. For everything else, see Environment Variables.

Server connection​

VariablePurpose
SERVERURL of the Tableau Cloud pod or Tableau Server.
SITE_NAMEContent URL of the site to connect to.
TRANSPORTstdio for single-user, or http for multi-user deployments.
AUTHAuthentication method (pat, direct-trust, or oauth).
tip

For any shared, multi-user deployment, run the server with TRANSPORT=http and protect it with OAuth. Non-OAuth HTTP configurations are intended only for testing/prototyping or deployments licensed and approved for usage-based licensing (UBL). See the HTTP Server page for details.

Admin-only tools​

Several tools are restricted to Tableau site administrators. They are disabled by default and must be turned on explicitly.

warning

Admin tools can read sensitive site data and, in some cases, delete content or change user site roles. Enable them only for deployments where the authenticated caller's site role can be trusted, and prefer OAuth so each caller's identity and permissions are enforced by Tableau.

Governing what tools and data are exposed​

:::tip Hosted service

Every variable in this list is also a site-overridable variable, so you can apply the same governance on the hosted service through Site Settings — for example, excluding tools or scoping content on https://mcp.tableau.com per site. See Governing the hosted service with Site Settings.

:::

Logging, telemetry, and safety​

danger

Never commit real secrets (PAT values, OAuth client secrets, connected-app keys) to source control, and do not disable log masking in a committed configuration.

Governing the hosted service with Site Settings​

Site Settings are the primary governance surface for the hosted service and an optional delegation surface for self-hosted deployments. They let you tailor a curated subset of configuration per site, applied to every user authenticated to that site, without deploying or restarting anything. See Site Settings.

:::info Hosted service

On https://mcp.tableau.com you cannot disable the service, but you can restrict what it does on your site. For example, exclude every tool group via EXCLUDE_TOOLS in Site Settings — see Admin controls for the exact REST API payload.

:::

Allowing per-request overrides (self-hosted)​

For self-hosted HTTP deployments, you can additionally let clients adjust a curated set of variables on a per-request basis via the x-tableau-mcp-config header. This is disabled by default and is not available on the hosted service. See Request Overrides.

Hosted service​

On https://mcp.tableau.com you govern the service per site through Site Settings, submitted via the Tableau MCP REST API. A conservative starting point caps result sizes and, optionally, narrows the exposed tools:

JSON
{
"mcpSiteSettings": {
"settings": [
{ "key": "MAX_RESULT_LIMIT", "value": "100" },
{ "key": "EXCLUDE_TOOLS", "value": "" }
]
}
}

Leave EXCLUDE_TOOLS empty to keep the full catalog, or list the tool groups you want to block — see Admin controls for the full-block payload. Authentication, transport, and logging are managed by Tableau on the hosted service.

Self-hosted​

A typical hardened, multi-user self-hosted configuration looks like:

SERVER=https://prod-useast-c.online.tableau.com
SITE_NAME=my-site
TRANSPORT=http
AUTH=oauth

# Turn on admin tools only if your callers are trusted site admins
ADMIN_TOOLS_ENABLED=false

# Keep secrets masked in logs
DISABLE_LOG_MASKING=false

# Constrain what can be returned
MAX_RESULT_LIMIT=100

# Request overrides off unless you explicitly need them
ALLOWED_REQUEST_OVERRIDES=

Adjust from either baseline as your governance, licensing, and security requirements dictate.