Typeform

Overview

Proxy Typeform's hosted MCP server so AI clients can work with forms through stackgate.ai. Tools mirror upstream dynamically after you connect. Insights, contacts, and automations tools are not yet available: Typeform hasn't enabled the insights:read scope for third-party apps, and contacts:*/automations:* scopes require Typeform's paid Contacts and Automations add-on on the connected account.

Prerequisites

• A Typeform account
• A stackgate.ai account

Getting credentials

1. Open Integrations → Typeform in stackgate.ai.
2. Click Activate, then Connect Typeform.
3. Complete Typeform OAuth (streamable HTTP MCP at https://api.typeform.com/mcp).
4. Open Preferences to set your data region (Global or EU) and whether mutating tools are allowed.

Mutating tools (create/edit/publish forms) are off by default. Enable Allow mutating tools in preferences when you need them.

Typeform MCP supports OAuth only — personal access tokens are not accepted by the upstream MCP server.

Using with AI clients

• Dedicated endpoint: POST /mcp/typeform
• Private gateway: typeform__* namespaced tools (mirrored from upstream)
• Run refresh_tools after connect (or after Typeform updates) to sync the latest upstream tool list

See Typeform MCP documentation for upstream capabilities.

See Documentation for HTTP authentication and private gateway setup.

Troubleshooting

• OAuth failed — confirm the hub redirect URI matches Typeform MCP OAuth registration, and that you selected OAuth (not a personal token).
• Empty tool list — call refresh_tools after connect; confirm the integration is enabled and tokens are valid.
• EU account 404s — set Preferences → Data region to EU (https://api.eu.typeform.com/mcp).
• Mutating tool missing — enable Allow mutating tools in preferences (read tools stay available either way).
• Token expired — reconnect Typeform from My Integrations.
• Response PII — keep write tools off when sharing briefs with other agents or Slack.
• Bad Request: scope not allowed: "insights:read" during connect — Typeform has not yet enabled the insights:read OAuth scope for third-party apps; the hub no longer requests it. If you still see this error, reconnect Typeform (the hub's stored OAuth scope list has been updated).
• Bad Request: scope not allowed: "contacts:read" (or automations:*) during connect — these scopes require Typeform's paid Contacts and Automations add-on on the account that owns the OAuth app. The hub no longer requests them by default; if you have the add-on and want these tools, add contacts:read contacts:write automations:read automations:write back to TYPEFORM_OAUTH_SCOPES and reconnect.
• Token request … failed with status [400] after consent — Typeform MCP access tokens cannot include refresh tokens. Do not set offline_access / offline in TYPEFORM_OAUTH_SCOPES. Reconnect when the access token expires.
• Connection timed out / cURL error 28 on callback — the hub could not reach https://api.typeform.com/oauth/token in time (often transient). Retry Connect Typeform; if it keeps failing, check outbound network access from the server to Typeform.