AI site builders · works with Furrow Forms
The form backend Cursor’s agent can register, provision, and verify on its own.
paste this into your agent
Fetch furrowforms.com/ai and set up forms for this site.agent-readable recipe: /forms-for/cursor.md
prefer clicking? start in the dashboard
<form action="https://api.furrowforms.com/s/fp_k7m2" method="POST">
<input type="text" name="_gotcha" style="display:none" tabindex="-1" />
<input type="hidden" name="_ft" value="" />
<script>document.currentScript.previousElementSibling.value = Date.now();</script>
<input name="name" type="text" required />
<input name="email" type="email" required />
<textarea name="message" required></textarea>
<button type="submit">Send</button>
</form>The gap
Cursor will happily build the whole site — pages, styles, the contact form markup — and then stop at the form’s action attribute, because every form backend expects a human to go sign up and paste an endpoint back. Furrow Forms removes that handoff. Its control plane is MCP and REST from the first call: the agent registers the account (you read one email code), provisions the site and forms in a single bootstrap_site call, writes the snippet into your codebase, and verifies the webhook. Setting up forms becomes one more prompt in the same chat that built the site.
Cursor can write the form but not the backend — until now it had to ask you to sign up somewhere. With Furrow, cold-start registration over POST /api/register means the agent creates the account too and keeps going.
Every snippet the agent writes ships with a honeypot, a timing field, and quarantine. Hand it Turnstile keys and it configures those at the project level as well.
One workspace runs every site you ship. Spam policy, notify emails, and webhooks are set per project and inherited by every form — so the agent sets up site five exactly like site one.
Two ways in
Furrow’s whole control plane is an API and MCP server. Paste this prompt into Claude Code, Cursor, or any agent — it does the rest:
paste this into your agent
Fetch furrowforms.com/ai and set up forms for this site.free tier: 100 subs/mo · unlimited forms · full API + MCP · pricing →
FAQ
The URL is enough: /ai carries the full REST reference, so the agent can register, provision, and verify with plain HTTP calls. Adding the Furrow MCP server (streamable HTTP or stdio) gives it the same operations as typed tools, which is nicer for ongoing changes.
No. The agent calls POST /api/register, Furrow emails you a 6-digit code, you paste it into the chat, and the agent receives a team-scoped token. That is the only human step.
It edits your form markup: sets the action to your Furrow submit URL, adds a hidden _gotcha honeypot and an _ft timing field, and (if you gave it keys) the Turnstile widget. Nothing else — there is no SDK to install and no server route to add.
paste this into your agent
Fetch furrowforms.com/ai and set up forms for this site.