Metabase vs Tableau MCP

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

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

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

Which MCP server should you choose?

Metabase logoChoose Metabase when

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

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMetabase logoMetabaseTableau MCP logoTableau MCP
CategoryData VisualizationData Visualization
Quality signal41/100 · Fair51/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNot declared
PricingFreeNot declared
Required env varsNone listedSERVERSITE_NAMEPAT_NAMEPAT_VALUE
Verified ownerCommunity listingCommunity listing
GitHub stars49,838357
Directory activity 1 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Metabase tools

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

Tableau MCP 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.

Metabase

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

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"
      }
    }
  }
}

Frequently asked questions

Metabase is categorized under Data Visualization and uses an install path we have not confirmed yet. Tableau MCP belongs to Data Visualization and uses a local stdio subprocess. Pick Metabase for data visualization work and Tableau MCP 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.

Metabase is listed as free. Tableau MCP has no declared pricing — check the project's own site. 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 metabase and tableau-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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