Jotform Sign
by Jotform Sign
Draft e-signature documents, manage signers and email a signature request from an AI agent. Ten tools, enumerated identically by Jotform and Anthropic. One tool sends to third parties; nothing voids, cancels or deletes.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Jotform Sign via MCP
https://mcp.jotform.com/mcp-sign-v1Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Jotform Sign Tools & Capabilities (10)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- One tool sends irreversibly to third parties.
sendForSignatureemails a contract to named signers, the signer list is itself agent-writable throughupdateSigner, and no tool here unsends. Counter-recommendation: do not add this tool to a blanket auto-approve list. - Nothing cancels, voids or deletes. Jotform's Sign Inbox can cancel a request not yet fully signed; this connector cannot. The absence protects the record and removes the brake at once.
- The scope pair is account-wide and does not separate send from draft.
readOnlyandfullare the only options, they are identical across all three Jotform MCP servers, and every write tool including the send needsfull. mcp_app_requestmakes the tool count misleading. It forwards to Jotform's documented REST API across five HTTP verbs includingDELETE, so the reachable operation count is the size of that API rather than ten. Jotform marks it private to the rendered UI; that is a model-behaviour mitigation, not a credential boundary.- Sending spends a metered quota that no tool can read. Signed documents are capped monthly by plan (10 free, 100 Bronze, 250 Silver, 1,000 Gold) and no tool reports usage, balance or billing. Jotform publishes no idempotency key for the send, so a timed-out call must not be retried blind.
- A widget send path exists that no tool audit covers. Jotform's rendered Sign interface carries a Send to Sign control. It acts on the user's click rather than the model's call, and we did not test it. Unverified, not absent.
- The read surface reaches counterparty personal data. Signer names, email addresses, signing order and per-signer timestamps are returned by
getSigners,getSigningStatusandlistSubmissions. Whether audit-trail contents are also reachable is undetermined. - Signer delegation adds recipients you did not name, and Jotform documents delegation as irreversible once performed.
- No tool schemas or safety annotations were readable. The endpoint returned HTTP 401 with body
NO_AUTH_HEADERto an anonymous handshake on 2026-08-23, so no parameter detail,readOnlyHint,destructiveHint, prompts or resources could be observed. Tool behaviour comes from Jotform's documentation; the read/write split is our classification. - A UI-rendering client is required. Jotform lists this as a requirement, and two of the ten tools are documented as callable only by the rendered interface.
- Installation is admin-gated. Only workspace admins can install the underlying Jotform MCP app.
- Jotform's own documentation is internally inconsistent about how many servers exist. The default developer page states Jotform offers "two" MCP experiences while the MCP App tab of the same page presents "three options". Anthropic lists three connectors.
- The tier changed recently. Anthropic listed this connector
communityon 2026-08-16 andpartneron 2026-08-23. Our Jotform Apps page records the older value.
Frequently asked questions
Yes. sendForSignature is documented by Jotform as sending a sign document to its configured signers by email, and it is the only tool here that reaches outside your account. The recipients are whoever updateSigner or the document already set, so confirm the signer list before approving the call. No tool in this connector recalls that email.
Four of the ten. createSignDocument makes a new document, editSignDocument rewrites an existing one, updateSigner changes a signer's name, email address and signing order, and sendForSignature emails the request out. The other six read: getSigners, getSigningStatus, listSubmissions, search, displaySignDocument and the private mcp_app_request dispatcher, which reads or writes depending on the call.
No tool among the ten carries a void, cancel, delete or archive verb. Jotform's product does have cancellation — the Sign Inbox offers a Cancel Document button for requests not yet signed by all parties — but that action has no counterpart in this tool surface. So an agent can send a request it cannot take back, and cleanup means opening Jotform.
Names, email addresses, roles, signing order, per-signer timestamps and signing activity. getSigners returns signer details and status, getSigningStatus reports each signer's progress and timestamps, and listSubmissions lists signatures and signing activity across documents. That is counterparty personal data belonging to people who never consented to your AI client seeing it.
Two, and they are account-wide. The server's RFC 9728 descriptor advertised readOnly and full on 2026-08-23, the same pair the Jotform and Jotform Apps servers advertise. There is no sign-only, send-only or document-scoped option, so granting the write access sendForSignature needs also grants write access to every Jotform resource your account holds.
No. Jotform runs separate MCP endpoints with separate tool sets, and Anthropic lists three of them. Jotform at mcp.jotform.com/mcp-app handles forms and submissions, Jotform Apps at mcp-jotform-apps-v1 builds portals, and Jotform Sign at mcp-sign-v1 handles signable documents. Connecting one gives an agent none of the others.
It consumes your plan's monthly signed-document allowance. Jotform's pricing data sets that allowance at 10 documents a month on the free Starter plan, 100 on Bronze, 250 on Silver and 1,000 on Gold. No tool in this connector reports usage, remaining quota or billing, so an agent can spend the allowance without any tool that could check it first.
It is a fallback dispatcher over Jotform's REST API. Jotform documents it as covering documented REST endpoints across GET, POST, PUT, PATCH and DELETE when no dedicated tool fits, limited to your account and granted scopes. Jotform marks it private so the assistant never picks it, but the token still reaches whatever it can call.
Sources
- Jotform MCP Server documentation, MCP App tab — the vendor's own tool table for all three interactive servers, and the documentation URL Anthropic publishes for this connector (fetched 2026-08-23, HTTP 200; a current browser user agent is required or the page serves an unsupported-browser stub) · retrieved 2026-08-23
- Jotform MCP Server documentation, default tab with no query parameter — source of the Enterprise rate limit, the no-additional-charge statement, the HIPAA position and the self-hosting note.
- Jotform MCP Server documentation, standard MCP tab — the OAuth, revocation, admin-install and bearer-token statements (fetched 2026-08-23) · retrieved 2026-08-23
- How to Track the Signing Process of Other Parties — Sign Inbox tabs, the Cancel Document button, the statement that canceled documents cannot be restarted, and the audit-trail field list (fetched 2026-08-23) · retrieved 2026-08-23
- How to Send a Document for Signature With Jotform Sign — the recipient, signing-order, expiration and CC options, and confirmation that signers receive an emailed invitation (fetched 2026-08-23) · retrieved 2026-08-23
- How to Use Jotform Sign — the audit-trail email setting and the completion notification (fetched 2026-08-23) · retrieved 2026-08-23
- How to Allow Signers to Delegate the Document to Other Signers — delegation behaviour and its irreversibility (fetched 2026-08-23) · retrieved 2026-08-23
- Does Jotform Sign Offer Legally Binding Signatures? — the ESIGN and UETA compliance statement (fetched 2026-08-23) · retrieved 2026-08-23
- How to Create a Sign Document Using ChatGPT — the rendered panel's Send to Sign and Edit in Jotform controls (fetched 2026-08-23) · retrieved 2026-08-23
- Jotform pricing — the signed-document limit definition, and the per-plan allowances read from the page's embedded plan data because the comparison table is client-rendered (fetched 2026-08-23) · retrieved 2026-08-23
- Live anonymous probe, 2026-08-23 —
initializeand a plain GET onhttps://mcp.jotform.com/mcp-sign-v1each returned HTTP 401 with body{"message":"NO_AUTH_HEADER"}and noWWW-Authenticateheader · retrieved 2026-08-23 - Live RFC 9728 protected-resource descriptor —
https://mcp.jotform.com/.well-known/oauth-protected-resourceand the/mcp-sign-v1path-insert form, both HTTP 200 advertisingreadOnlyandfull; the path-append form returns 401 (fetched 2026-08-23). Themcp-appandmcp-jotform-apps-v1descriptors were fetched for comparison and advertise an identical scope list · retrieved 2026-08-23 - Live RFC 8414 authorization-server metadata —
https://oauth2.jotform.com/.well-known/oauth-authorization-server, mirrored identically athttps://mcp.jotform.com/.well-known/oauth-authorization-server(fetched 2026-08-23) · retrieved 2026-08-23 www.jotform.com/robots.txtpermits/developers/,/help/,/products/and/pricing/, and carries noContent-Signaldirective on any axis;/llms.txtand/llms-full.txtboth return HTTP 404. Help-article slugs were resolved fromhttps://www.jotform.com/sitemaps/help/sitemap.xml.gz, named inrobots.txt, rather than guessed (checked 2026-08-23) · retrieved 2026-08-23- Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-23; the 2026-08-16 snapshot listed the same server at
communitytier · retrieved 2026-08-23 - Jotform support — · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Jotform Sign
- Tools
- 10
- Domain
- mcp.jotform.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.