Typeform MCP Server

The Typeform MCP server is the official, provider-hosted connector that lets LLM clients interact with a Typeform account. It is currently in beta with a deliberately small surface area: basic read-only access to Forms and basic read-write access to Contacts. Typeform plans to expand the toolset and add OAuth authentication over time.

The server is exposed as a remote HTTP endpoint (streamable HTTP transport only; SSE is not supported). Global accounts connect through https://api.typeform.com/mcp, while EU data center accounts use https://api.eu.typeform.com/mcp or https://api.typeform.eu/mcp. Authentication is performed by sending a Typeform personal access token in the Authorization: Bearer header. Under the hood, Typeform built the server using a federated architecture where domain teams ship their own MCP servers behind a central gateway that handles routing, rate limiting, and access control.

Because the server is hosted by Typeform there is nothing to install or run locally. You point your MCP client (Claude Code, Claude Desktop, Cursor, etc.) at the URL and supply your token. Feature availability still depends on your Typeform subscription tier.

Tools

Prerequisites

• A Typeform account (feature access depends on your plan tier)
• A Typeform personal access token. Create one from your Typeform account settings under Personal tokens.
• An MCP client that supports remote HTTP servers (Claude Code, Claude Desktop with connectors, Cursor, etc.)

Endpoint

Pick the endpoint that matches your data center:

• Global: https://api.typeform.com/mcp
• EU: https://api.eu.typeform.com/mcp or https://api.typeform.eu/mcp

Authentication header:

Authorization: Bearer <YOUR_TYPEFORM_PERSONAL_ACCESS_TOKEN>

Transport: streamable HTTP only (no SSE).

Claude Code

Add the server with the claude mcp add command, passing the bearer token as a header:

claude mcp add --transport http typeform https://api.typeform.com/mcp \
  --header "Authorization: Bearer <YOUR_TYPEFORM_PERSONAL_ACCESS_TOKEN>"

Replace the URL with the EU endpoint if your account lives in the EU data center.

Claude Desktop / generic MCP client

For clients that read an mcpServers config, configure a remote HTTP server entry:

{
  "mcpServers": {
    "typeform": {
      "type": "http",
      "url": "https://api.typeform.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TYPEFORM_PERSONAL_ACCESS_TOKEN>"
      }
    }
  }
}

After connecting, ask the model to list all actions it can perform with the Typeform MCP server to discover the current tool set, since the server is in active development.

Notes

• OAuth (Sign in with Typeform) is on the roadmap but not yet available.
• The server is in beta; tools and behavior may change.

• Look up an existing form's metadata or settings without leaving your AI assistant ("show details for the customer feedback form")
• Add or update Typeform contacts from a chat workflow, such as after a meeting or call summary
• Query a contact list to check whether someone is already in Typeform before adding them
• Build lightweight CRM-style automations in Claude Code that combine Typeform contacts with other connectors (CRM, email, calendar)
• Triage and audit your Typeform account from natural language ("which forms do I own?")

• "List all the forms in my Typeform account."
• "Show me the configuration for my 'NPS Survey' form."
• "Add a new Typeform contact named Jane Smith with email jane@acme.com."
• "Update the contact with email john@acme.com to set the company field to Acme Corp."
• "What tools are available through the Typeform MCP server right now?"

• Official, provider-hosted server maintained by Typeform, no self-hosting required
• Works with any MCP client that supports remote HTTP transport
• Separate EU endpoints for data residency compliance
• Simple bearer token setup with personal access tokens

• Beta with a small surface area: only basic Forms (read) and Contacts (read/write) today, no responses, webhooks, or workspace tools yet
• No OAuth yet; only personal access tokens, which makes multi-user setups awkward
• Tool names and capabilities are not fully documented; users must introspect tools through the client
• Feature availability is gated by Typeform subscription plan

• dscovr/typeform-mcp: community-built Typeform MCP server covering more endpoints (forms CRUD, responses, etc.) via the public REST API
• Composio Typeform toolkit: managed Typeform MCP integration that proxies REST actions through Composio
• Zapier MCP for Typeform: Typeform actions exposed through Zapier's MCP gateway