Skip to main content
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

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 is free.
  • A form in the dashboard. 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:
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:

​
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:

​
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:
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

Stuck? Write to help@formcarry.com. Include the form id.