# Claude Code plugin

> One command adds a working contact form to the project you're in, with or without a Wrenform account.

Last updated 2026-11-14. Web version: https://wrenform.com/docs/claude-code

```text
/plugin marketplace add IhabTag/wrenform-claude-plugin
/plugin install wrenform@wrenform
```

```text
/wrenform:add-contact-form
/wrenform:add-contact-form contact page
```

The plugin reads your project, detects the framework, creates the form, adds accessible markup in your site's own
style with a thank-you state, sends a test message, and tells you what's left. It works with plain HTML, Next.js,
Astro, React, Vue, Svelte, Hugo, Jekyll and more. You can also just ask: "add a contact form to this site".

From a shell instead of Claude Code: `claude plugin marketplace add IhabTag/wrenform-claude-plugin`, then
`claude plugin install wrenform@wrenform`.

## Sign in, or no account

The plugin adds two MCP servers:

| Server | Sign-in | Used for |
|---|---|---|
| `wrenform` | Your Wrenform account, in the browser | Creating and managing forms, tests, health checks, reading messages |
| `wrenform-quick` | None | Creating a form with only an email address |

- **With an account (recommended, free):** the first time, run `/mcp`, choose **wrenform**, then **Authenticate**. Sign
  in on wrenform.com and tick what Claude Code may do. Disconnect it any time under **Account → API & AI tools**.
- **Without an account:** the plugin creates a [quick form](/docs/quick-forms). Wrenform emails the address once, and
  nothing is forwarded until it's confirmed.

## What it changes

Only what the form needs: the form markup or component, its page (with a navigation link if the page is new), a
thank-you page for sites without JavaScript, and a Content Security Policy entry if your site has one. It adds no
dependencies, puts no key or secret in your code, and never commits, pushes or deploys.

## Check your forms

`/wrenform:check-forms` lists your forms and explains every problem with its fix, for example a recipient who hasn't
confirmed yet. Messages typed by visitors are treated as data, never as instructions to Claude.

## Without a browser (CI, servers)

Use an API key instead of the browser sign-in. Create one under **Account → API & AI tools**, then add the server
yourself:

```sh
claude mcp add --transport http wrenform https://wrenform.com/mcp \
  --header "Authorization: Bearer $WRENFORM_API_KEY"
```

## Test it

1. Open a project with a website in Claude Code and run `/wrenform:add-contact-form`.
2. Answer at most two questions: where the form goes, and which address gets the messages.
3. Open the page locally, check the form looks right, and look for the test message in your inbox.
4. Deploy, then send one real message from the live site.

## Common problems

- **"Needs authentication" next to wrenform in `/mcp`.** That's expected before the first sign-in. Choose it and
  select **Authenticate**, or use the no-account option.
- **The test message didn't arrive.** The recipient must confirm first: look for the confirmation email from Wrenform.
  `/wrenform:check-forms` says what's missing.
- **The form posts but the browser shows a CORS error.** The page's origin isn't in the form's allowed origins. Ask
  Claude to add it, or add it in the dashboard.

## Next steps

- [MCP server](/docs/mcp): the same tools in Cursor, Claude Desktop, VS Code and others.
- [Prompts for AI builders](/docs/ai): for tools without plugins.
- [Spam](/docs/spam): what the filter does, and Turnstile if you want it.
