Jotform Sign for AI agents
Jotform Sign covers the forms, submissions, and webhook side of Jotform's e-signature workflows, used to collect and route signed documents. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Jotform Sign.
Check a submission's status
Check whether a sent signature form has been completed by the signer.
List forms available for signing
List forms configured for signature workflows to find the right one for a new document.
Register a webhook for updates
Register a webhook on a form so completed signatures trigger a downstream notification.
10 Jotform Sign actions, graded by risk.
Every Jotform Sign action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
6Look things up. Allowed by default.
- jotform_sign.list_formsList Forms
- jotform_sign.get_submissionGet Submission
- jotform_sign.get_form_schemaGet Form Schema
- jotform_sign.list_form_filesList Form Files
- jotform_sign.list_submissionsList Submissions
- jotform_sign.list_form_webhooksList Form Webhooks
write
2Create and change things. Allow, or ask the user first.
- jotform_sign.create_submissionCreate Submission
- jotform_sign.register_form_webhookRegister Form Webhook
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- jotform_sign.delete_submissionDelete Submission
- jotform_sign.delete_form_webhookDelete Form Webhook
Jotform Sign in three steps.
- 01Your users connect Jotform SignThey add their Jotform Sign api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Submission” can wait for the user, and “delete Submission” can be denied outright.
- 03Any agent can actYour agent calls Jotform Sign through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('jotform_sign', { read: 'allow', write: 'ask', // create_submission destructive: 'deny', // delete_submission }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Jotform Sign connects.
Users add their Jotform Sign api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Jotform Sign connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Jotform Sign from any agent.
Jotform Sign and Arc0, answered.
Can I use Jotform Sign with Claude, ChatGPT or Cursor?
Yes. Connect Jotform Sign to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Jotform Sign actions you allow.
How do users connect Jotform Sign?
Users add their Jotform Sign api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Jotform Sign actions can my agent take?
10 in total: 6 read, 2 write and 2 destructive, such as “create Submission”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Jotform Sign?
Yes. Actions like “delete Submission” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Jotform Sign too?
Yes. The same Jotform Sign connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Jotform Sign into your agent.
Your users connect Jotform Sign once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan