# Use FormDoc with AI coding assistants

> Connect FormDoc to Claude Code, Cursor or any MCP client so your assistant can create a form, add it to your site and test it.

FormDoc has an MCP server, so an AI coding assistant can add a working form to your site for you: it creates the form, waits while you confirm your email, pastes the code into the right file and sends a test. The same tools work from your terminal.

Everything runs with `npx`, so there is nothing to install first. You need Node.js 18 or newer.

## Connect your assistant

**Claude Code**

SH

```sh
claude mcp add formdoc -- npx -y @formdocdev/cli mcp
```

Or install the [FormDoc plugin for Claude Code](https://www.formdoc.dev/docs/claude-code-plugin/), which adds the MCP server together with a forms skill and a hook that checks every form Claude writes.

**Claude Desktop, Cursor and other MCP clients**

Add this to the client’s MCP settings file:

JSON

```json
{
  "mcpServers": {
    "formdoc": { "command": "npx", "args": ["-y", "@formdocdev/cli", "mcp"] }
  }
}
```

Then ask, for example: “Add a contact form to this site with FormDoc.”

## What the assistant can do

| Tool | What it does |
| --- | --- |
| `create_form` | Creates a form for your email address. You get a confirmation email; the access key appears when you click it. |
| `get_verification_status` | Checks whether the form is confirmed and active. |
| `get_snippet` | Returns a ready, accessible form for HTML, Astro or vagejs, with your key filled in. |
| `send_test_submission` | Sends one real test, which arrives in your inbox and counts toward your monthly limit. |
| `check_forms_in_project` | Scans your project for forms that post to FormDoc and lists problems, such as a missing key, a GET method or fields without a name. |

The assistant is told to ask for your real email address and never to make one up. Your access key is public, so it is safe for the assistant to see and to put in your HTML.

## From the terminal

SH

```sh
npx @formdocdev/cli create --email you@example.com
npx @formdocdev/cli status fd_your_access_key
npx @formdocdev/cli snippet fd_your_access_key --framework astro
npx @formdocdev/cli test fd_your_access_key
npx @formdocdev/cli check .
```

`check` exits with code 1 when it finds problems, so you can run it in CI before you deploy.

## Teach your assistant the rules

The MCP server gives your assistant tools; rules tell it how to write forms. The [Claude Code skill generator](https://www.formdoc.dev/tools/claude-skill-generator/) writes FormDoc’s form rules as a Claude Code skill, or for CLAUDE.md, AGENTS.md, Cursor and Copilot. The [Claude Code hook generator](https://www.formdoc.dev/tools/claude-code-hook-generator/) makes Claude check each form it writes.

## Common questions

### Does the assistant need my password or an API token?

No. Creating a form only needs your email address, and you confirm it yourself by clicking the link FormDoc sends. Nothing the assistant sees can read your submissions.

### Which assistants does it work with?

Any client that supports MCP servers over standard input and output, including Claude Code, Claude Desktop and Cursor.

### Can the assistant list or change my existing forms?

Not yet. Today it creates new forms, writes their code and checks your project. Manage existing forms in the FormDoc dashboard at app.formdoc.dev.