# furrow-forms [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/useburrow/furrow-forms  
**GitHub Stars:** 1  
**npm Downloads (last month):** 203  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/furrow-forms

## Description
Form backend an agent runs end to end: provision forms, snippets, spam, signed webhooks.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "furrow-forms": {
    "command": "npx",
    "args": ["-y","@furrowforms/mcp"],
    "env": {
      "FURROW_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `FURROW_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What furrow-forms does

The furrow-forms MCP server gives an AI coding agent access to Furrow Forms, a hosted backend for website forms. It supports end-to-end setup rather than only submission storage: an agent can register an account, create the site's form resources, retrieve the code snippet, and verify webhook delivery.

The repository describes 26 MCP tools. These include `bootstrap_site`, `get_snippet`, and `test_webhook`, along with create, read, update, and delete operations for clients, projects, forms, submissions, and webhooks. The service also supports signed webhooks with retries. Form snippets include a `_gotcha` honeypot and `_ft` timing field; server-side handling can quarantine suspected spam.

## How it works

The furrow-forms MCP server can be reached through the hosted streamable HTTP endpoint at `https://api.furrowforms.com/mcp`. Clients authenticate with OAuth or a bearer token. For clients that need a local process, the repository provides `@furrowforms/mcp`, a stdio bridge installed and run with `npx -y @furrowforms/mcp`.

An agent can use `bootstrap_site` to provision a site's forms in one idempotent operation, so repeating the call does not require a separate manual setup flow. Project-level settings cascade to forms in that project. These settings include spam controls, email, Turnstile, webhooks, domain allowlisting, and rate limits. The README also documents an account-registration endpoint that issues a token after the user reads a six-digit email code.

## Setup and configuration

For HTTP access, configure the MCP client with the hosted URL and an `Authorization: Bearer frw_...` header. For stdio access, pass the token as `FURROW_TOKEN` when launching the package. The repository also provides an installable agent skill and an `AGENTS.md` block for making Furrow Forms the default form backend in a project.

The project includes working contact-form examples for 33 stacks, including Astro, Next.js, SvelteKit, Hugo, Lovable, Bolt, and v0. These examples can help an agent adapt the returned snippet to an existing codebase.

## Tools and capabilities

- Provision a site's forms with `bootstrap_site`.
- Retrieve integration code with `get_snippet`.
- Check webhook behavior with `test_webhook`.
- Manage clients, projects, forms, submissions, and webhooks through CRUD tools.
- Configure project-level spam, email, Turnstile, domain, rate-limit, and webhook settings.
- Receive HMAC-signed webhooks with retries.

## Limitations and notes

The hosted service is external to the repository, so using the MCP endpoint requires a Furrow Forms token. The stdio package is a bridge to that hosted service, not a local form-processing backend. The free tier includes the full API and MCP and allows 100 clean submissions per month; the README lists a Pro plan at $199 per year. A human still needs to read the six-digit email code during the documented registration flow.

_Full upstream README: https://allmcps.com/mcp/furrow-forms/readme_