Jotform Sign

@Jotform Sign list all forms in my account and show me which ones have active webhooks configured

Found 12 forms in your Jotform account. Three have active webhooks: 'Customer Onboarding' (form ID 240123456789012) has 2 webhooks pointing to Zapier and Slack; 'Employee NDA' (240234567890123) has 1 webhook to your CRM; 'Vendor Agreement' (240345678901234) has no webhooks. The remaining 9 forms have no webhook integrations. Note that these are general Jotform forms—this MCP does not distinguish whether they are Jotform Sign documents or standard forms.

This example combines two read operations (list forms, then check webhooks for each). Useful for auditing integrations. The MCP returns all forms visible to your API key, including soft-deleted ones, and does not filter by Jotform Sign status—you'll see every form type in the results.

@Jotform Sign create a new submission for form 240123456789012 with question 3 answered 'Acme Corp' and question 5 answered 'accepted'

Submission created successfully with ID 5678901234567890123. Question 3 (company name) set to 'Acme Corp', question 5 (terms acceptance) set to 'accepted'. This submission is now visible in your Jotform account and has permanently consumed one submission from your monthly quota. Important: this creates an ordinary form submission—it does not trigger Jotform Sign's document-sending workflow or generate a signed PDF.

This write action permanently consumes your monthly submission quota even if you later delete the submission via API. The MCP creates standard Jotform submissions, not Jotform Sign signature requests—use this for programmatic form filling, not document signing workflows. Requires knowing question IDs from the form schema.

@Jotform Sign get the schema for form 240123456789012, then check if any submissions in the last week have question 7 marked as 'urgent'

Form schema retrieved: 8 questions including question 7 ('Priority Level', dropdown with options normal/high/urgent). Checking recent submissions—found 23 submissions in the past 7 days. Five have question 7 set to 'urgent': submission IDs 5678901234567890120 through 5678901234567890124, all created between March 15-17. The 'urgent' submissions came from three different email addresses. This analysis required fetching the schema first to understand question 7's structure, then iterating through submissions to filter by answer value.

This synthesis example shows the MCP's strength in programmatic form inspection and data filtering. The AI must chain two operations: schema inspection to understand field structure, then submission retrieval to analyze answers. Useful for building custom dashboards or alerts, but remember each submission fetch counts toward API rate limits.

When Jotform Sign simplifies distributed new-hire packets

A 6-person agency hiring contractors across three states needs I-9s, NDAs, and direct-deposit forms signed before day one. Jotform Sign works here because the MCP lets an agent pre-fill forms with HR-system data, trigger sends, and poll submission status without opening the Jotform dashboard. The Create Submission tool permanently consumes your monthly quota, so this only makes sense if you're already paying for a Jotform plan and want to automate the 3-5 forms each hire requires. If you're onboarding more than 20 people a month, budget the submission burn carefully—each test run counts. The buying call: use this when you need signature collection wired into a Slack or email workflow, not when you're manually sending one-off contracts.

Why this MCP fits discovery-call follow-up automation

A 3-person consultancy closes 8-12 new clients a quarter and sends a scope-of-work form after every discovery call. The Jotform Sign MCP shines here because an agent can read the CRM note, pre-fill the SOW with project details, and queue the signature request while the consultant is still on Zoom. The Get Form Schema and List Forms tools let the agent pick the right template without hard-coding form IDs. The threshold: if your intake forms change weekly or you're A/B testing question wording, the MCP's schema-inspection overhead slows you down—just use Jotform's native Zapier hooks instead. This wins when your forms are stable and you want signature collection inside a larger workflow, not as a standalone step.

When webhook polling beats this MCP for multi-signer flows

A 12-person ops team routes purchase orders through finance, legal, and the department head before vendor execution. Jotform Sign supports multi-party signing, but this MCP's toolset is thin on orchestration: you can create a submission and check its status, but you can't programmatically add signers mid-flight or react to partial-completion events without polling List Form Webhooks and parsing payloads yourself. If your approval chain has conditional branches—skip legal under $5k, add the CFO over $50k—you'll spend more time managing state than the MCP saves. The buying call: use this for straight-line, everyone-signs-in-order workflows where you just need to kick off the packet and check if it's done. For conditional routing, Jotform's Zapier integration or a custom webhook listener is the better play.