tableau

tableau is an MCP server for Claude Code from daddia/claude-for-strategy. Its token cost is not measured, scanned A, original, MIT.

A connection to Tableau Cloud, a service for viewing data dashboards and workbooks. It lets the agent read metrics and workbook context according to the user's Tableau permissions.

In plain words
What is it for?
Checking Tableau Cloud metrics and reviewing workbook context during analysis or planning.
Why use it?
It avoids switching between the coding agent and Tableau to check dashboard data or understand a workbook. Access remains limited to what the user can view.

MCP server for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: listed in a Claude config.

Part of the balanced-scorecard plugin — 7 skills, 1 agent, 13 MCP servers shipped together

One of 13 entries in .mcp.json — they are configured in one file and arrive together.

Good fit Checking Tableau Cloud metrics and reviewing workbook context during analysis or planning.

Compare 6 mcp servers from other repositories ↓
Install with agentmods
npx agentmods add mcp/daddia/claude-for-strategy/tableau
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/daddia/claude-for-strategy

Made for: Claude Code.

Or install balanced-scorecard, the plugin that ships this one along with the rest of its 7 skills, 1 agent, 13 MCP servers.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for tableau

README.md
[![agentmods](https://agentmods.dev/badge/mcp/daddia/claude-for-strategy/tableau.svg)](https://agentmods.dev/mcp/daddia/claude-for-strategy/tableau)
Your own site
<a href="https://agentmods.dev/mcp/daddia/claude-for-strategy/tableau"><img src="https://agentmods.dev/badge/mcp/daddia/claude-for-strategy/tableau.svg" alt="Measured on agentmods" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

tableau scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

balanced-scorecard/.mcp.json · 8 lines

What it actually says

{
  "tableau": {
    "type": "http",
    "url": "https://mcp.tableau.com",
    "title": "Tableau",
    "description": "Read Tableau Cloud metrics and workbook context — OAuth per user with Tableau permissions enforced."
  }
}
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 8 lines scan A f024ba3ddc0a

Subscribe to this mod's changes

tableau is an MCP server published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.