> ## Documentation Index
> Fetch the complete documentation index at: https://formcarry.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Build with AI

> An AI tool builds the form and connects it to formcarry from one prompt.

It reads formcarry's instructions for machines, writes the form into your project and sends a test submission.

## Connect over MCP

<Card title="Connect over MCP" icon="plug" href="/docs/connect" horizontal cta="See how to connect">
  Formcarry's MCP does everything you would do in the dashboard for your forms and submissions: create a form, set its recipients, spam blocker and webhooks, list and search submissions, mark spam, and read where each submission was delivered. Claude, Codex, Cursor and v0 connect to it, so the tool that writes your form also manages it from the chat. The prompt below still works without it.
</Card>

## Prerequisites

Before you start, you need:

* A formcarry account. [Sign up](https://app.formcarry.com/register) is free.
* A form in the [dashboard](https://app.formcarry.com). Its endpoint is on the form's Setup page.
* The form's name and id from its page in the dashboard, for the prompt.

## The prompt

To connect a form the tool built, paste this where the tool takes instructions, with your form's name and id in place of the placeholders:

```text theme={null}
Read https://formcarry.com/llms.txt for how the front end setup works, then connect my formcarry form "<form name>" (id <form_id>) to the form in this project, send a test submission and tell me what you changed.
```

The first sentence sends the tool to `https://formcarry.com/llms.txt`, a page written for machines that holds the whole contract: the endpoint, the field names, the JSON answer, files, the spam blocker and the limits.

The rest tells it what to do and to report back. The form's Setup page in the dashboard shows the same prompt with your form's details filled in.

## Two rules for every tool

* **Post from the browser.** Some tools put form handling on a server, where no spam blocker token exists. If the tool wrote a server route, reply "post to formcarry from the browser".
* **Check three things** in the code it wrote: the endpoint from the Setup page, a `name` on every field with `email` on the address field, and `Accept: application/json` when it posts from JavaScript.

## Pick your tool

* [Lovable](/docs/ai/lovable): the chat and the project's Knowledge.
* [v0](/docs/ai/v0): the prompt bar and saved Instructions; watch for Server Actions.
* [Replit](/docs/ai/replit): Agent chat and `replit.md`; Agent builds a backend by default.
* [Claude](/docs/ai/claude): Claude Code in your project, or claude.ai, where an artifact cannot post to the endpoint.
* [ChatGPT](/docs/ai/chatgpt): Canvas, or Codex in your project with `AGENTS.md`.

## What's next

* [What every form needs](/docs/what-every-form-needs): field names, hidden inputs, limits and the answers.
* [Spam protection](/docs/features/spam-protection): add a challenge once the form is live.
* [Connect over MCP](/docs/connect): let the tool manage the form, not only write it.

Stuck? Write to [help@formcarry.com](mailto:help@formcarry.com). Include the form id.


## Related topics

- [Connect over MCP](/docs/connect.md)
- [Introduction](/docs/introduction.md)
- [Claude](/docs/ai/claude.md)
- [Lovable](/docs/ai/lovable.md)
- [Replit](/docs/ai/replit.md)
