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.
| Evidence field | Typeform MCPShortlist candidate | tableauMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| 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 stars | Not documented | 345 GitHub stars · checked 2026-09-24T04:14:47.698000Z |
| Client coverage | ||
| Client coverage details | Not documented | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | OAuth 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. |
| Cost | No 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. |
| Permissions | Each 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 handling | Not 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 |
|
|
| Risk context | The 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 review | 2026-10-19 | 2026-07-30 |
| Candidate evidence | 2026-10-20 | 2026-09-24T04:25:05.554391Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →