Typeform

Typeform

A leading interactive-form platform with APIs that can create forms, retrieve responses, manage workspaces, and receive webhook events without using the native builder.

Research, forms & feedbackSystem of intelligenceExtensible SaaS
An illustration of access surfaces surrounding a governed system.
System roleSystem of intelligence
Access maturityExtensible SaaS
MCP supportOfficial MCP server
Reference updatedNot stated by publisher
BYO-UI reviewedJul 22, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Forms and responses; automations; contacts, lists, and mappings.

02 · Data you can retrieve

Read accounts, form capabilities and current definitions, responses and analyses, automation working state, and supported contacts, properties, lists and mappings.

03 · Actions and write paths

Create forms, validate and apply draft patches, publish or delete forms; manage automations; and create, upsert or delete contacts, lists, properties and mappings.

04 · Authentication and permissions

Typeform's hosted server uses OAuth with per-tool scopes. Clients must select the global or appropriate EU endpoint, which Typeform documents as distinct regional servers.

05 · Monitoring, approval, and recovery

Keep validated draft patches separate from published forms; require explicit confirmation before publishing, deleting forms or contacts, activating automations, or sending webhook and email steps.

06 · Limits and caveats

The service is a generally available beta with limited capabilities. It supports Streamable HTTP, not SSE, and requires the global or matching EU regional endpoint.

Agent access

MCP support

Official MCP serverTypeform hosted MCPGenerally available beta with limited capabilities

Support: Official MCP server

Read scope: Expose authorized account, form definition, response analysis, automation state and contact-database context while preserving form, response, automation, contact, list, property and region identifiers.

Write scope: Use Typeform's validate-before-save patch flow for form drafts, publish explicitly, and separately scope automation lifecycle changes and contact-database mutations.

Authentication: OAuth

Approval boundary: Show the validated form patch before applying it, then confirm publication separately; require named confirmation for form or contact deletion and automation steps with external effects.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access4
Identity4
Governance4
Agent access3
UI extensibility4
Portability3
Observability3
Documentation4

Proposed customer-shaped experiences

What customers could create on top.

The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Typeform ships them.

Single-platform patterns

  • Research intake and response-triage console
  • Research synthesis room
  • Feedback triage console
  • Evidence-backed insight brief
Use in the brief builder →

Multi-platform compositions

  • Typeform + CRM or product analytics: research synthesis room
  • Typeform + work and knowledge system + content or planning platform: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

4 recorded sources
MCP / agent-role validationRepresentative source
https://www.typeform.com/developers/get-started/mcp/ ↗

Typeform documents hosted global and EU MCP endpoints with OAuth for form and response workflows.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 12, 2026

Targeted first-party MCP/agent-role review; broader API inventory retained

Developer portalSource inventory
https://www.typeform.com/developers/ ↗

First-party API documentation.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory
https://www.typeform.com/ ↗

Product overview.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

WebhooksSource inventory
https://www.typeform.com/developers/webhooks/ ↗

First-party event guidance.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Verified fact

Tied to cited first-party evidence reviewed for this profile.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.