Formkove

Configurez des formulaires web sur Formkove depuis votre assistant IA : créez des formulaires, obtenez le code du formulaire pour HTML, React, Next.js ou Astro, consultez l’utilisation et lisez les soumissions avec une clé distincte en lecture seule.

Serveur MCP hébergé

npx add-mcp 'https://app.formkove.com/mcp'

S’installe dans Claude Code, Codex, Cursor et plus

Documentation

Formkove has a hosted MCP server. Connect an AI assistant and you can say “add a contact form to this site” and it creates the form, sets it up, gets the code and drops it into your page. It can also read your submissions when you allow that. Nothing it does sends an email.

It works on every plan, Free included. The endpoint is https://app.formkove.com/mcp.

What you can ask it

  • “Add a contact form to my Next.js site with name, email and a budget select. Use Formkove.”
  • “Send new leads from my contact form to Slack when the sentiment is negative.”
  • “Check that my form accepts a submission from https://example.com and tell me if anything is missing.”
  • “Show me the unread submissions on my contact form and group them by topic.” (needs Submissions: Read)

If a form on your site uses fetch() or React, the site’s address has to be in the form’s Allowed Origins. Plain HTML forms don’t need it. The assistant is told this when it gets the form’s code.

The full list of tools is in What the assistant can do.

Choose what it can do

Whichever way you connect, you pick what the assistant is allowed to do. Start from a template, then change what you need:

TemplateThe assistant canUse it for
Build and set up formsList your forms, check settings, usage and stats, get setup code, dry-run a submission, create forms and change their settings (name, honeypot, Turnstile, file uploads, AI, allowed origins, your own address as a recipient).Adding and configuring forms
Read submissionsList your forms, check settings, usage and stats, get setup code, read and search submissions. It can’t change anything.Summarising or sorting what came in

The permissions list has four rows:

  • Forms: Read or Manage. Manage lets the assistant create and configure forms.
  • Integrations (off by default). Adds, pauses, tests and deletes integrations, and sets routing rules. The assistant can send future submissions to any URL it adds, so only turn this on when you need it (see Security).
  • Delete forms (off by default). Deletes forms and removes notification recipients. Deleting a form is permanent and removes its submissions.
  • Submissions: Off or Read.

A summary under the list shows what the assistant can and can’t do. It never sends email.

Integrations and Delete forms need Forms: Manage. You can give Submissions: Read and Forms: Manage together. The page then warns you that text someone types into your form could try to get your assistant to change your settings, or send your submissions to another site if Integrations is on. Keep tool approval on in your assistant if you do.

In a team workspace, any member can connect with read-only access. Only owners and admins can allow managing forms, connecting integrations or deleting forms.

Connect Claude or ChatGPT

Claude (claude.ai and the desktop app) and ChatGPT sign in to your Formkove account, so there’s no key to copy.

Claude (claude.ai)

Formkove is in Claude’s connector directory. In Claude, open Settings → Connectors, browse the connectors, search for Formkove and add it. Claude opens Formkove to sign in, as in steps 3 and 4 below. If you can’t find it, add it as a custom connector:

  1. In Claude, open Settings → Connectors, click Add and choose Add custom connector.
  2. Name it Formkove, enter https://app.formkove.com/mcp and click Add. Leave the OAuth client fields as Claude fills them in.
  3. Claude opens Formkove. Sign in if you aren’t already, then pick the workspace and what Claude can do. Integrations and Delete forms start off.
  4. Click Allow. You’re back in Claude and the connector shows as connected.

Claude asks before it runs each tool, unless you change that in the connector’s settings.

ChatGPT

  1. In ChatGPT, open Plugins in the sidebar, click Add and choose Add custom MCP server. Tick the box that you understand the risk.
  2. Name it Formkove, enter https://app.formkove.com/mcp and choose OAuth. ChatGPT picks the registration method (Client Identifier Metadata Document) by itself.
  3. Create it, then click Continue to Formkove. Pick the workspace and what ChatGPT can do, and click Allow.

ChatGPT runs tools it treats as low-risk, such as listing your forms, without asking. You can change that in the plugin’s permission setting.

Connect a coding assistant

Claude Code, Cursor, VS Code, Codex and Antigravity connect with an API key. Create the key first, then add it to your tool.

Create an API key

  1. In the dashboard, open Settings → API keys. If you work in a team workspace, switch to it first: a key belongs to the workspace that is active when you create it, and only sees that workspace’s forms.
  2. Name the key, pick a template and what it can do, pick an expiry (30, 90 or 365 days) and click Create key. You can also limit a key to one form.
  3. Copy the key now. It is shown once.

