Jotform Sign

Draft e-signature documents, manage signers and email a signature request.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Jotform Sign connector does

The Jotform Sign MCP server connects Jotform's e-signature product to Claude, ChatGPT and any MCP-compatible agent. Its ten tools draft signable documents from a description, edit them, set signers and signing order, email the request out, and track who has signed. Sign-in is OAuth, and the write grant is account-wide rather than sign-specific.

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.

Jotform Sign tools (10)

  • create_sign_document
  • display_sign_document
  • edit_sign_document
  • update_sign_document_content
  • get_signers
  • update_signer
  • get_signing_status
  • send_for_signature
  • list_submissions
  • mcp_app_request
  • search

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. sendForSignature emails a contract to named signers, the signer list is itself agent-writable through updateSigner, 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. readOnly and full are the only options, they are identical across all three Jotform MCP servers, and every write tool including the send needs full.
  • mcp_app_request makes the tool count misleading. It forwards to Jotform's documented REST API across five HTTP verbs including DELETE, 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, getSigningStatus and listSubmissions. 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_HEADER to 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 community on 2026-08-16 and partner on 2026-08-23. Our Jotform Apps page records the older value.

Frequently asked questions

Can the Jotform Sign connector email a signature request to someone else?

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.

How many Jotform Sign tools change state?

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.

Can the Jotform Sign connector void, cancel or delete a signed document?

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.

What signer personal data can the Jotform Sign connector read?

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.

Which OAuth scopes does the Jotform Sign MCP server request?

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.

Is Jotform Sign the same connector as the Jotform MCP server?

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.

Does sending a signature request cost anything?

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.

What does the mcp_app_request tool do on the Jotform Sign server?

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

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Jotform Sign to work.

Connect Jotform Sign once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.