Jotform MCP App works with forms and submissions and adds interactive, sandboxed interfaces in clients that support MCP Apps, such as Claude and ChatGPT. You can create and preview forms, work with submissions, and browse your forms without leaving the chat.

Along with standard MCP requirements, Jotform requires the following:

1. Jotform-capable client (e.g., Claude Desktop, ChatGPT, or IDEs with UI rendering support).

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.

Jotform Apps focuses on building and managing Jotform Apps (mobile-friendly portals) directly inside your AI assistant. It renders interactive, sandboxed UI so you can create, preview, and edit multi-page apps without leaving the chat.

Jotform Apps builds on the standard MCP requirements. To start using Jotform Apps you need the following:

1. A Jotform account with access to Jotform Apps.
2. A Jotform Apps capable client that can render interactive UI (e.g., Claude Desktop, ChatGPT, or an IDE with UI rendering support).
3. One‑time OAuth approval to connect Jotform Apps to your Jotform data.

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.

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.

Jotform Sign builds on the standard 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.

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.

Form Backend connects an existing website form to Jotform through your AI assistant. It creates a backing form in your Jotform account, collects responses, and configures owner notifications and visitor confirmation emails. Your website keeps its own form and design; no Jotform embed is required.

These tools return structured data without an embedded UI. Set up each website form once with create_form_backend, then reuse its form_id, submit_url, submission_key, and field_mapping. Calling the creation tool again creates another backing form.

After changing website fields, keep existing field names to retain their question IDs. Use response_emails_to_review from update_form_backend to update affected templates with update_response_email. If a visitor autoresponder was disabled because its email field changed, configure it again with configure_response_emails.

Form Backend builds on the standard MCP requirements. To get started you need:

1. A Jotform account and OAuth approval through your MCP connection.
2. An MCP-capable AI client and an existing website form whose submit handler you can edit.
3. Supported fields: text, email, number, textarea, select, radio, and checkbox. File uploads and payment fields are not supported.

The public website uses the returned submission key to write responses to that form only. It cannot read submissions or access your Jotform account. Keep Jotform API keys, OAuth tokens, and other secrets out of website code and form fields.

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.

Ask your assistant:

• “Connect my website's contact form to Jotform using its name, email, and message fields.” (create_form_backend)
• “Add a required topic dropdown to this website form and update its Jotform backend.” (update_form_backend)
• “Show the latest responses collected by my website's contact form.” (list_form_responses)
• “Notify me and send the visitor a confirmation after each submission.” (configure_response_emails)
• “Add a styled thank-you message to the visitor confirmation email.” (update_response_email)

After setup, have your assistant connect the website's submit handler to the returned submit_url. Send a JSON POST with Content-Type: application/json, the returned submission_key, and a data object whose keys exactly match the website field names in field_mapping. Send checkbox groups as arrays of strings or a single checkbox as a boolean.

Check that the response has responseCode: 200 and content.success: true before displaying a success message. Email setup and edits apply to future submissions; they do not send a message immediately.