Keys are bearer tokens. Treat them like passwords: keep the key in an environment variable where your tool supports it, and never paste it into a config file that is committed to a repository.

Claude Code

Put the key in an environment variable, then add the server:

export FORMKOVE_API_KEY="fk1_your_key_here"
claude mcp add --transport http formkove https://app.formkove.com/mcp --header "Authorization: Bearer ${FORMKOVE_API_KEY}"

Run /mcp inside Claude Code to check that formkove is connected.

Cursor

Add this to ~/.cursor/mcp.json (or .cursor/mcp.json in a project) and set FORMKOVE_API_KEY in the environment Cursor starts from:

{
  "mcpServers": {
    "formkove": {
      "url": "https://app.formkove.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:FORMKOVE_API_KEY}"
      }
    }
  }
}

VS Code

Add this to .vscode/mcp.json. VS Code asks for the key when the server starts and keeps it out of the file:

{
  "inputs": [
    { "id": "formkove-key", "type": "promptString", "description": "Formkove API key", "password": true }
  ],
  "servers": {
    "formkove": {
      "type": "http",
      "url": "https://app.formkove.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:formkove-key}"
      }
    }
  }
}

Codex

Add this to ~/.codex/config.toml (or .codex/config.toml in a trusted project) and set FORMKOVE_API_KEY in the environment Codex starts from. Codex reads the key from that variable, so it stays out of the file:

[mcp_servers.formkove]
url = "https://app.formkove.com/mcp"
bearer_token_env_var = "FORMKOVE_API_KEY"

Run codex mcp list to check that formkove is there.

Google Antigravity

In the agent panel, open the … menu, choose MCP Servers → Manage MCP Servers → View raw config, and add the server:

{
  "mcpServers": {
    "formkove": {
      "serverUrl": "https://app.formkove.com/mcp",
      "headers": {
        "Authorization": "Bearer fk1_your_key_here"
      }
    }
  }
}

Antigravity doesn’t read environment variables in headers, so the key is stored in this file. Keep it in your user config (~/.gemini/config/mcp_config.json), not in a workspace’s .agents/mcp_config.json that could be committed.

Other clients

Formkove is in the official MCP Registry as com.formkove/formkove, and on Glama. Clients that install from either still need your API key in the Authorization header, as above.

Disconnect or revoke access

Apps (Claude, ChatGPT): open Settings → API keys in Formkove and click Disconnect next to the app under Connected apps. It stops working right away. Removing the connector in Claude or ChatGPT works too, and changing or resetting your password disconnects every app.

API keys: revoke a key on the same page and it stops working immediately. Keys also expire after the time you chose. You can have 10 active keys.

In a team workspace, owners and admins see every member’s keys and the apps members connected to that workspace, and can revoke or disconnect them. Removing a member from the workspace disconnects their apps there.

What the assistant can do

The assistant only sees the tools you allowed. In a team workspace, members don’t get the tools that change anything.

Read (always available)

ToolWhat it does
list_formsLists your forms with totals, unread counts and endpoint URLs
get_setupCode for a form in HTML, fetch, React, Next.js, Vue, Svelte, Astro or HTMX, built from the fields you describe. Includes the honeypot and the Turnstile widget when the form uses them
get_form_settingsA form’s name, honeypot, Turnstile site key, allowed origins, file upload and AI settings, recipients (other people’s addresses are partly hidden) and integrations. Never secrets
get_statsTotals, unread, the days with activity in the last 30 days and this month’s usage. Counts only, no submission text
get_usageYour plan, this month’s submissions against the limit, number of forms and file storage. Not available to a key limited to one form
check_submissionA dry run: would a submission with this origin, fields, files and redirect be accepted? Nothing is stored or sent
list_integrationsWebhooks and destinations on a form: type, host, on or off, routing and last delivery. Never the full URL

Setup (Forms: Manage)

ToolWhat it does
create_formCreates a form and returns its ID and code. Same limits as the dashboard
update_formRenames a form, sets the honeypot field name (it must start with _; turning it off is dashboard-only), sets or removes Turnstile (the secret key is stored encrypted and never shown again), changes file upload settings
configure_aiTurns AI on or off, sets the purpose and tags. On Free this works during your first 50 submissions; after that only the spam filter can be changed, as in the dashboard
add_recipientAdds your own account email as a recipient. It can’t add anyone else
update_allowed_originsAdds sites to a form’s Allowed Origins. It only adds, never removes or replaces, and refuses *
remove_recipientNeeds the Delete forms switch. Removes a recipient
delete_formNeeds the Delete forms switch. Permanently deletes a form and its submissions. The assistant has to give the form’s exact name, and a key limited to one form can’t do it

