Connect FormBackend to Claude and Cursor with MCP

You can now talk to your FormBackend account from inside the AI assistants you already use. We’ve shipped a Model Context Protocol server at https://www.formbackend.com/mcp — point Claude Code, Claude.ai, Claude Desktop, or Cursor at it and your assistant gets a set of FormBackend tools it can call on your behalf.

What you can ask for

Once it’s connected, you can drop into a chat and ask things in plain English:

• “List my forms and tell me which ones got submissions this week.”
• “Show me the last 20 submissions to my contact form, skip the spam.”
• “Create a new form called ‘Beta waitlist’ and turn on the honeypot.”
• “Update the redirect URL on my newsletter form to point at /thanks.”

Under the hood the assistant calls one of five tools — list_forms, get_form, create_form, update_form_settings, and list_submissions — against the same API the rest of FormBackend uses. Quotas, plan limits, and project permissions are enforced exactly like they are in the web app.

Why we built it

Most of our users already live in an AI assistant for some part of their day. Tabbing back to the FormBackend dashboard to copy a form token, eyeball a submission count, or tweak a setting is a small but constant context switch. MCP lets the assistant do it without leaving the window — and without us having to build a custom integration for every tool that wants one. One server, every MCP-compatible client.

Connecting in 30 seconds

The fastest path is Claude Code:

claude mcp add --transport http formbackend https://www.formbackend.com/mcp

The first request opens your browser, you log in to FormBackend, approve the consent screen, and the token is stored automatically. No API key juggling.

For Claude.ai (web and Desktop) you add it under Settings → Connectors → Add custom connector with the same URL. Cursor reads ~/.cursor/mcp.json. Full setup blocks for each client, plus the API-key alternative for scripts and CI, are in the MCP server documentation.

Scopes and revoking access

OAuth connections request three scopes — forms_read, forms_write, and submissions_read — and you’ll see exactly which ones are being asked for on the consent screen. Every connected assistant shows up on your authorized applications page, and revoking one immediately invalidates its tokens.

Try it

If you’ve got a FormBackend account, the server is live right now — no flag, no waitlist. Connect your assistant, ask it to list your forms, and let us know what you end up using it for.

For the full reference, see the MCP server documentation.