Set up Typeform MCP Server

Start Set up Typeform MCP Server with minimal permissions, correct transport configuration, and verified data flow.

Published on 18.09.2026

The Typeform MCP Server connects your AI agent to your Typeform account: create forms, analyze responses, and set up automations — directly from your AI client. Start with read tools and enable write tools only when needed.

Establish the connection

For Claude Code, a single command is enough: claude mcp add --transport http typeform https://api.typeform.com/mcp. For Claude Desktop or the web interface, go to Settings → Connectors, search for Typeform, and click Connect. For other clients (Cursor, VS Code, Codex), add the server in your MCP configuration file with the URL https://api.typeform.com/mcp and HTTP transport. On first connection, a browser window opens for the Typeform OAuth login. Important: SSE transport is not supported by the server — make sure your client uses Streamable HTTP.

First call: get the account ID

After connecting, call the accounts-list_accounts tool first. Almost all other tools require the returned account_id as a parameter. Without this step, subsequent requests will fail with an authorization error. This is a characteristic of the Typeform API model, not a server bug.

Use tools selectively

The server provides four tool groups according to the provider: forms-* (create and edit forms), automations-* (build workflows), contacts-* (contact management), and insights-* (response analytics). For pure analytics tasks, the insights-* tools are sufficient. Write tools in forms-* and automations-* can modify forms and workflows — only enable these when the agent is actually supposed to make changes.

Avoid prompt injection

When the agent analyzes form responses, user input enters the language model's context. This input may contain instructions that lead the agent to unintended actions (prompt injection). Separate read and write operations: analyze responses in a separate session without write tools enabled, or manually confirm write operations before the agent executes them.

Published on 18.09.2026

Categories

Frequently asked questions

Why does the connection fail with SSE transport?

The Typeform MCP Server only supports Streamable HTTP transport according to the provider. Clients configured for SSE receive an immediate connection error. Check your client's transport configuration and make sure HTTP (not SSE) is set.

Which Typeform plan is required for the MCP Server?

Basic connection is possible within an existing Typeform account. Advanced features such as automations and certain analytics are plan-dependent according to the provider. Plan errors are returned as structured error responses. Current details at typeform.com/pricing.

Can I use the server for EU-hosted accounts?

Yes, but EU-hosted accounts use different endpoints according to the provider. The current endpoints are documented at developer.typeform.com/developers/get-started/mcp/.

How do I restrict the agent's data access?

Only authorize a Typeform account with the minimum required permissions. For pure analytics scenarios, configure only the `insights-*` tools. Enable write tools only when the agent is specifically intended to create forms or set up automations.