Docs / AI and API
MCP server
A remote MCP server, so any AI tool can create forms, check their health and read submissions.
{
"mcpServers": {
"wrenform": { "url": "https://wrenform.com/mcp" },
"wrenform-quick": { "url": "https://wrenform.com/mcp/quick" }
}
}In Claude Desktop and claude.ai, add a custom connector with the URL https://wrenform.com/mcp. Windsurf takes the
same mcpServers entry as Cursor, with serverUrl instead of url. In Claude Code, the
plugin adds both servers for you.
Two servers
| URL | Sign-in | Tools |
|---|---|---|
https://wrenform.com/mcp |
OAuth in the browser, or an API key | Everything below |
https://wrenform.com/mcp/quick |
None | create_quick_form, check_quick_form, get_snippet, get_docs |
Signing in: the first time your tool calls /mcp, it opens wrenform.com in the browser. Sign in, then tick what
the tool may do (read forms, change forms, read submissions…). Each connection shows under Account → API & AI
tools, where you can disconnect it at once. Tokens last an hour and refresh for up to 30 days.
Headless: send an API key instead, as Authorization: Bearer wf_live_…. Create keys under Account → API & AI
tools. A key's scopes (forms:read, forms:write, submissions:read, submissions:write, webhooks:write) limit what the tools can do.
Tools on /mcp
| Tool | What it does |
|---|---|
whoami |
Which account, its plan and this month's usage |
list_forms |
Every form with its ID, status and endpoint |
create_form |
A new form, its endpoint, a snippet for your framework and next steps |
get_snippet |
Ready-to-paste code for a form in a given framework |
set_recipients |
Which addresses get submissions (new ones confirm by email first) |
send_test_submission |
A test message, as a visitor would send it |
get_form_status |
The form's health: recipients, last test, usage, and issues with fixes |
update_form |
Name, allowed origins, thank-you page, email notifications, spam sensitivity, retention |
pause_form, resume_form |
Stop or restart accepting submissions |
delete_form |
Delete a form; needs its exact name as confirmation |
list_submissions |
Recent submissions, newest first, at most 20 per call |
mark_submission |
Move a submission between inbox and spam |
create_webhook, list_webhooks |
Add or list webhook endpoints (Pro and Agency) |
get_docs |
Any docs page as Markdown |
Tools that only read are marked read-only, so your tool can run them without asking each time.
Safety
Submissions are typed by website visitors, so list_submissions returns them under untrusted_submission_data, next
to a notice that they are data, not instructions. Long values are shortened. No tool ever returns a password, a full
API key or a webhook secret after it's created.
Test it
- Add the servers to your tool.
- Ask: "Which Wrenform account am I connected to?" Your tool signs in and calls
whoami. - Ask it to create a contact form for your site and send a test. The test message arrives by email.
Common problems
- Your tool keeps asking to sign in. The connection was revoked or has expired. Connect again from your tool's MCP settings.
insufficient_scope. The connection or key wasn't allowed that action. Reconnect and tick the permission, or use a key with that scope.plan_limit. The plan's form or recipient limit is reached. Upgrade, or delete what you no longer need.rate_limited. Too many calls in a minute. Wait and retry.
Next steps
- REST API: the same actions over plain HTTP.
- Forms without an account: what
create_quick_formdoes. - Errors: every error code and its fix.