# Jotform MCP: MCP Apps › Jotform Sign The Jotform MCP server, built on the open Model Context Protocol, enables AI-powered, natural language access to forms and submissions. > Markdown version of https://www.jotform.com/developers/mcp/?tab=mcp-app. Other pages: [Overview](https://www.jotform.com/developers/mcp/?format=md), [MCP](https://www.jotform.com/developers/mcp/?tab=mcp&format=md), [MCP Apps](https://www.jotform.com/developers/mcp/?tab=mcp-app&format=md). # Jotform Sign ## Overview Jotform Sign lets you create and manage signable documents directly inside your AI assistant. Its interactive UI helps you generate and edit documents, review your document list and signing submissions, manage signers, send documents for signature, and track signing progress without leaving the chat. ## Available tools Jotform Sign MCP App provides 10 tools. The Access column shows whether a tool is read-only, writes data, or is destructive, meaning it can delete or overwrite existing data. Tools with an interactive UI open a panel in clients that support MCP Apps. Full tool reference with descriptions, behavior hints, and input and output schemas (JSON): https://api.jotform.com/mcp/documentation/servers/mcp-sign-v1 | Tool | Description | Access | Interactive UI | | --- | --- | --- | --- | | `create_sign_document` | Create a signable document that can be sent to one or more signers for e-signature. | Writes data | Yes | | `edit_sign_document` | Edit an existing sign document. | Destructive | Yes | | `get_signers` | 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. | Read-only | No | | `get_signing_links` | Get the signing links for a sent Jotform Sign document that is waiting for the current account's signature. | Read-only | No | | `get_signing_status` | Report the current status of a sign document including the overall document status and per-signer status (sent, viewed, signed, declined) with key timestamps. | Read-only | No | | `get_teams` | Retrieves team information for the user in Enterprise environments. | Read-only | No | | `list_submissions` | List signatures and signing submissions for sign documents. | Read-only | Yes | | `search` | Search and list the user's Jotform products of these types only: sign document. | Read-only | Yes | | `send_for_signature` | Send a sign document to signers via email. | Destructive | No | | `update_signer` | Update an existing signer role on a sign document with a person's name, email, and optional signing order. | Destructive | No | ## Requirements Jotform Sign builds on the [standard MCP requirements](https://www.jotform.com/developers/mcp/?tab=mcp#requirements). To start using Jotform Sign you need the following: 1. A Jotform account with access to Jotform Sign. 2. A Jotform Sign capable client that can render interactive UI. 3. One-time OAuth approval to connect Jotform Sign to your Jotform data. ## Connect | Setting | Value | | --- | --- | | Endpoint | `https://mcp.jotform.com/mcp-sign-v1` | | Transport | Streamable HTTP | | Authentication | OAuth 2.0 authorization code flow with PKCE (`S256`). Each user approves access once on the Jotform consent screen. Jotform API keys are not accepted. | | Authorization server | `https://oauth2.jotform.com`, advertised in the protected resource metadata at `https://mcp.jotform.com/.well-known/oauth-protected-resource/mcp-sign-v1` | | Scopes | `readOnly`, `full` | | Client registration | Dynamic client registration is supported, so no client ID or secret is needed. | | Interactive UI | Rendered in clients that support MCP Apps, such as Claude and ChatGPT. In other clients, tools return their results without the interface. | ### Add to your client #### ChatGPT **ChatGPT** Open the Jotform Sign app in the ChatGPT app directory and click Connect. Sign in to Jotform and approve access, then mention @Jotform Sign in a chat to use it. Open Jotform Sign in ChatGPT: **Codex** Run this command. Codex adds the server to `~/.codex/config.toml` and starts the sign-in; run `codex mcp login jotform-sign` if you need to sign in again. ```bash codex mcp add jotform-sign --url https://mcp.jotform.com/mcp-sign-v1 ``` #### Claude **Claude** Open Settings → Connectors, find Jotform Sign in the connector directory, and click Connect. Sign in to Jotform and approve access, then make sure the Jotform Sign connector is turned on in your chat. Open Jotform Sign in Claude: **Claude Code** Run this command, then run `/mcp` in Claude Code and select the server to sign in. ```bash claude mcp add --transport http jotform-sign https://mcp.jotform.com/mcp-sign-v1 ``` #### Cursor Add the server to `~/.cursor/mcp.json` for all projects or `.cursor/mcp.json` for one project. Then open the MCP section of Cursor Settings, connect the server, and approve access in your browser. ```json { "mcpServers": { "jotform-sign": { "url": "https://mcp.jotform.com/mcp-sign-v1" } } } ``` Add to Cursor: #### VS Code Add the server to `.vscode/mcp.json` in your workspace, or run `MCP: Add Server` from the Command Palette and enter the server URL. Start the server and approve access when VS Code asks you to sign in. ```json { "servers": { "jotform-sign": { "type": "http", "url": "https://mcp.jotform.com/mcp-sign-v1" } } } ``` Add to VS Code: #### Other clients Clients that support remote servers over Streamable HTTP with OAuth only need the server URL. Clients that can only run local (stdio) servers can connect through the `mcp-remote` bridge: ```json { "mcpServers": { "jotform-sign": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.jotform.com/mcp-sign-v1" ] } } } ``` ### Set up with your agent Paste this prompt into an agent that can edit its own MCP configuration, such as Cursor, Claude Code, or Codex. ```text Set up the Jotform Sign MCP App in this MCP client. - Server URL: https://mcp.jotform.com/mcp-sign-v1 - Transport: Streamable HTTP - Authentication: OAuth 2.0 with dynamic client registration. Do not ask me for an API key; I will approve access in the browser when the client asks me to sign in. - Documentation: https://www.jotform.com/developers/mcp/?tab=mcp-app&panel=jotform-sign&format=md Add the server to this client's MCP configuration under the name "jotform-sign", start the sign-in, then list the available tools to confirm the connection. ``` ## OAuth connections When you add the Jotform MCP server to a client, the client opens an OAuth consent screen that lets you authorize the connection to your Jotform data. OAuth runs through a **Jotform App** and is required for every user the first time they connect. Only workspace admins can install the Jotform MCP app. ### View authorized MCP clients 1. Sign in to the Jotform Dashboard. 2. Go to **My Account** → **Connected Apps**. 3. Select **Jotform MCP**. 4. In the right panel, choose **Clients** to see all OAuth‑connected MCP clients. ### Revoke OAuth access for a specific client 1. In the Clients list, find the client you want to remove. 2. Click the overflow menu (⋮) next to its entry. 3. Select Revoke. The client loses access immediately. Bearer‑token access is not supported; OAuth 2.0 is required for all connections.