If you're building an MCP connector that works with your users' Typeform accounts, submit a connector request before you start.
We need this to add your redirect URI to our allowlist. The authorization server rejects any redirect URI whose domain isn't on it, so registration fails until we've added yours.
Matching is by domain, not by exact URI — any path under an accepted domain works.
Current as of 25 August 2026. If your domain isn't listed, submit a request and we'll add it.
This means you can develop locally without submitting a request, and test our MCP server on Claude and ChatGPT / Codex through the native MCP connectors.
Just want to use Typeform from an AI client yourself? You don't need a request — see the Help Center links on the overview.
Start with Core concepts: it covers the endpoints, data residency, and the OAuth flow you need before your first tool call, then the order the tools have to be called in.
From there, Supported tools is the full surface, and Not yet supported is what still needs the REST API — worth reading early, so you find the gaps before your users do.