Direct answer: Typeform's MCP server supports form building, automations, contacts, and response analysis over Streamable HTTP. Finta's current catalog lists the official endpoint but records bearer authentication while Typeform's current MCP documentation specifies OAuth, so this page should not publish until the production connection method is reconciled and proven.
This guide is for teams using Finta as relationship intelligence around a capital, investor, customer, or company-building workflow. Typeform remains the source system for its records. Aurora can use only the context and actions exposed to the connected account.
Current connection note: The enabled Aurora catalog currently uses a bearer token, while Typeform's current MCP guidance emphasizes OAuth for supported clients. The page documents the current Finta setup and the provider difference.
How the Typeform connection works
| Connection detail | Current Finta guidance |
|---|---|
| Classification | Catalog MCP |
| Configured endpoint | https://api.typeform.com/mcp |
| Authentication and transport | User-supplied bearer or personal access token; Streamable HTTP |
| Source of truth | Typeform remains authoritative for provider records, permissions, and action results. |
| Human control | Review external communication, record changes, financial actions, publishing, deletion, and other consequential work before execution. |
What you can use it for
- List and inspect permitted Typeform forms, workspaces, structures, and current drafts.
- Analyze provider-supported response fields for a defined investor intake or LP questionnaire.
- Review or prepare contact records and form-to-contact mappings supported by Typeform.
- Prepare form or automation changes using Typeform's validate-before-patch and explicit publish controls.
These uses summarize the current provider documentation and Finta catalog purpose. The exact tool inventory varies by provider version, plan, workspace, user permissions, region, and authorization scopes.
Relationship intelligence workflows for Typeform
Investor or advisor intake review
Outcome: A structured review of submitted fit, relationship, timing, and request information without treating form answers as verified facts.
- Identify the authoritative Typeform and retrieve its field structure and response schema.
- Analyze the selected response set for complete answers, missing context, and explicit consent fields.
- Prepare a review queue that links each recommendation to the Typeform response and separates stated data from inference.
Human decision: A person reviews sensitive response data, consent, identity matching, and any CRM or contact action.
LP diligence questionnaire improvement
Outcome: A safer, clearer draft questionnaire or automation based on actual response friction and unanswered fields.
- Retrieve the form structure and the provider-supported response analysis for a defined period.
- Identify ambiguous questions, abandoned sections, or missing routing logic without exposing respondent data unnecessarily.
- Prepare validated form patches or automation changes as a draft, not a live publication.
Human decision: The form owner approves copy, logic, data collection, automation, and the final publish action.
How to connect Typeform to Aurora
- Before public launch, reconcile Finta's bearer catalog record with Typeform's current OAuth-only MCP documentation.
- If the catalog is updated, select Typeform in Aurora and complete the provider OAuth flow with the minimum required scopes.
- Confirm whether the account uses the global or one of Typeform's EU data-center endpoints.
- Retrieve one known form and its structure before reading any responses.
- Keep form patches in draft and require explicit confirmation before Typeform's publish tool is called.
Open the official Finta apps directory to confirm the catalog entry before authorizing a provider account.
Permissions and approval boundary
Typeform separates read, write, validation, and publish operations. Aurora may retrieve or prepare, but contact writes, response imports, automation changes, form edits, deletion, and publication require an identified owner and explicit approval. Sensitive responses must be minimized and handled according to consent and policy.
Limitations to understand
- Typeform describes the MCP server as a generally available beta with limited and evolving capabilities.
- The current Finta bearer auth record conflicts with Typeform's documented OAuth flow and is a publication blocker until verified.
- EU-hosted accounts require the correct regional endpoint.
- Tool access depends on Typeform subscription, scopes, workspace access, and the form's data sensitivity.
Verification checklist
- Resolve whether production Aurora supports Typeform OAuth or a provider-supported bearer path for the MCP endpoint.
- Update or confirm the catalog auth type before publication and capture a successful authentication receipt.
- Discover the live Typeform tool list and granted scopes.
- Retrieve one known form and compare its fields with Typeform.
- Retrieve a controlled response set without exposing production PII in logs or screenshots.
- Validate a draft patch and confirm that nothing goes live until an explicit publish approval.
Verification status: On 2026-08-22, Finta confirmed that this connector appears in the enabled production Aurora catalog and reviewed the configured endpoint, authentication type, and first-party sources listed below. This is not a claim that every provider tool or an authenticated end-to-end action has been tested for every account.
Official provider sources
- Typeform official MCP documentation (developer.typeform.com)
- Typeform official MCP documentation 2 (developer.typeform.com)