Formcarry
Formcarry is a form API that allows you to collect submissions from your own designed HTML forms without coding any backend, providing features like email notifications, file uploads, spam protection, and integrations with other apps.
Verdict
Common use cases
- Triage new leads during morning standup
- Spot recurring support questions across submissions
- Pull contact requests for outreach campaigns
- Review event registrations before sending confirmations
- Audit form spam patterns by date range
Integration
- Vendor
- Formcarry
- Category
- other
- Auth
- API_KEY
- Tools
- 1
- Composio slug
formcarry
Tools
- Retrieve Form Submissions
Tool to retrieve a list of submissions for a specific form identified by its id. supports pagination to navigate through large sets of submissions.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations > Add Integration. 2. Search for Formcarry and click Connect. 3. Log into your Formcarry dashboard at formcarry.com, go to Account Settings, and copy your API key from the API Access section. 4. Paste the API key into Switchy's connection dialog and click Authorize. 5. Switchy will verify the key and confirm the connection. 6. Open any Space and type '@Formcarry retrieve submissions for form [your-form-id]' to test — the MCP will return your most recent entries. 7. Find your form ID in the Formcarry dashboard by clicking on a form and copying the alphanumeric string from the URL or form settings. 8. If you manage multiple forms, repeat the command with different form IDs to confirm access across your account.
What teammates see: by default, memories from Formcarry are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Summarize Recent Leads
@Formcarry retrieve the last 20 submissions for form abc123 and summarize them by topic. Highlight any urgent requests or repeat inquiries.Open in a Space →
Weekly Submission Report
@Formcarry get all submissions from the past week for form abc123. Count total entries and list the five most common questions or topics.Open in a Space →
Filter by Email Domain
@Formcarry retrieve submissions for form abc123 and filter for email addresses ending in @example.com. List names, messages, and submission dates.Open in a Space →
Identify Spam Patterns
@Formcarry pull the last 50 submissions for form abc123 and flag any that look like spam based on repeated text, fake emails, or gibberish content.Open in a Space →
Export Contact List
@Formcarry retrieve all submissions from the last 30 days for form abc123. Extract names and email addresses into a formatted list I can copy.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Formcarry show me the last 20 submissions from our contact form, grouped by submission date
Retrieved 20 recent submissions from form ID fc_abc123. The data shows 8 submissions from today, 7 from yesterday, and 5 from two days ago. Each entry includes the submitter's email, message content, timestamp, and any custom fields you've configured. The most recent submission came in 14 minutes ago from contact@example.com with subject 'Partnership inquiry'.
This example demonstrates the read-only retrieval capability. You'll need your form ID from the Formcarry dashboard and an API key with read permissions. The MCP returns raw submission data — the AI can then group, filter, or summarize it based on your prompt. Pagination kicks in automatically for forms with hundreds of entries.
@Formcarry pull all submissions from the past 7 days that mention 'pricing' or 'enterprise' in the message field
Scanned 143 submissions from the past week and found 11 matches containing 'pricing' or 'enterprise'. Five explicitly asked about enterprise licensing, four requested custom pricing quotes, and two mentioned both terms in the context of team plans. The earliest match was 6 days ago; the most recent was this morning. All 11 include contact details for follow-up.
This showcases the AI's ability to filter and interpret submission content after retrieval. The MCP itself doesn't offer server-side search — it fetches submissions in bulk, then the AI scans the text. For forms with thousands of entries, you may need multiple paginated requests, which can approach rate limits on high-volume accounts.
@Formcarry summarize common themes from our feedback form submissions this month and draft a response template for the top issue
Analyzed 87 feedback submissions from March. Three recurring themes emerged: 1) Mobile responsiveness issues (mentioned in 34 submissions), 2) Confusion about the checkout flow (18 mentions), 3) Requests for dark mode (12 mentions). The mobile responsiveness complaints cluster around tablet viewport widths. Here's a draft response: 'Thank you for reporting the mobile display issue. We're aware of the tablet layout problem and our team is prioritizing a fix in the next sprint. We'll notify you once it's deployed.'
This example pairs retrieval with synthesis — the MCP fetches raw submissions, then the AI identifies patterns and generates a response. Useful for turning unstructured form data into actionable insights. Keep in mind the AI sees only what the MCP retrieves; if your form has conditional fields or file uploads, those may require separate handling outside this integration.
Use-case deep-dives
When Formcarry works for small sales teams tracking inbound leads
A 3-person sales team runs a contact form on their site and reviews new leads every Monday morning. Formcarry's single retrieval tool pulls submissions by form ID with pagination, which means the team can ask Switchy to summarize this week's leads, flag high-intent prospects, or compare volume week-over-week without opening the Formcarry dashboard. The API key auth keeps setup under two minutes. This works cleanly if you're processing under 200 submissions per week and your form structure is stable. If you need to update form fields, archive old submissions, or manage multiple forms across different sites, you'll hit the tool's read-only limit fast. For teams that just need a weekly digest of who filled out the form and what they said, this MCP saves the context-switching tax.
Formcarry as a lightweight feedback inbox for early-stage products
A 4-person product team embeds a feedback form on their beta app and wants to triage user requests during sprint planning. Formcarry's retrieval tool lets Switchy pull all submissions since the last sprint, group them by theme, and surface the most-requested features without anyone logging into a separate tool. Pagination handles the case where you get 50+ submissions in a two-week cycle. The trade-off: you can't mark submissions as resolved, assign them to teammates, or push them into Linear or Jira from Switchy. If your feedback volume stays under 100 submissions per sprint and you're comfortable manually moving high-priority items into your project tracker afterward, this MCP keeps the initial review step fast. Once you're triaging 200+ pieces of feedback per cycle, you'll want a tool with write access and status tracking.
Using Formcarry to audit event signups before a launch
A 2-person ops team runs a webinar signup form and needs to reconcile registrations against their email platform the day before the event. Formcarry's submission retrieval tool pulls the full list with pagination, so Switchy can cross-check emails, flag duplicates, and identify incomplete signups in one query. The API key setup means the ops lead doesn't need to involve engineering. This scenario works if your event draws under 500 registrations and you're doing a one-time audit rather than real-time sync. If you need to update attendee status, send confirmation emails, or trigger Zapier workflows from Switchy, the read-only tool won't cut it. For teams running occasional events with straightforward forms, this MCP turns a 30-minute spreadsheet task into a 2-minute Switchy question.
Frequently asked
What does the Formcarry MCP do in Switchy?
It pulls form submissions from your Formcarry forms into Switchy so your AI agents can read, analyze, and act on them. You can retrieve submissions by form ID with pagination support for large datasets. This lets you build workflows that process contact forms, survey responses, or lead captures without manually exporting CSVs.
Do I need a Formcarry API key to connect this?
Yes. You'll need to generate an API key from your Formcarry account settings and paste it into Switchy during setup. The key authenticates read access to your forms and submissions. Anyone on your team with access to the Formcarry account can create one, but treat it like a password since it grants full read access.
Can the MCP send new form submissions or update existing ones?
No. This integration is read-only — it retrieves submissions but can't create or modify them. If you need to respond to form fills, you'll pull the data into Switchy and then use a different MCP like Gmail or Slack to send replies. Formcarry itself handles the actual form hosting and submission collection.
Why use this instead of Formcarry's webhooks or Zapier?
Webhooks push data when submissions arrive; this MCP lets your AI pull submissions on demand whenever it needs context. That's useful for batch analysis, historical lookups, or workflows that trigger from something other than a new form fill. If you just want real-time notifications, webhooks are simpler. If you want AI to reason over past submissions, use this.
Who on the team should connect the Formcarry MCP?
Whoever owns your Formcarry account or has access to generate API keys. Once connected in Switchy, any team member can use it in their AI workflows without needing their own Formcarry login. The connection doesn't count against Formcarry's submission limits, but you're still bound by their plan's storage and form quotas.