Claude Task Master vs Tableau Graphql MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
Claude Task Master vs Tableau Graphql MCP
In-depth architectural comparison of the Claude Task Master and Tableau Graphql MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Claude Task Master
Developer Tools · Local stdio
Quality: 61/100 (Good) | Auth: API Key required
Tableau Graphql MCP
Developer Tools · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Claude Task Master if you need specialized Developer Tools tools running via a local process. Choose Tableau Graphql MCP if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Claude Task Master when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: ANTHROPIC_API_KEY, OPENAI_API_KEY, GOOGLE_API_KEY, PERPLEXITY_API_KEY, XAI_API_KEY, OPENROUTER_API_KEY, MISTRAL_API_KEY, TASK_MASTER_TOOLS.
AI-powered task management system for AI-driven development. Features PRD parsing, task expansion, multi-provider support (Claude, OpenAI, Gemini, Perplexity, xAI), and selective tool loading for optimized context usage.
Ask any Tableau lineage question, in any MCP client, through the Tableau Metadata API.
Claude Task Master is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Tableau Graphql MCP belongs to Developer Tools using local stdio subprocess. Select Claude Task Master when you need capabilities focused on developer tools and Tableau Graphql MCP when you require tools for developer tools.
Live schema introspection: list entry points, or a type's exact fields.
lineage_examples
A schema cheat-sheet plus 28 curated question-to-GraphQL templates (8 categories).
where_used
Which workbooks/datasources use given column / field / table names (robust one-hop core-lineage resolution).
impact_analysis
Full transitive **multi-hop** blast radius of a column/field/table: every dependent field, plus affected sheets, dashboards, workbooks, and **owners to notify**.
search_content
Find content whose **name contains** a term (case-insensitive substring), across workbooks, datasources, tables (and optionally fields/columns), with coverage numbers.
server_info
Connected server, site, versions, endpoint, auth, and whether Catalog lineage is available.