OPNForm
OPNForm is an open-source form builder for creating forms, managing workspaces, collecting submissions, and configuring integrations.
Verdict
Common use cases
- Draft event registration forms from chat
- Collect customer feedback after support calls
- Build intake questionnaires for onboarding
- Route form submissions to Make workflows
- Audit and delete old survey data
Integration
- Vendor
- OPNForm
- Category
- other
- Auth
- API_KEY
- Tools
- 28
- Composio slug
opn_form
Tools
- Cancel Workspace Invite
Cancel and remove a pending workspace invitation before it is accepted. Requires a personal access token with the workspace-users-write ability.
- Create Form
Create an OpnForm form in a workspace from a title, ordered field or layout blocks, and optional validated form settings. Optional retention settings permanently delete future submissions after the configured period. Requires a personal acc
- Create Form Integration
Create a generic webhook or Make integration for an OpnForm form. This registers an external destination for future form submission data; an active integration can begin sending submissions to that destination immediately, while an inactive
- Create Submission
Submit answers to a public OpnForm form. A completed submission may immediately send its data to active webhook or Make integrations; optionally save a partial submission with completion and campaign-attribution metadata.
- Create Workspace
Create an OpnForm workspace. Account workspace limits may reject creation even when the personal access token has write access. Requires a personal access token with the workspaces-write ability.
- Delete Formdestructive
Permanently delete a form and all of its submissions by numeric ID. This irreversible operation cannot be undone. Requires a personal access token with the forms-write ability.
- Delete Form Integrationdestructive
Permanently remove a webhook integration from a form and stop its future deliveries. This operation cannot be undone. Requires a personal access token with the manage-integrations ability.
- Delete Submissiondestructive
Permanently delete one submission from a form using both numeric IDs. This irreversible operation cannot be undone. Requires a personal access token with the forms-write ability.
- Delete Submissionsdestructive
Permanently delete 1-25 submissions from one form through sequential provider requests. This operation is irreversible and not atomic: confirmed earlier deletions are not rolled back. Processing continues after item-local invalid or not-fou
- Delete Workspacedestructive
Permanently delete a workspace and its contained resources. This irreversible operation cannot be undone and requires repeating the workspace ID as explicit confirmation. Requires a personal access token with the workspaces-write ability.
- Get Current User
Return the name and email of the OpnForm user associated with the connected personal access token.
- Get Form
Retrieve a form by its public slug, including its complete field and layout definitions. Requires a personal access token with the forms-read ability.
- Invite Workspace Member
Add an existing OpnForm user to a workspace or email an invitation to a new user. Sending an invitation email cannot be undone. OpnForm Cloud requires a Pro plan and a personal access token with the workspace-users-write ability.
- Invite Workspace Members
Add or invite 1-10 users to one workspace through sequential provider requests. Each successful item may send an invitation email that cannot be undone, and the batch is not atomic. Processing continues after item-local validation failures
- List Form Integrations
List webhook and Make integrations configured for a form, including IDs, status, and endpoint configuration. Requires a personal access token with the manage-integrations ability.
- List Forms
Return one page of lightweight form summaries from a workspace. Pass the returned cursor back to continue; use Get Form for complete field definitions. Requires a personal access token with the forms-read ability.
- List Integration Events
Inspect past delivery attempts for one form integration, including the attempt date, Success or Error status, and a downstream HTTP status when available. Requires a personal access token with the manage-integrations ability.
- List Submissions
Return one searchable page of completed, partial, or all submissions for a form. Pass the returned cursor back unchanged to continue with the same filters. Requires a personal access token with the forms-read ability.
- List Workspace Invites
List pending and accepted invitations for a workspace where the connected user is an administrator. Requires a personal access token with the workspaces-write ability.
- List Workspace Members
List members of a workspace with their user IDs, names, emails, and workspace roles. Requires a personal access token with the workspace-users-read ability.
- List Workspaces
List workspaces accessible to the connected user, including IDs, plan tier, role flags, usage counts, enabled features, and plan limits. Requires a personal access token with the workspaces-read ability.
- Remove Workspace Memberdestructive
Remove a specified member from a workspace without deleting the member's OpnForm account. Requires a personal access token with the workspace-users-write ability.
- Resend Workspace Invite
Send another invitation email for an existing pending workspace invite. Each successful call sends an external email to the invite recipient and requires a personal access token with the workspace-users-write ability.
- Update Form
Replace or change an existing form's field definitions and settings using its numeric form ID. Requires a personal access token with the forms-write ability.
- Update Form Integration
Change a generic webhook integration's delivery URL or active status. Requires a personal access token with the manage-integrations ability.
- Update Form Submission Retention
Change or disable a form's automatic submission-retention policy. Expired submissions are permanently deleted and cannot be restored; shortening the period can make existing submissions eligible for the next hourly cleanup. Requires a perso
- Update Workspace
Change a workspace's name and icon without affecting its membership or forms. Both values are required because OpnForm clears an omitted icon. Requires a personal access token with the workspaces-write ability.
- Update Workspace Member Role
Change an existing workspace member's role to admin, user, or readonly. Requires a personal access token with the workspace-users-write ability.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings → Integrations → Add MCP Server. 2. Select OPNForm from the catalog and choose API Key authentication. 3. Log in to your OPNForm account, go to Settings → API Tokens, and generate a new personal access token with the scopes you need (forms-write for creating and deleting forms, workspace-users-write for managing invites, manage-integrations for webhook setup). 4. Paste the token into Switchy's API Key field and click Connect. 5. Open any Project, type '@OPNForm list my workspaces' and send; if you see workspace names in the reply, the connection is live. 6. To create a form, @mention OPNForm again with a prompt like 'build a three-question feedback form in workspace X' and it will return the form ID and public URL.
What teammates see: by default, memories from OPNForm are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Build Feedback Form
@OPNForm create a form titled 'Post-Demo Feedback' in my default workspace with three fields: a 1-5 rating for 'Overall Experience', a text area for 'What went well?', and a text area for 'What could improve?'. Make all fields required.
List Active Forms
@OPNForm show me all forms in workspace ID 42, including their titles, public URLs, and submission counts.
Wire Webhook Integration
@OPNForm add a webhook integration to form ID 789 that sends every submission to https://example.com/intake. Include all field data in the payload.
Submit Test Response
@OPNForm submit a test response to form ID 123 with answers: 'Name' = 'Alice Smith', 'Email' = 'alice@example.com', 'Feedback' = 'Great experience, very smooth process.'
Delete Old Submissions
@OPNForm delete submission ID 456 from form ID 123. Confirm the operation is permanent and cannot be undone.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@OPNForm list all submissions from the 'Product Feedback' form in the last 7 days and summarize the top 3 feature requests by frequency
Retrieved 47 submissions from form ID 8291 ('Product Feedback') since January 15. After analyzing the free-text responses, the top three requested features are: (1) Dark mode support — mentioned in 18 submissions, often citing eye strain during evening use. (2) Bulk export to CSV — requested 12 times, primarily by users managing large datasets. (3) Conditional logic for follow-up questions — appeared in 9 submissions, with users wanting dynamic forms that adapt based on prior answers. Note: This analysis reflects illustrative patterns; actual submission content and frequency will vary by your workspace activity.
This example combines OPNForm's read access (fetching submissions) with the AI's synthesis capability. Requires a personal access token with forms-read ability. Be aware that large forms with hundreds of submissions may hit rate limits or require pagination; the MCP handles retrieval, but summarization quality depends on submission volume and text clarity.
@OPNForm create a new form called 'Q1 Team Retro' in the Engineering workspace with fields for rating (1-5), what went well, and what to improve
Successfully created form 'Q1 Team Retro' (ID 8403) in workspace 'Engineering' (ID 142). The form includes three fields: (1) a numeric rating field (1-5 scale, required), (2) a long-text field labeled 'What went well?' (optional, 500-character limit), and (3) a long-text field labeled 'What should we improve?' (optional, 500-character limit). The form is currently private; you can publish it or configure integrations via the OPNForm dashboard. Direct link: opnform.com/forms/8403/edit
This write operation demonstrates form creation from a natural-language description. Requires a personal access token with forms-write ability. The MCP translates your intent into OPNForm's field schema, but complex validation rules (regex patterns, conditional visibility) may need manual refinement in the UI after creation. Account workspace limits may block creation if you've reached your plan's form quota.
@OPNForm set up a webhook integration for the 'Bug Report' form to send new submissions to our Slack channel at hooks.slack.com/services/T00/B00/XX
Created webhook integration (ID 7721) for form 'Bug Report' (ID 8156). All future submissions will POST to https://hooks.slack.com/services/T00/B00/XX immediately after completion. The payload includes submission ID, timestamp, and all field responses in JSON format. Integration is now active; test it by submitting the form. You can disable or delete this integration anytime via the OPNForm dashboard or by calling the delete-integration tool. Note: This is a one-way push; OPNForm does not retry failed deliveries or store webhook response data.
This action example shows side-effect risk clearly: once active, the integration begins sending real submission data to an external endpoint. Requires a personal access token with manage-integrations ability. Verify the webhook URL is correct before creation — OPNForm does not validate the destination or handle delivery failures. If your Slack webhook changes, you must delete the old integration and create a new one; updates are not supported.
Use-case deep-dives
When OPNForm beats Typeform for onboarding workflows
A 6-person SaaS company runs customer onboarding through a multi-step intake form that feeds Slack and their CRM. OPNForm wins here because the Create Form Integration tool lets you wire submissions directly to webhooks without paying per-response pricing. You build the form once with Create Form, point it at your Make.com scenario or custom endpoint, and every new customer submission lands in your stack automatically. The trade-off: if you need advanced conditional logic or payment collection in the form itself, OPNForm's 28 tools don't cover those natively—you'd handle branching in your webhook receiver. But for straightforward intake where the real work happens downstream, OPNForm keeps your per-seat cost flat and your integration ownership in-house. If you're onboarding fewer than 50 customers a month, this is overkill; stay with a no-code form builder.
OPNForm's retention settings solve compliance headaches
A 3-person nonprofit runs quarterly webinars and collects attendee emails through a registration form. European privacy law requires they delete registration data 90 days after each event. OPNForm's Create Form tool includes retention settings that auto-delete submissions on a schedule—no cron job, no manual purge. You set the retention window when you build the form, and Delete Submission runs automatically when the clock expires. This beats Google Forms or Airtable, where you'd script the cleanup yourself or risk a GDPR fine. The boundary: if your event series runs year-round with overlapping cohorts, managing per-form retention windows gets messy fast. At that scale, you want a dedicated CRM with lifecycle automation. But for episodic events with clean cutoff dates, OPNForm's built-in purge is the fastest path to compliance.
When to use OPNForm's workspace model for client isolation
A 10-person design agency builds intake forms for 15 active clients. Each client needs their own form library, and some clients have junior staff who shouldn't see other clients' data. OPNForm's Create Workspace and Cancel Workspace Invite tools let you spin up isolated environments per client and control who joins. You create one workspace per client, build their forms inside it, and invite only their team members—no cross-client data leakage. The API_KEY auth means you can script workspace provisioning when you onboard a new client. The catch: if a client needs real-time collaboration on form design (comments, version history), OPNForm doesn't surface that in the MCP—you're managing form JSON directly. This works when the agency owns form creation and clients just consume the published links. If clients want to co-edit, you'd need a layer on top or a different tool.
Frequently asked
What does the OPNForm MCP let me do in Switchy?
It lets your AI agents create forms, manage workspaces, submit responses, and wire up webhook integrations — all without leaving the chat. You can build a customer feedback form, delete old submissions, or connect a Make automation in a single prompt. The MCP wraps OPNForm's API so agents handle the form lifecycle end-to-end.
Do I need a paid OPNForm plan to use this MCP?
You need an OPNForm account and a personal access token with the right abilities — workspace-users-write, forms-write, manage-integrations, depending on which tools you call. Free-tier workspace limits may block new workspace creation even when your token has write access. Check your plan's workspace cap before asking an agent to create one.
Can the MCP edit an existing form's fields or logic?
No. The Create Form tool builds a new form from scratch with ordered field blocks and settings, but there's no Update Form tool. To change a live form's structure, you'd delete it and recreate it — which also wipes submissions. For minor tweaks, edit the form directly in OPNForm's UI instead.
Why use the MCP instead of OPNForm's web dashboard?
The MCP shines when you're already in a Switchy chat and want to spin up a form, pull submission data, or wire a webhook without context-switching. If you're designing complex conditional logic or branding a form, the dashboard is faster. Think of the MCP as the API for agents — quick, scriptable, but not a full UI replacement.
Who on my team should connect the OPNForm MCP?
Whoever owns the OPNForm account and can generate a personal access token with the abilities your workflows need. That person's token permissions gate what agents can do — if the token lacks forms-write, agents can't delete submissions. One shared connection works for the whole Switchy workspace; you don't need per-user tokens.