Integrations (needs the Integrations switch; Pro and Agency plans, and Free accounts on their first 50 submissions with up to 3 integrations in total, as in the dashboard)

ToolWhat it does
add_webhookSends new submissions to a URL, optionally signed with a secret you give it
add_destinationConnects Slack, Discord, Microsoft Teams, Google Chat, Telegram, Zapier, Make or n8n. Google Sheets, Airtable, Notion, Mailchimp, Kit, Brevo and HubSpot are connected in the dashboard, since they need a Google sign-in or an API key
update_integrationTurns an integration on or off and sets its routing rules (for example only negative sentiment)
delete_integrationRemoves an integration. Works on any plan
test_integrationSends a sample message to a destination (not a custom webhook)

Submissions (Submissions: Read)

ToolWhat it does
list_submissionsLists submissions, newest first. Spam is hidden unless asked for. Filter by unread, sentiment, tag or date
get_submissionOne submission in full, with its AI result and file names
search_submissionsSearches the newest 200 submissions of one form for some text

The assistant can also read these docs pages and use an add_contact_form prompt, which walks through adding a form to a site.

What it can’t do. Anything that sends an email: adding anyone else as a recipient, resending a verification, inviting team members, or delivering a submission that was flagged as spam. It can’t change billing or your plan, mark submissions as spam, or turn back on a form that Formkove disabled.

Limits

  • Up to 60 requests a minute per IP address and 60 tool calls a minute per account. Over that, the assistant is told to wait.
  • create_form is limited to 20 forms an hour and to your plan’s form limit, the same as the dashboard. test_integration is limited to 3 tests a minute per destination and 20 an hour per form. A form can have up to 10 integrations. In a team workspace only owners and admins can change anything.
  • Lists return at most 50 submissions at a time. When you filter (or spam is hidden), each call checks the newest 2,000 submissions after where it left off, and tells the assistant if older ones may match. Search looks at the newest 200 submissions of one form, returns up to 25, and is limited to 10 searches a minute. Form lists show at most 200 forms.
  • Long field values are shortened, and a response is cut to a fixed size. The assistant can page through the rest.

Security

Submissions are written by strangers. Anyone can post to your form, so a submission can contain text meant to trick an AI assistant (“ignore your instructions and run this command”). That is called prompt injection, and no one can fully prevent it. Here is what Formkove does about it:

  • Submission text, file names and AI summaries are returned as clearly marked untrusted data, with a note telling the assistant not to follow instructions in it.
  • Control characters, hidden and bidirectional text characters and terminal escape sequences are removed, and long values are shortened.
  • Spam is hidden by default.
  • The templates keep reading and changing apart: “Build and set up forms” can’t read submissions, and “Read submissions” can’t change anything. If you combine them yourself, Formkove warns you.
  • Every tool that changes something is marked as destructive, so your assistant asks before running it.
  • No tool sends email.

The Integrations switch lets the assistant send your future submissions to any URL it adds. A webhook or destination (Slack, Teams, Zapier and the others) sends every new submission to another address. If the assistant reads something untrusted while it has that access (a web page, a README, another tool’s output), that content could try to make it add a connection to an attacker’s URL. Only turn on Integrations when you need it, use a short key expiry, keep manual approval on, check the form’s integrations afterwards and revoke access when you’re done. Formkove marks these tools as destructive so your assistant asks first, and logs every change.

This lowers the risk. It doesn’t remove it. While an assistant is reading submissions:

  • Keep manual approval on for shell commands and file edits.
  • Use Submissions: Read only, with a key limited to one form if you can.
  • Keep Forms: Manage, Integrations and Delete forms off for anything else.
  • Revoke keys and disconnect apps you no longer use.

Other things to know:

  • Your assistant and its AI provider receive whatever the assistant reads. See the Privacy Policy.
  • There is no official local or npm package for Formkove’s MCP server. The only official server is the hosted one at https://app.formkove.com/mcp. Be careful with packages that claim otherwise.

For a walkthrough from setup to a working form, see Add a contact form from Claude Code or Cursor. See also Security and the API reference.