> ## 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. # Replit > Replit Agent connects the form it built to formcarry from one prompt in the Agent chat. Agent reads `replit.md` at the project root on every request, so a rule you keep there applies to each request that follows. ## Connect over MCP 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. Replit Agent connects to it as an MCP server, so it manages the form it built instead of only writing the front end. ## 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 examples use `https://formcarry.com/s/AbC123xyz`; put yours in its place. * The form's name and id from its page in the dashboard, for the prompt. ## 1. Provide the instructions Type the prompt into the Agent chat, 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 "
" (id ) to the form in this project, send a test submission and tell me what you changed. ``` Agent builds every web app with a front end and a back end. Ask it to post to formcarry from the browser rather than from a server route, otherwise no spam blocker token exists. Agent creates `replit.md` at the project root itself, and you can edit it. To keep the rule for later requests, add it there: ```text theme={null} Post to formcarry from the browser, never from a server route. Read https://formcarry.com/llms.txt before changing the form. ``` ## 2. Check what it changed Open History in the Agent panel: each checkpoint shows what changed and has a Changes control. The folder icon on the left opens the file tree. Check in the form's code: * The endpoint from the Setup page in the form's `action` or the `fetch` URL. * `method="POST"`. * A `name` on every field, and `email` on the address field. * `Accept: application/json` when it posts from JavaScript. * The request runs in the browser, not in a server route. If the request is in a server route, reply: ```text theme={null} Post to formcarry from the browser, not from a server route. ``` ## 3. Send a test submission Press Run and fill the form in the Preview. The Preview is the app itself, at a temporary `*.replit.dev` URL reachable on the internet. The submission is on the form's page in the dashboard and the notification email arrives at your account's address. Devtools in the Preview tab lists the request and its status under Network. With `Accept: application/json`, a stored submission answers with: ```json theme={null} { "code": 200, "status": "success", "title": "Thank You!", "message": "We received your submission" } ``` Without the header the browser lands on formcarry's thank you page. A second test inside 15 seconds from the same address gets a `429`. Wait 15 seconds, then send again. ## Publishing * Publishing makes a separate copy at its own URL. Edits reach it only when you select Republish, so publish again after Agent connects the form. * A Static deployment has no back end and does not fit an app Agent built. Publish as Autoscale or Reserved VM. ## 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 - [Build with AI](/docs/ai/overview.md) - [Introduction](/docs/introduction.md)