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 | Salesforce Hosted MCPMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP Typeform · Publisher source ↗ | First-party MCP Salesforce · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Not documented Package: Not documented | Repo: Not documented Package: Not documented |
| Popularity evidence | ||
| Client coverage | ||
| Client coverage details | Not documented | Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP |
| 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. | Follow only the publisher source; credential storage, scopes, and revocation remain under review. |
| 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. | Publisher plans, API usage, infrastructure, or per-action charges may apply; MCP100 has not published a cost conclusion. |
| 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. | Exact permissions and read/write boundaries have not completed MCP100 review. |
| Data handling | Not documented in the reviewed sources. The reviewed Typeform MCP pages do not state an MCP-specific retention or training policy. | Candidate-specific retention, subprocess, telemetry, and model-data behavior remain review items. |
| 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. | Use a test account, least privilege, read-only controls where available, and explicit approval for mutations. |
| Evidence date | ||
| Editorial review | 2026-10-19 | 2026-07-24 |
| 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 →