Skip to main content
Free - like the rest of the MCP server, create_form is not plan-gated.
Creates a new form on your account and returns everything needed to wire it up: the form’s id, its access_key, and a ready-to-paste snippet for the framework you asked for. This is the MCP equivalent of clicking New form in the dashboard - there is no separate REST endpoint for this.

Input schema

Example call

Returned shape

Destination verification: two outcomes

Every form needs a verified destination email before submissions get delivered by email - this stops a form being pointed at an inbox its owner doesn’t control. What create_form does about that depends on whether destinationEmail is already proven on your account: Already verified (either it matches a destination you’ve verified before, or it’s your own account’s verified sign-in email) - the form is ready immediately:
A new address - Formpaste emails a 6-digit code to destinationEmail and stores submissions right away, but holds email delivery until the code is entered:
The agent can’t finish this step itself - it can’t read the destination inbox to see the code. verification_required: true means an agent should tell the developer to check that inbox and enter the code on the form’s Setup tab in the dashboard. This is by design, not a gap: it’s the same anti-bombing check the dashboard enforces on every new destination, described in Your first form.

Errors

An invalid or revoked token returns an MCP tool error (not a form-specific one):
See MCP server for the auth model this comes from.

get_snippet

Fetch a snippet on its own, for an existing form or as a placeholder.

Cookbook prompts

Prompts that drive create_form end to end.