All tools
- Form checker: paste a page address and get the problems in its forms, such as a missing action, fields without a name or no spam protection
- AI builder prompts: ready prompts for Claude Code, Windsurf and the builders with a setup guide
- Agent rules files: AGENTS.md and similar files that tell a coding agent how to wire the form
- Formgong MCP server: let an agent create a form and get its snippet without leaving the editor
A typical setup
- Before you build, add the rules file for your agent to the project: AGENTS.md, CLAUDE.md, a Cursor rule or .windsurfrules. It tells the agent to send the form to Formgong with your public access key and never to write a secret into the code.
- Ask your AI tool for the form with the prompt for that tool. The prompt describes the fields, the spam protection and where the form sends its data, so the tool does not invent its own email backend.
- Publish the site and run the form checker on the live page. It reads the HTML once and lists what would stop messages from arriving, with a fix for each problem.
- If your agent supports MCP, it can create the form in your account and fetch the snippet itself, so you don't copy the access key by hand.
Questions
Which tool should I start with?
If the form is already live, run the form checker. If you are about to build it, copy the prompt for your AI tool. If your agent supports MCP, connect it so it can create the form for you.
Do I need an account?
Not for the form checker: it is free and works with any form. The prompts and rules files are plain text you can copy. The MCP server works with a Formgong API token, so it needs an account.
Sources
Checked on 04.10.2026 against these public pages: Formgong /agents.md, Formgong MCP.