Typeform MCP server
Inspect forms, questions, and workspace structure with Arc0’s Typeform tools. Response lookup requires an existing completed-response ID and returns metadata without answers. Connect through Arc0 to use the actions your identity is allowed to call.
Working with Typeform
A form audit begins with typeform.list_forms to identify the intended form by title and ID. typeform.get_form reads compact question descriptors, including IDs, types, and titles. An agent can use that structure to discuss which questions exist, but the result is not an editable copy of the whole form and cannot be written back through these tools.
typeform.list_workspaces discovers accessible workspaces, which may belong to different organizations. typeform.get_workspace checks one workspace’s organization, sharing state, and form count without exposing members. Keep those boundaries explicit when preparing an inventory rather than assuming the first workspace represents the whole account.
typeform.get_response is a narrow lookup for an already-known completed-response ID. It first verifies the form’s region, then returns submission metadata without answers. It does not discover response IDs or read partial submissions. Recent submissions may take time to appear, so an empty lookup is not immediate proof that someone failed to submit. All five tools are reads: they do not create forms, delete responses, or send notifications.
Official MCP reference: Typeform documentation.
Agent workflows for Typeform.
Find the intended form
Use typeform.list_forms to inspect titles and IDs in an account or workspace.
Review question structure
Use typeform.get_form for question IDs, types, and titles before discussing a form’s design.
Check a known submission
Use typeform.get_response with a completed-response ID to inspect metadata, not answer content.
Inspect workspace context
Use typeform.list_workspaces and typeform.get_workspace to check organization, sharing state, and form count.
5 Typeform actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
5Look things up, subject to your permissions.
- typeform.list_formsList forms
Use when finding forms in an account or workspace. Returns a bounded page of form IDs, titles and timestamps; total_items counts forms, not responses. Use get_form for question details.
- typeform.get_formGet form
Use when inspecting a known form’s question IDs, types and titles before interpreting responses. Use list_forms to discover IDs; not an editable round-trip form payload.
- typeform.get_responseGet response
Use when checking a known completed response ID. Metadata only; two requests against the 2 req/s account limit verify region then read. Not for discovering IDs, partials or answers. Recent submissions may take 30 minutes to appear
- typeform.list_workspacesList workspaces
Use when locating accessible workspaces and their organization IDs. Results can span multiple organizations; not an account identity check; use get_workspace for a known ID.
- typeform.get_workspaceGet workspace
Use when checking a known workspace’s organization and sharing status. Includes forms.count, excludes members. Use list_workspaces to discover IDs.
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Control access to Typeform.
Connect the intended Typeform account, authorize your AI client and set policies for its tools.
Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.
Configure policies and approvalsExample policy choices
- Read actions: allow where authorized
Arc0 MCP endpoint: https://api.arc0.ai/mcp
How Typeform connects.
Connect Typeform using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Typeform with your AI client.
Sign in to Arc0 and connect Typeform in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
Typeform with Claude
Claude Desktop + Claude Code
- In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
- For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
- Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpFull MCP setup and troubleshootingTypeform with ChatGPT
ChatGPT on the web
- Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
- Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
- Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingTypeform with OpenAI Codex
Codex app + CLI
- Run the registration command below. The app and CLI share ~/.codex/config.toml.
- Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
- Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcpFull MCP setup and troubleshootingTypeform with Cursor
Remote MCP setup
- Add Arc0 in your client’s remote MCP settings using the server URL below.
- Choose OAuth, sign in to Arc0, select the intended workspace and review access.
- Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingTypeform with VS Code
Remote MCP setup
- Add a remote HTTP MCP server named Arc0 using the URL below.
- Use OAuth and finish Arc0 sign-in, workspace selection and consent.
- Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingTypeform with Any MCP client
Streamable HTTP
- Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
- For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
- Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingAfter setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.
More forms and surveys apps.
Typeform and Arc0, answered.
Is there an official Typeform MCP server, and how does Arc0 differ?
Yes. Typeform’s developer portal documents an MCP server. Arc0’s current Typeform tools use a deliberately read-only REST action set, including exact-ID response metadata rather than answer retrieval.
Which permissions does Arc0 need for Typeform?
Use a personal access token with forms:read, responses:read and workspaces:read. Configure the correct supported Typeform region. No OAuth lane or accounts:read requirement is declared; reconnect does not establish that two different keys belong to the same account.
Does this work with Claude, ChatGPT, Codex and Cursor?
Yes, through Arc0 MCP when your Claude, ChatGPT, Codex, or Cursor client supports remote MCP and your account permits it. Connect the app in Arc0 and configure your client using the Arc0 setup guide. App permissions still apply.
How are credentials stored, refreshed and revoked?
Arc0 stores the PAT encrypted and does not refresh it. Disconnect removes local access. Revoke the token in Typeform to invalidate it elsewhere, and confirm the account and region when supplying a replacement.
What happens with rate limits or errors?
Typeform applies an account request limit; the response lookup makes two requests. Arc0 reports throttling and wrong-access errors. Recent submissions can take up to 30 minutes to appear, and the wrong region can return no result without implying that the response does not exist.
What is the availability of these Typeform tools?
These tools are available. Connect the app in Arc0 and authorize your AI client. The action list describes the current implementation.
Plug Typeform into your agent.
Typeform MCP server: 5 actions including list forms, get form, get response. Connect through Arc0.
Free to build · MCP + REST · Audit log on every plan
Typeform and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Typeform.