Formcarry
Server Details
formcarry handles everything after your form is submitted: it emails you, auto replies to the person who submitted, filters spam, and delivers webhooks. You write the HTML form and set its action to a URL formcarry gives you. An agent can create a form, wire the emails and webhooks, and answer questions about the submissions, like how many signups last week.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- formcarry
TDQS
Scored across 23 tools
Every tool targets a distinct resource and action: forms, submissions, webhooks, recipients, deliveries, teams, and email servers are cleanly separated. The potentially overlapping list_submissions, search_submissions, and count_submissions are explicitly differentiated by purpose (known form vs. unknown form vs. counting).
All 23 tools follow a consistent verb_noun snake_case pattern: add_, remove_, create_, update_, delete_, get_, list_, count_, search_, mark_, restore_, redeliver_. There are no mixed conventions or vague verbs.
23 tools is on the heavier side, but each tool maps to a clear workflow area and earns its place across forms, submissions, webhooks, and notifications. It is slightly beyond the ideal range but not bloated or redundant.
The surface covers form CRUD (minus delete), submission lifecycle including spam handling and deletion, webhook lifecycle with delivery logs and redelivery, recipient management, and team/email server lookup. Minor gaps exist—notably no delete_form and no single-webhook getter—but the core workflows are well covered.
Publisher details
- Operator
- Formcarry · Publisher source
- Operator website
- https://formcarry.com · Publisher source
- Vendor relationship
- Not applicable
- Documentation
- Unknown
- Privacy policy
- Not provided
- Trust center
- Not applicable
- Restrictions
- No setup restrictions
Available Tools
23 toolsadd_recipientAdd a recipientAIdempotentInspect
Adds one address to the list that receives the email on every submission and keeps the others; an address already on the list changes nothing. The free plan allows one address. Returns the whole list. (To replace the list, pass self_email_notification.recipients to update_form.)
Inputs: email (required), form_id (required).
count_submissionsCount submissionsARead-onlyIdempotentInspect
How many submissions match, instead of the submissions themselves. Call this before listing when you do not know how big an answer is, so you can narrow it rather than paging blindly. Takes the same filters as list_submissions. Pass group_by to count by day, week, month, country, spam, read, or field: for a submitted field, and the largest 20 groups come back with the rest in "other". group_by field: is also how you learn what a field holds before filtering on it: the buckets are its distinct values, and a field in filter then selects up to 20 of them. A count that runs out of time returns what it reached with exact false: say so rather than presenting it as the whole number, and narrow the date range for an exact one.
Inputs: form_id (required), q, read, field, +6 more.
create_formCreate a formAInspect
Creates a form and returns it with the endpoint URL to post submissions to. Pass name and, optionally, any configuration block (see update_form); what you leave out gets the defaults. The same rules as the dashboard apply (plan form limit, one notification address on the free plan, features the plan includes), and a refused configuration creates nothing. team_id is required when the connection covers several teams.
Inputs: name (required), spam, active, storage, +6 more.
create_webhookAdd a webhookAInspect
Adds a webhook that receives every submission as a JSON POST. The result carries the signing secret once; tell the user to store it. A form takes up to 10 webhooks (webhook_limit_reached past that) and one webhook per URL (webhook_url_taken). Needs a plan that includes webhooks.
Inputs: url (required), form_id (required), events, enabled, +1 more.
delete_submissionDelete a submissionADestructiveIdempotentInspect
Permanently deletes one submission. Cannot be undone; attachments stay in storage.
Inputs: form_id (required), submission_id (required).
delete_webhookDelete a webhookADestructiveIdempotentInspect
Removes a webhook, so no later submission is delivered to it. A delivery already queued or being retried can still complete. Adding it again issues a new secret.
Inputs: form_id (required), webhook_id (required).
get_formGet a formARead-onlyIdempotentInspect
One form with its full configuration: storage, spam protection, the notification email, the auto response, what the visitor sees after submitting, validation rules, its webhooks (read-only here, see list_webhooks), plus its endpoint URL and submission counts.
Inputs: form_id (required).
get_form_fieldsDiscover form fieldsARead-onlyIdempotentInspect
The field names the newest 2,000 submissions of this form carry, most used first, each with a count and the date it was last seen. Read the counts before you filter: "email" on 2,000 of 2,000 is what people send today, while a name on 11 of them, last seen months ago, was renamed and will return an empty page. At most 200 names, so a form with many rare names can hide one; q finds text without naming a field.
Inputs: form_id (required).
get_submissionGet a submissionBRead-onlyIdempotentInspect
One submission with its fields, attachments and metadata.
Inputs: form_id (required), submission_id (required).
get_submission_deliveriesWhat happened to submissionsARead-onlyIdempotentInspect
What happened to up to 20 submissions after they arrived: every email, webhook, Zapier zap and integration each one was handed to, with the latest outcome of each, and one status per submission rolled up from its rows (succeeded, partial, failed, bounced, retrying, pending, skipped, or null when nothing is on record). Read the rows to say why: pending or retrying means read again in a minute; bounced means the address rejected the email; SKIPPED_PLUGIN_DISABLED means the feature is off on the form; SKIPPED_PLAN_LIMIT means the plan cut it; SKIPPED_SPAM means the submission was spam. Ids the form does not have are left out. A submission received seconds ago can have no rows yet, and the log is kept 18 months.
Inputs: form_id (required), submission_ids (required).
list_email_serversList email serversARead-onlyIdempotentInspect
The email servers the teams have set up in the dashboard, to use as a form's notification sender: email_server is an SMTP server, premium_server a verified sending domain. Put the id in self_email_notification.sender.server_id.
Inputs: no named parameters.
list_formsList formsARead-onlyIdempotentInspect
Forms the connection can see, newest first, paginated with next_cursor. Pass team_id to list one team only.
Inputs: limit, cursor, team_id.
list_submissionsList submissionsARead-onlyIdempotentInspect
Submissions of one form, newest first. Search in this order: read a page of recent submissions to see the field names people are sending now, widen that list with get_form_fields when you need more names, use q for a first pass when you do not know which field holds the text, then narrow with field filters. When you do not know how many submissions an answer covers, call count_submissions before paging through them, and when you do not know what values a field holds, call it with group_by field: and select the ones you want with a field in filter. Filters combine with AND: q, status (inbox, spam, all), read, has_attachments, created_after, created_before, country, and up to 5 field filters (eq, contains, starts_with, exists, in). Pass fields to return only the values you need when you are scanning many submissions. Follow next_cursor until it is null. Not possible here, so say so rather than approximating: no totals in this tool, no "not equal" or "does not contain", no greater than or less than on a value, and no sorting by anything but time. To compare numbers, filter to the submissions that have the field, pass fields to read just that value, and compare them yourself.
Inputs: form_id (required), q, read, field, +9 more.
list_teamsList teamsARead-onlyIdempotentInspect
The formcarry teams this connection can reach, with the permissions granted for each. Call first when you are not sure which team a form belongs to.
Inputs: no named parameters.
list_webhook_deliveriesList webhook deliveriesARead-onlyIdempotentInspect
The delivery log of one webhook, newest first: one entry per submission with its latest outcome (succeeded, failed, retrying, pending, skipped), the HTTP status the endpoint answered and the error text when it did not. Filter by status; page with limit (1 to 100, default 25) and before (the previous page's last occurred_at).
Inputs: form_id (required), webhook_id (required), limit, before, +1 more.
list_webhooksList webhooksARead-onlyIdempotentInspect
The form's webhooks: url, enabled, description, events, and how deliveries are signed. Up to 10 per form.
Inputs: form_id (required).
mark_submission_spamMark a submission as spamAIdempotentInspect
Moves a submission to the spam folder and answers with its id and the new spam flag. Reversible with restore_submission.
Inputs: form_id (required), submission_id (required).
redeliver_webhookSend a submission to a webhook againADestructiveInspect
Queues one submission for the delivery worker again, for this webhook only, signed afresh, and answers when it is queued, not when it is delivered: read the delivery log for the outcome. A paused webhook receives it too. Sending again repeats whatever the endpoint does with it. Refused when the form keeps no submissions (submission_not_stored).
Inputs: form_id (required), webhook_id (required), submission_id (required).
remove_recipientRemove a recipientADestructiveIdempotentInspect
Removes one address from the list that receives the email on every submission and keeps the others. Returns the whole list; recipient_not_found when the address is not on it.
Inputs: email (required), form_id (required).
restore_submissionRestore a submission from spamAIdempotentInspect
Moves a submission back to the inbox and answers with its id and the new spam flag. There is no undo for deletions; this only clears the spam flag.
Inputs: form_id (required), submission_id (required).
search_submissionsSearch submissions across formsARead-onlyIdempotentInspect
Searches the 25 most recently active forms the connection can read and returns matches with the form each came from. Use it when you do not know which form holds what you are looking for; use list_submissions when you do, because that one pages through a single form completely. Takes the same filters. When the answer carries complete false, say the search was partial and narrow it with form_ids, team_id or a date range.
Inputs: q, read, field, limit, +8 more.
update_formUpdate a formADestructiveIdempotentInspect
Changes only what you pass. Nested objects are merged (passing after_submit.page.headline changes just the headline), lists (recipients, rules) are replaced as a whole. Blocks: storage, spam, self_email_notification (the email you get on every submission), auto_response, after_submit, validation, plus name, active and folder_id. Webhooks have their own tools. Features the plan does not include are refused with the dashboard's message.
Inputs: form_id (required), name, spam, active, +6 more.
update_webhookUpdate a webhookADestructiveIdempotentInspect
Changes only what you pass on one webhook: url, enabled, description, events. The secret does not change.
Inputs: form_id (required), webhook_id (required), url, events, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Hosted form backend for coding agents: create form endpoints, verify submissions, manage webhooks.
Backend for any website form: create forms, read and triage submissions, debug webhooks.
Form backend with an inbox: create form endpoints, read submissions and reply by email.
Form backend an agent runs end to end: provision forms, snippets, spam, signed webhooks.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to create and wire up contact forms, retrieve framework-specific copy-paste snippets with real access keys, inspect form configuration, and read inbox or spam submissions. It also stores marked test submissions to confirm a form is live without sending email.73 npmMIT

sounnyforms-mcpofficial
AlicenseAqualityCmaintenanceEnables AI agents to submit and triage leads via email, check endpoint health, and generate production-ready form code across multiple frameworks without requiring API keys.49 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to build and operate production-ready forms, quizzes, surveys, and workflows, including creation, publishing, submission management, and integration with webhooks and analytics.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create and manage forms, read responses as JSON or CSV, and lets visitors authorize their own agents to fill and submit forms with one-time codes.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.