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 fieldTypeform MCPShortlist candidatetableauMCP100 Recommended
Task fit
Best for
  • Create and operate Typeform forms, automations, contacts, and analytics
  • Typeform users who need to create and operate typeform forms, automations, contacts, and analytics.
  • Business-intelligence discovery and analysis using authorized Tableau content.
Not ideal for
  • The server exposes destructive form/contact operations and publishing actions. Feature access is plan-dependent. Use the correct regional endpoint for EU data-center accounts.
  • Teams outside the publisher ecosystem or without least-privilege credentials
Avoid when
  • The server exposes destructive form/contact operations and publishing actions. Feature access is plan-dependent. Use the correct regional endpoint for EU data-center accounts.
  • The connected identity is broader than the task requires
  • Tool calls cannot be reviewed before consequential mutations
Provenance
Provenance details

First-party MCP

Typeform · Publisher source ↗

First-party MCP

ecosystem:tableau · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Sep 24, 2026

Package: Not documented

Popularity evidence
GitHub starsNot documented

345

GitHub stars · checked 2026-09-24T04:14:47.698000Z

Client coverage
Client coverage detailsNot documented
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
AuthenticationOAuth 2.0. Typeform documents three region-specific MCP endpoints; the two EU endpoints are not interchangeable. Personal access tokens are not supported for current MCP connections.The official package documents Tableau authentication and server connection configuration.
CostNo separate MCP fee is documented. Typeform offers a free plan and paid plans; access to some MCP-backed product features is plan-dependent.The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.
PermissionsEach tool declares required scopes and product-plan access is enforced at call time. Typeform currently requires users to grant all MCP-supported scopes when connecting; users cannot customize a smaller scope set.Tableau site roles, content permissions, and connected-data policies determine what the server can return.
Data handlingNot documented in the reviewed sources. The reviewed Typeform MCP pages do not state an MCP-specific retention or training policy.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
  • Shortlist evidence is sufficient for identity, setup and task value; authenticated runtime tool-schema measurement and exhaustive security certification remain out of scope.
  • Workbook metadata and query results may expose business-sensitive information or inherited data access.
Risk contextThe MCP has broad write capability: it can create, patch, publish, duplicate and delete forms; modify themes and automations; and create/update/delete contact data and mappings. Typeform marks destructive tools that cannot be undone.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-10-192026-07-30
Candidate evidence2026-10-202026-09-24T04:25:05.554391Z

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

Read the evidence method →