Tableau MCP vs Metabase

A side-by-side look at the Tableau MCP and Metabase MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Tableau MCP logoTableau MCPData Visualization · Local subprocess (stdio)Tableau's official MCP Server. Helping agents see and understand data.51GoodAuth: not declaredMetabase logoMetabaseData VisualizationLets AI clients search, explore, query, and visualize data in a Metabase instance.41FairAuth: not declared

Verdict: choose Tableau MCP for data visualization work as a local process; choose Metabase for data visualization. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Tableau MCP logoChoose Tableau MCP when

  • You need dedicated capabilities in the Data Visualization domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: SERVER, SITE_NAME, PAT_NAME, PAT_VALUE.
Explore Tableau MCP

Metabase logoChoose Metabase when

  • You need dedicated capabilities in the Data Visualization domain.
Explore Metabase

Feature & specification comparison

Rows where the two servers differ are marked.

SpecTableau MCP logoTableau MCPMetabase logoMetabase
CategoryData VisualizationData Visualization
Quality signal51/100 · Good41/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNot declared
PricingNot declaredFree
Required env varsSERVERSITE_NAMEPAT_NAMEPAT_VALUENone listed
Verified ownerCommunity listingCommunity listing
GitHub stars35749,838
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Tableau MCP tools

No tool names declared yet. Check the project README from the listing page.

Metabase tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Tableau MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "tableau-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tableau/mcp-server@latest"
      ],
      "env": {
        "SERVER": "YOUR_SERVER_HERE",
        "SITE_NAME": "YOUR_SITE_NAME_HERE",
        "PAT_NAME": "YOUR_PAT_NAME_HERE",
        "PAT_VALUE": "YOUR_PAT_VALUE_HERE"
      }
    }
  }
}

Metabase

No confirmed install command for Metabase yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Tableau MCP is categorized under Data Visualization and uses a local stdio subprocess. Metabase belongs to Data Visualization and uses an install path we have not confirmed yet. Pick Tableau MCP for data visualization work and Metabase for data visualization.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Metabase has no confirmed install command yet — follow its own setup instructions.

Tableau MCP has no declared pricing — check the project's own site. Metabase is listed as free. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add tableau-mcp and metabase as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Tableau MCP has a quality signal of 51/100 (Good) with 0 views, 0 installs and 357 GitHub stars. Metabase has 41/100 (Fair) with 1 views, 0 installs and 49,838 GitHub stars.