# Typeform
ID: 14-typeform
Page: https://gtmmcps.com/tools/14-typeform
JSON: https://gtmmcps.com/data/tools/14-typeform.json
Documentation references: https://gtmmcps.com/docs/14-typeform/
Category: Inbound & PLG Chat
MCP support: official
Testing: RESEARCHED
API access: paid
Last checked: 2026-09-07
Endpoint check: not-probed; date: Not recorded

An online form and survey builder (conversational one-question-at-a-time forms, quizzes, lead-capture forms) with logic, integrations, webhooks and a REST API, widely used as the top-of-funnel intake form.

## MCP links
- https://api.typeform.com/mcp
- https://www.typeform.com/developers/get-started/mcp/
- https://www.typeform.com/developers/mcp/plans/

## Sources
- https://www.typeform.com/developers/get-started/mcp/
- https://www.typeform.com/developers/mcp/plans/
- https://www.typeform.com/pricing/
- https://api.typeform.com/mcp

## Research notes
Verified 2026-09-07: POST of an MCP initialize to https://api.typeform.com/mcp returned HTTP 401 with JSON reading "not authorized"; the control POST to /zzz-not-a-route returned 404 with a JSON body reading "Endpoint not found". Live first-party auth-gated server. The plan-gating design (stable tool list, per-call enforcement, and the docs' instruction to "Branch on the top-level code, never on the prose") is the clearest published pattern in this directory for how a vendor hides plan limits inside an MCP: the connector works on every plan and the tool call fails on the wrong one, the same failure shape Vayne documents in 01-data-enrichment.md. 2026-09-07: https://api.typeform.com/mcp returned 401 to an MCP initialize POST (https://api.typeform.com/mcp).

## Named capabilities
Tool names below are reported by sources. Their presence is not a successful call.

## CLI evidence
Status: none-found

Read current vendor documentation before configuring or running commands.