Skip to main content

HTTP Server

The Tableau MCP server can be configured to run as an HTTP server, leveraging the Streaming HTTP MCP transport. This is useful for deploying the server remotely and exposing it to multiple clients.

warning

When TRANSPORT is http, the default behavior changes to require protecting your MCP server with OAuth as a security best practice for general multi-user deployments.

Non-OAuth HTTP configurations are intended only for testing/prototyping or deployments that are licensed and approved for user-based licensing (UBL). Confirm this with your Tableau licensing and security guidance before opting out. To opt out, see the entry on DANGEROUSLY_DISABLE_OAUTH.

When TRANSPORT is http, the following environment variables can be used to configure the HTTP server. They are all optional.

AUTH​

The method the MCP server uses to authenticate to the Tableau REST APIs.

danger

For general multi-user HTTP deployments, prefer OAuth. Non-OAuth HTTP configurations such as PAT or Direct Trust are intended for testing/prototyping or deployments that are licensed and approved for UBL.

As an additional operational caveat, do not use a PAT when TRANSPORT is http if you expect simultaneous requests from multiple clients since PATs cannot be used concurrently. Signing in multiple times with the same PAT at the same time will terminate any prior session and will result in an authentication error. See Understand personal access tokens for more details.

HTTP_PORT_ENV_VAR_NAME​

The environment variable name to use for the HTTP server port.

  • Default: PORT

[Value of HTTP_PORT_ENV_VAR_NAME]​

The port to use for the HTTP server.

  • Default: 3927

SSL_KEY​

The path to the SSL key file to use for the HTTP server.

SSL_CERT​

The path to the SSL certificate file to use for the HTTP server.

CORS_ORIGIN_CONFIG​

The origin or origins to allow CORS requests from.

  • Default: true
  • Acceptable values include true, false, *, or a URL or array of URLs. See cors config options for details.