Integration

OpnForm integration

OpnForm is an open-source form builder. List, create, update and delete workspaces, list, add and remove workspace members and change their roles, list, resend and cancel invites, list the forms of a workspace, read, create, update and delete forms, list, update and delete submissions, submit a new answer to a form, and manage a form's webhook integrations and read their delivery events. Custom code and SEO settings of a form, the CSV export routes (their answer can be a file), the deprecated all-forms listing and the Zapier-only routes are not exposed. Requests are limited to 100 per minute per IP. Authentication is a Personal Access Token created in OpnForm Settings, Access Tokens, sent as a Bearer token; each token carries abilities (workspaces-read, workspaces-write, workspace-users-read, workspace-users-write, forms-read, forms-write, manage-integrations) and a call outside them answers 403.

Connect OpnForm How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in OpnForm.Built from the 26 OpnForm tools below, on the connection you add once.

What you can do with OpnForm

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Form, 5 operations

create_formCreate formPOSTCreates a form. Send workspace, title, visibility, language, properties and the display settings update_form requires (theme, presentation style, width, size, border radius, dark mode, color, label case, branding, background). Needs forms-write.
delete_formDelete formDELETEDeletes a form. Needs the forms-write ability.
get_formGet formGETReturns one form with all its settings and its properties (the field and layout blocks, each with its id). Needs the forms-read ability.
list_workspace_formsList workspace formsGETLists a workspace's forms as lightweight summaries (no fields): id, slug, title, visibility, view and submission counts, dates, closing state, share URL. 10 per page by default, up to 100. Use get_form for the full form. Needs forms-read.
update_formUpdate formPUTUpdates a form. Send all required settings and the complete properties list: read it with get_form, change it, send it back. Setting submission_retention_value and _unit together permanently deletes submissions after that period. Needs forms-write.

Workspace, 5 operations

create_workspaceCreate workspacePOSTCreates a workspace with a name and an optional emoji, and returns its id. Needs the workspaces-write ability.
delete_workspaceDelete workspaceDELETEPermanently deletes a workspace. Needs the workspaces-write ability.
leave_workspaceLeave workspacePOSTMakes the token's own user leave the workspace. Needs the workspace-users-write ability.
list_workspacesList workspacesGETLists the workspaces the token's user belongs to, with each one's id, name, icon and settings. Needs the workspaces-read ability.
update_workspaceUpdate workspacePUTRenames a workspace or changes its icon. The user must be an admin of the workspace. Needs the workspaces-write ability.

Form integration, 4 operations

create_form_integrationCreate form integrationPOSTAdds a webhook (generic) or make (the official OpnForm app on Make) integration to a form, which sends each new submission to the configured URL. Needs the manage-integrations ability.
delete_form_integrationDelete form integrationDELETEDeletes a webhook integration of a form. Needs the manage-integrations ability.
list_form_integrationsList form integrationsGETLists the integrations of a form, each with its type, status and configuration. Needs the manage-integrations ability.
update_form_integrationUpdate form integrationPUTUpdates a webhook integration of a form: its status and its configuration. Needs the manage-integrations ability.

Submission, 4 operations

create_form_submissionCreate form submissionPOSTSubmits a new answer to a published form, like a visitor would; this route needs no authentication. Answers are validated against the form (422 with per-field errors), and a partial submission answers with a submission_hash.
delete_form_submissionDelete form submissionDELETEDeletes a submission of a form. Needs the forms-write ability.
list_form_submissionsList form submissionsGETLists a form's submissions, 100 per page by default (the maximum), each with its answers keyed by field id, completion time and attribution. Filter by status (completed, partial or all) or a search term on the answers. Needs forms-read.
update_form_submissionUpdate form submissionPUTChanges answers of an existing submission and returns it. Needs the forms-write ability.

Workspace user, 4 operations

add_workspace_userAdd workspace userPOSTAdds a user to a workspace with a role, or sends an invite when the email is unknown. Needs the workspace-users-write ability.
list_workspace_usersList workspace usersGETLists the members of a workspace with their id, name, email and role. Needs the workspace-users-read ability.
remove_workspace_userRemove workspace userDELETERemoves a member from a workspace. Needs the workspace-users-write ability.
update_workspace_user_roleUpdate workspace user rolePUTChanges the role of a workspace member. Needs the workspace-users-write ability.

Workspace invite, 3 operations

cancel_workspace_inviteCancel workspace inviteDELETEDeletes a pending invite. Needs the workspace-users-write ability.
list_workspace_invitesList workspace invitesGETLists the pending and accepted invites of a workspace, with email, role, status and expiry. The token must include workspaces-write and belong to a workspace admin.
resend_workspace_inviteResend workspace invitePOSTSends the invitation email of a pending invite again. Needs the workspace-users-write ability.

Integration event, 1 operation

list_form_integration_eventsList form integration eventsGETLists the past webhook deliveries of an integration, each with its event type, status, HTTP response code, error message and time. Needs the manage-integrations ability.

Use OpnForm from Claude Code, Cursor or Codex

Connect OpnForm in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its OpnForm operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect OpnForm

Create your workspace
Sign up free. Nothing to install.
Connect OpnForm once
Add your OpnForm connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.