Parseflow vs Tableau Graphql MCP

In-depth architectural comparison of the Parseflow 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.

Which MCP Server Should You Choose?

Choose Parseflow when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Parseflow Details

T

Choose Tableau Graphql MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: graphql_query, introspect_schema, lineage_examples.

Explore Tableau Graphql MCP Details

Feature & Specification Comparison

Specification	Parseflow Developer Tools	T Tableau Graphql MCP Developer Tools
Summary	PDF parsing server with text extraction, metadata, search, images, and TOC via MCP	Ask any Tableau lineage question, in any MCP client, through the Tableau Metadata API.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "parseflow": {
      "command": "npx",
      "args": [
        "-y",
        "npx"
      ]
    }
  }
}

{
  "mcpServers": {
    "tableau-graphql-mcp": {
      "command": "uvx",
      "args": [
        "tableau-graphql-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons