Feathery

@Feathery list all forms in my workspace and show me which ones have the most submissions this month

Based on your workspace data, here are your active forms: 'Customer Onboarding' (247 submissions), 'Product Feedback Survey' (189 submissions), 'Support Ticket Intake' (156 submissions), 'Newsletter Signup' (94 submissions), and 'Contact Us' (67 submissions). The Customer Onboarding form is seeing the highest activity, with submissions concentrated in the first two weeks of the month. This example illustrates typical form analytics available through the Feathery MCP.

This read-heavy example demonstrates the MCP's ability to surface form metadata and submission counts. Requires API key authentication with read permissions on forms. Actual submission counts and form names will vary by your workspace state. The MCP can retrieve form lists but may not expose all analytics dimensions available in the Feathery dashboard.

@Feathery create a new hidden field called 'utm_source' in my Customer Onboarding form to track where signups are coming from

Hidden field 'utm_source' has been created in your Customer Onboarding form (form ID: frm_abc123). This field will now capture UTM source parameters automatically when users submit the form, but won't be visible to form fillers. You can map this field to your CRM or analytics tools through Feathery's integration settings. Remember to update any existing form embeds to pass the utm_source parameter if you're using custom URL tracking.

This write example shows the MCP's form modification capabilities. Creating hidden fields is permanent and affects live forms immediately — test in a staging environment first. You must provide a unique field_id that doesn't conflict with existing fields. The MCP can create the field but won't automatically configure downstream integrations or data mappings.

@Feathery review all users created in the last week and draft an email summarizing their signup patterns and common form abandonment points

I've analyzed 43 users created between March 10-17. Key patterns: 68% signed up via the Customer Onboarding form, with peak activity on Tuesday afternoons. Common abandonment occurs at Step 3 (payment information) — 29% of users drop off here, suggesting friction with the credit card input field. Another 15% abandon at Step 5 (document upload), likely due to file size confusion. Draft email: 'This week's signup data shows strong Tuesday engagement but reveals two friction points: payment entry (29% drop-off) and document uploads (15% drop-off). Consider adding inline help text at these steps or simplifying required fields.' This synthesis combines user creation data with form completion analytics.

This synthesis example pairs the MCP's user-fetching tools with AI reasoning to identify trends. Requires API access to both user records and form submission data. The MCP provides raw data; the AI interprets patterns and drafts communications. Abandonment analysis depends on Feathery tracking partial submissions — verify this is enabled in your workspace settings before relying on these insights.

When Feathery wins for multi-step user onboarding flows

A 6-person B2B SaaS team needs to collect customer data across a 4-step signup flow—company details, payment info, team invites, and document signing. Feathery is the right call here because the MCP lets you script the entire form lifecycle from Switchy: create hidden fields to pre-fill known user data, generate workspace login tokens so customers land in the right context, and trigger document template fills when contracts need signing. The 19 tools cover form CRUD, user provisioning, and document generation in one integration. If your onboarding is a single-page form with no conditional logic, Feathery is overkill—stick with a lighter form tool. But if you're stitching together multi-step flows with backend state and document workflows, this MCP collapses what would otherwise be three separate integrations into one Switchy workspace.

How Feathery handles dynamic support form routing

A 3-person support team at a fintech startup uses Feathery forms to triage inbound tickets—customers fill out a form, and hidden fields route the submission to the right queue based on account tier and issue type. The Feathery MCP lets the team script form updates from Switchy without touching the Feathery UI: create or update hidden fields when routing logic changes, fetch user SDK keys to embed forms in the help center, and delete deprecated forms when workflows evolve. The API key auth means any team member can run these scripts without sharing credentials. The threshold: if your support flow is static (same form, same fields, no routing), you don't need this level of control. But if you're iterating on intake logic weekly or running A/B tests on form structure, the MCP saves hours of manual clicking in the Feathery dashboard.

When Feathery scales lead gen across client accounts

A 5-person marketing agency manages lead capture forms for 12 clients, each with their own Feathery workspace. The MCP is the right fit because it lets the agency script bulk operations from Switchy: generate workspace login tokens to access each client's forms, create hidden fields to tag leads by campaign source, and delete old forms when campaigns end. The edit account tool lets the agency adjust permissions as client teams grow. The trade-off: if you're managing forms for a single brand with one workspace, the MCP's multi-account tooling is more than you need—just use Feathery's UI. But if you're juggling 10+ workspaces and need to replicate form structures or audit field usage across clients, this integration turns a week of manual work into a 20-minute Switchy script.