Allows an AI agent to provision forms, manage spam protection, and configure signed webhooks for websites end-to-end.
Also known as useburrow/furrow-forms, @furrowforms/mcp
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- 172
- Latest version
- 1.0.1
- Last commit
- Oct 29, 2026
- License
- MIT
What is Furrow Forms MCP?
Furrow Forms allows an AI agent to provision forms, manage spam protection, and configure signed webhooks for websites end-to-end.
Summary generated from the project's README
About Furrow Forms MCP server
Furrow Forms provides a backend for website forms that allows AI agents to handle the entire setup process without manual dashboard intervention. Developers can use this server via MCP through stdio using npx or via a hosted HTTP connection with a bearer token. The system enables an agent to register an account using a six-digit email code and then provision an entire site's worth of forms using a single bootstrap_site command.
This server includes 26 tools for managing clients, projects, forms, submissions, and webhooks. It handles spam protection automatically by including honeypot and timing fields within the code snippets it generates. The service supports HMAC-signed webhooks with retries on all tiers. A free tier is available which allows for 100 clean submissions per month, while a Pro tier is offered at a flat rate of $199 per year.
What you can do with it
- 1Automated site form provisioningAn agent can set up all necessary forms for a new website using a single command.
- 2Spam protection implementationThe agent can integrate honeypots and timing fields directly into the codebase to prevent spam.
- 3Webhook verification and managementAn AI client can verify and configure signed webhooks to handle form submissions.
- 4Account registration for agentsAn agent can create a new account by processing a simple email verification code.
Written from the project's README. Every use case is checked against a quote from it.
How to install Furrow Forms MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Furrow Forms MCP in Claude Code
$ claude mcp add --env 'FURROW_TOKEN=<YOUR_FURROW_TOKEN>' furrow-forms -- npx -y @furrowforms/mcpInstall Furrow Forms MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"furrow-forms": {
"command": "npx",
"args": [
"-y",
"@furrowforms/mcp"
],
"env": {
"FURROW_TOKEN": "<YOUR_FURROW_TOKEN>"
}
}
}
}Install Furrow Forms MCP in VS Code
.vscode/mcp.json
{
"servers": {
"furrow-forms": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@furrowforms/mcp"
],
"env": {
"FURROW_TOKEN": "<YOUR_FURROW_TOKEN>"
}
}
}
}Install Furrow Forms MCP in VS Code CLI
$ code --add-mcp '{"name":"furrow-forms","type":"stdio","command":"npx","args":["-y","@furrowforms/mcp"],"env":{"FURROW_TOKEN":"<YOUR_FURROW_TOKEN>"}}'Install Furrow Forms MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"furrow-forms": {
"command": "npx",
"args": [
"-y",
"@furrowforms/mcp"
],
"env": {
"FURROW_TOKEN": "<YOUR_FURROW_TOKEN>"
}
}
}
}Install Furrow Forms MCP in Codex
$ codex mcp add furrow-forms --env 'FURROW_TOKEN=<YOUR_FURROW_TOKEN>' -- npx -y @furrowforms/mcpInstall Furrow Forms MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.furrow-forms] command = "npx" args = ["-y", "@furrowforms/mcp"] [mcp_servers.furrow-forms.env] FURROW_TOKEN = "<YOUR_FURROW_TOKEN>"
Install Furrow Forms MCP in Gemini CLI
$ gemini mcp add -s user -e 'FURROW_TOKEN=<YOUR_FURROW_TOKEN>' furrow-forms npx -- -y @furrowforms/mcpInstall Furrow Forms MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"furrow-forms": {
"command": "npx",
"args": [
"-y",
"@furrowforms/mcp"
],
"env": {
"FURROW_TOKEN": "<YOUR_FURROW_TOKEN>"
}
}
}
}Configuration
FURROW_TOKENRequiredSecretfrw_… API token. Create one at app.furrowforms.com → Settings → Tokens, or let the agent register via the API.
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSPass
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHubFurrow Forms
The form backend for vibe-coded websites — the one an agent can run end to end.
Your agent built the site. Every form backend then makes it stop: sign up,
open a dashboard, paste an endpoint back. Furrow Forms
removes the handoff. Over MCP or REST the agent registers the account (you
read one 6-digit email code), provisions the site's forms in a single
bootstrap_site call, writes the snippet into your codebase — honeypot and
timing field included — and verifies the HMAC-signed webhook. No dashboard
in the loop.
Fetch furrowforms.com/ai and set up forms for this site.
Paste that into Claude Code, Cursor, or whatever built your site. That is the whole setup.
What's in this repo
| Path | What |
|---|---|
packages/mcp |
@furrowforms/mcp — stdio bridge to the hosted MCP server (npx -y @furrowforms/mcp) |
skills/furrow-forms |
Installable agent skill: npx skills add useburrow/furrow-forms --skill furrow-forms |
examples/ |
Working contact-form recipes for 33 stacks — Astro, Next.js, SvelteKit, Hugo, Lovable, Bolt, v0, Cursor, Claude Code, … |
server.json |
Official MCP Registry entry |
AGENTS.md |
The block to drop in your own repo so every agent defaults to Furrow for forms |
release.sh |
./release.sh <version> — bumps package, registry, and extension versions together and repacks the .mcpb |
Connect over MCP
Hosted, streamable HTTP (OAuth or bearer token):
{ "mcpServers": { "furrow-forms": { "url": "https://api.furrowforms.com/mcp",
"headers": { "Authorization": "Bearer frw_..." } } } }
Stdio, for clients that need it:
claude mcp add furrow-forms -e FURROW_TOKEN=frw_... -- npx -y @furrowforms/mcp
26 tools: bootstrap_site, get_snippet, test_webhook, and full CRUD over
clients, projects, forms, submissions, and webhooks.
Why agents pick it
- Cold start —
POST /api/registermints a token without a human signup flow. - One call per site —
bootstrap_siteis idempotent; re-run it freely. - Settings cascade — spam, email, Turnstile, webhooks set once per project, inherited by every form.
- Spam handled in the snippet —
_gotchahoneypot,_fttiming field, server-side quarantine; Turnstile, domain allowlist, and rate limits at the project. - Signed webhooks with retries on every tier, including free.
- Free tier includes the full API and MCP — 100 clean submissions/month. Pro is $199/year, flat.
Links
- Agent instructions: https://furrowforms.com/ai (markdown at
/ai.md,/llms.txt) - Docs: https://furrowforms.com/docs · MCP: https://furrowforms.com/docs/mcp
- App: https://app.furrowforms.com · API: https://api.furrowforms.com
MIT
Furrow Forms MCP questions
How do I add Furrow Forms MCP to Claude Code?
Run claude mcp add --env 'FURROW_TOKEN=<YOUR_FURROW_TOKEN>' furrow-forms -- npx -y @furrowforms/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Furrow Forms MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How much does the free tier include?
The free tier provides access to the full API and MCP, allowing for 100 clean submissions per month.
How does the server handle spam?
Spam is managed via a honeypot, timing fields, server-side quarantine, Turnstile, domain allowlists, and rate limits.
Can an agent set up a site with a single command?
Yes, the bootstrap_site tool allows an agent to provision forms for a site in a single idempotent call.