Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldSalesforce Hosted MCPMCP100 SelectedtableauMCP100 Selected
Task fit
Best for
  • Connect compatible AI clients to Salesforce's documented MCP capabilities.
  • Business-intelligence discovery and analysis using authorized Tableau content.
Not ideal for
  • Users who need a fully reviewed MCP100 recommendation today
  • Teams outside the publisher ecosystem or without least-privilege credentials
Avoid when
  • Permissions, credentials, and connected data cannot be tested with least privilege
  • The connected identity is broader than the task requires
  • Tool calls cannot be reviewed before consequential mutations
Provenance
Provenance details

First-party MCP

Salesforce · Publisher source ↗

First-party MCP

ecosystem:tableau · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Aug 14, 2026

Package: Not documented

Popularity evidence
GitHub starsNot documented

322

GitHub stars · checked 2026-08-14T18:46:26.000Z

External adoption evidenceNot documented
  • github: repository stars: 322Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details
Claude Code✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationFollow only the publisher source; credential storage, scopes, and revocation remain under review.The official package documents Tableau authentication and server connection configuration.
CostPublisher plans, API usage, infrastructure, or per-action charges may apply; MCP100 has not published a cost conclusion.The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.
PermissionsExact permissions and read/write boundaries have not completed MCP100 review.Tableau site roles, content permissions, and connected-data policies determine what the server can return.
Data handlingCandidate-specific retention, subprocess, telemetry, and model-data behavior remain review items.Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive analytics & data information.
Limitations
Tradeoffs
  • Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
  • Workbook metadata and query results may expose business-sensitive information or inherited data access.
Risk contextUse a test account, least privilege, read-only controls where available, and explicit approval for mutations.Workbook metadata and query results may expose business-sensitive information or inherited data access. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review.
Evidence date
Editorial review2026-07-242026-07-30
Candidate evidence2026-07-30T19:00:00.000Z2026-08-14T18:46:26.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →