MCP App Store
by KeenEthics
Jotform Sign icon

Jotform Sign MCP Server for Claude and ChatGPT

By Jotform

Overview

Create, share, and edit e-sign documents right inside Claude with Jotform Sign. Generate agreements, forms, and other signable documents from simple prompts, then customize fields, recipients, signing order, and workflows through conversation. Send documents for signature and streamline approvals with legally binding e-signatures that work on any device. Perfect for creating contracts, onboarding paperwork, consent forms, and other documents that require signatures — without starting from scratch. Key Features Generate signable documents from natural language prompts Create contracts, agreements, forms, and approval documents in minutes Add signature fields, dates, initials, and other fillable fields Configure recipients, signing order, and approval workflows Send documents for secure, legally binding e-signatures Track document status and manage signed documents in one place Sign and complete documents from any device Create e-sign documents for all use cases, including: Employment contracts and onboarding documents Client agreements and service contracts NDAs and confidentiality agreements Consent and waiver forms Sales proposals and approval workflows Vendor and partnership agreements Rental and lease agreements Internal approvals, policies, and acknowledgments

How to connect

  1. Claude: Open the Jotform Sign listing in the Claude connectors directory and choose Connect. Claude listing Jotform Sign exposes 11 tools here.
  2. ChatGPT: Open the Jotform Sign listing in the ChatGPT app directory and choose Connect. ChatGPT listing Jotform Sign exposes 16 tools here.

Tools

assignFieldsToSigners

ChatGPT
Auto-detect fields in a sign document, create signer roles, and assign signature, date, and text fields to each signer. This tool handles both creating the signers and distributing the fields among them in one step.

bulkSendForSignature

ChatGPT
Send a sign document to multiple recipients in bulk using an uploaded file (CSV or spreadsheet) containing recipient names and emails. Each recipient gets their own copy of the document to sign independently. Useful when the same document (e.g. an NDA or waiver) needs to be signed by many people.

createSignDocument

ChatGPT
Create a signable document that can be sent to one or more signers for e-signature. Use this tool when the user wants to collect signatures, build a signing workflow, or prepare a document for signing. The document content is generated from a text prompt; an optional uploaded PDF, image, or DOCX can be passed as reference context (it is analyzed, not used as the final file).

create_sign_document

ChatGPT
Create a signable document that can be sent to one or more signers for e-signature. Use this tool when the user wants to collect signatures, build a signing workflow, or prepare a document for signing. The document content is generated from a text prompt; an optional uploaded PDF, image, or DOCX can be passed as reference context (it is analyzed, not used as the final file).

displaySignDocument

ChatGPT
Refresh and display an already-created signable document in the rendered App. Returns the document with fresh, time-limited file URLs so it can be previewed again after the previous URLs expire. Requires the document_id and form_id of an existing sign document.

display_sign_document

ChatGPT
Refresh an already-created signable document in the rendered App so it can be previewed again after its previous preview expires. The refreshed document is handed to the App, which renders it; the response reports which document was refreshed. Requires the document_id and form_id of an existing sign document.

downloadSignedDocument

ChatGPT
Return the completed, sealed PDF of a fully signed document including the audit trail. Only available once all signers have completed signing.

editSignDocument

ChatGPT
Edit an existing sign document. Can update the document title, regenerate the document content from a new prompt, or modify document settings.

edit_sign_document

ChatGPT
Edit an existing sign document. Can update the document title, regenerate the document content from a new prompt, or modify document settings.

getSigners

ChatGPT
Retrieve the list of signers (participants) on a sign document, including their participant IDs, names, emails, roles, and assigned fields. Use this to get participant IDs before updating signers.

getSigningStatus

ChatGPT
Report the current status of a sign document including overall document status and per-signer status (sent, viewed, signed) with key audit events and timestamps.

get_signers

ChatGPT
Retrieve the signers of a sign document or sign form — participants that have signature/date/text fields assigned to them — including their participant IDs, names, emails, roles, signing order, and signing status. When given a form ID, this returns signers across all of the form's documents (the editable draft plus every sent document), each annotated with its document ID and status. Participant roles with no assigned fields are excluded. Use this to see who has been sent a document and to get participant IDs before updating signers.

get_signing_status

ChatGPT
Report the current status of a sign document including the overall document status and per-signer status (sent, viewed, signed, declined) with key timestamps. Accepts a sign document ID or a sign form ID (as seen in the /sign/{id} builder URL); A sent document ID reports that copy only. A form ID or draft document ID aggregates all non-deleted sent copies, or reports the draft if no copies have been sent. Performs a single status lookup.

get_teams

ChatGPT
Retrieves team information for the user in Enterprise environments. Returns team details including members when returnBasicTeamInfo is false.

listSignDocuments

ChatGPT
List the user's sign documents with their current statuses. Supports filtering by status. Use this to help the user find or manage their documents.

listSubmissions

ChatGPT
List signatures and signing submissions for sign documents. Use this tool when the user wants to view who has signed, check signatures, or see signing activity. You can list submissions for a specific sign document by passing its form_id, or across all sign documents when form_ids is empty.

list_submissions

ChatGPT
List signatures and signing submissions for sign documents. Use this tool when the user wants to view who has signed, check signatures, or see signing activity. You can list submissions for a specific sign document by passing its form_id, or across all sign documents when form_ids is empty. Do NOT use this tool to list the user's sign documents themselves — use the sign document listing/search tool for that.

mcp_app_request

ChatGPT
Makes an authenticated request to the Jotform REST API with the given method, body, and query parameters. The API host is resolved automatically for the current account, so pass only a relative path. WHEN TO USE: Prefer a dedicated tool when one exists for the requested action (for example: create_form, edit_form, list_submissions, search, fetch, display_form, analyze_submissions). Only use this tool as a fallback when no dedicated tool covers the request. See https://api.jotform.com/docs/ for the full API reference. COMMON ENDPOINTS (relative paths, grouped by resource; not exhaustive): - User: "user", "user/forms", "user/submissions", "user/folders", "user/reports", "user/settings", "user/usage". - Form: "form/{formID}", "form/{formID}/questions", "form/{formID}/question/{questionID}", "form/{formID}/properties", "form/{formID}/properties/{propertyKey}", "form/{formID}/submissions", "form/{formID}/files", "form/{formID}/reports", "form/{formID}/webhooks". - Submission: "submission/{submissionID}". - Report: "report/{reportID}". - Folder: "folder/{folderID}". RULES: - Use a relative path with no leading slash and no "API/" prefix (use "user", not "/API/user" or "/user"). - The endpoints above are examples, not a complete list. You may use any documented Jotform API endpoint. Do not invent sub-resources; if unsure, start from a parent/collection endpoint above (for example "form/{formID}/properties") instead of guessing a new path. - "emails", "conditions", "products" and "formStrings" are not standalone endpoints and are not valid {propertyKey} values. They are returned as grouped sections of "form/{formID}/properties", so read them from there. - Treat a 404 as "this path does not exist" and report it, instead of retrying variations of the same path. TIP: To reference a specific question or property, first GET the parent collection ("form/{formID}/questions" or "form/{formID}/properties") and use the IDs/keys returned there instead of guessing.

sendForSignature

ChatGPT
Send a sign document to all assigned signers via email. Supports signing order, auto-reminders, and expiration settings. This action emails real people — confirm with the user before calling.

sendSignReminder

ChatGPT
Send a reminder email to pending signers who have not yet signed the document.

send_feedback

ChatGPT
Report unsupported user requests and missing capabilities in the current Jotform app to the Jotform team. Primary use: when the user requests an action that the available tools cannot perform, call this tool with category=missing_capability before explaining the limitation. The user does not need to ask for feedback or request a report. First establish the gap from the available tool descriptions or an explicit unsupported-operation result. Do not report missing input, authentication failures, permission restrictions, temporary errors, or an operation that the available tools can perform as missing capabilities. Also use when the user explicitly wants to submit a bug report, suggestion, or general feedback. Send only a brief, generic summary of the unsupported action or feedback, without personal data, credentials, document contents, submission data, or chat transcripts. Follow the host data-sharing permissions and confirmation requirements. After the call, explain the limitation and continue with any supported parts of the task. Only say feedback was recorded if the result confirms success. This records feedback; it does not perform the unsupported action, open a support ticket, or promise implementation.

send_for_signature

ChatGPT
Send a sign document to signers via email. A sign document has a fixed set of signer roles (signature slots). Each send dispatches one independent copy of the document to one person per role — a "set". The number of signer roles only controls how many people are on a single copy; it is NOT a limit on how many people can ever receive the document. You can call this tool as many times as needed to send additional independent copies to different people: a one-signer document can be sent to any number of individuals (one copy each), and a multi-signer document can be sent to different sets of people (one copy per set). To send a copy to a different person or set of people, first point the signer role(s) at them with the updateSigner tool (set each role's name and email), then call this tool — there is no separate "add signer" step, and having only one signer role does not prevent sending to more people. Supports signing order and auto-reminders. This action emails real people — confirm with the user before calling.

sign_home

ChatGPT
Open the Jotform Sign home.

sign_in

ChatGPT
Connect a Jotform account. Use it when the user wants to sign in, use their existing Jotform account or see the documents in it, or when a result says the session has no Jotform account. Signing in keeps the drafts made before it.

updateSigner

ChatGPT
Update an existing signer on a sign document with their name, email, and optional signing order. Use this to fill in signer details (e.g. after assignFieldsToSigners created the signer roles). Call this tool once per signer that needs updating.

update_sign_document_content

ChatGPT
Saves user-edited HTML content of an AI-created sign document and regenerates its PDF and fields.

update_signer

ChatGPT
Update an existing signer role on a sign document with a person's name, email, and optional signing order. Use this to fill in signer details (e.g. after assignFieldsToSigners created the signer roles), or to re-target a signer role to a different person before (re-)sending: update the role's name and email here, then call sendForSignature again to send a new independent copy to that person. A document keeps the same signer roles across sends, so repeating updateSigner + sendForSignature lets you send copies to any number of different people even when there is only one signer role. Get valid participant IDs from getSigners. Call this tool once per signer role that needs updating.

createSignDocument

Claude

create_sign_document

Claude

displaySignDocument

Claude

display_sign_document

Claude

editSignDocument

Claude

edit_sign_document

Claude

getSigners

Claude

getSigningStatus

Claude

get_signers

Claude

get_signing_status

Claude

listSignDocuments

Claude

listSubmissions

Claude

list_submissions

Claude

mcp_app_request

Claude

sendForSignature

Claude

send_for_signature

Claude

updateSigner

Claude

update_sign_document_content

Claude

update_signer

Claude

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/jotform-sign"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/jotform-sign)