Jotform MCP connector
The Jotform connector lets Claude, ChatGPT, Cursor, and the Elaichi Agent find your Jotform forms, pull in submissions, build and edit forms, and summarize responses, with every person working inside their own Jotform access.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
7 tools
How to connect
How to connect Jotform to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Jotform once
-
Open Connections, choose Add connection, and pick Jotform.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Jotform. Jotform's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Jotform MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Jotform MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Jotform MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Jotform to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Jotform through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Marketing
Summarize a campaign survey before the standup
Ask for the main themes in this week's responses to the event feedback form and get a short summary with counts, no spreadsheet export needed.
-
HR
Build a new hire questionnaire in minutes
Describe the questions you want and get a draft form in Jotform that you can tidy up before sending it to the next intake.
-
Support
Find the complaint form submissions from today
Pull the day's submissions to the issue report form and sort them by product so the desk knows where to start.
-
Operations
Assign the facilities request form to a manager
Hand the maintenance request form to the site lead so submissions route to them, without anyone passing a Jotform password around.
-
Events
Adjust registration questions after the venue changes
Edit the dietary and session choice questions on the live registration form and check what has already come in.
-
Research
Analyze a customer survey by segment
Ask how satisfaction scores differ between plan tiers across a survey's submissions and get the breakdown in plain language.
Try asking
- “Summarize this week's submissions to the customer feedback form”
- “Create a form for the Q3 offsite registration with meal choices”
- “Which submissions to the intake form mention pricing?”
Compare
Elaichi vs Zapier MCP vs Composio for Jotform
All three can connect Jotform to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Jotform tools | Allow or restrict single Jotform tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Jotform call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Jotform tools for your AI agents
7 tools are ready to call through Elaichi's MCP endpoint the moment you connect Jotform, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Jotform builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Jotform gets you
6 screens from the product, each doing one job for your Jotform account.
The agent
Ask about your Jotform submissions in plain language.
Three starter prompts pull live answers from your forms and submissions, no export required.
- forms
- submissions
- assignments
- questions
Ask Elaichi to work across your apps.
Summarize this week's submissions to the customer feedback form
Create a form for the Q3 offsite registration with meal choices
Which submissions to the intake form mention pricing?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings Jotform to every MCP client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
7 Jotform tools, ready with no code.
Search, create and edit forms, fetch submissions and analyze them, all cataloged automatically.
- Search
- Create form
- Edit form
- Fetch
ElaichiToolsToolboxes
Every team gets its own Jotform toolbox.
Marketing edits forms, Support reads submissions, each team scoped to the work it owns.
- Marketing
- HR
- Support
- Operations
ElaichiToolboxesShared connections
Share one Jotform connection, never a password.
Teammates work through the shared account while the credential stays with the person who connected it.
- Marketing
- People Ops
- Support
- Events
ElaichiConnectionsAudit log
Every Jotform call is logged with a name.
When, who, what happened, and which form or submission, in an append-only record.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule turns Jotform submissions into a digest.
New submissions are fetched, grouped, drafted into a summary, approved, then posted back to Jotform.
Jotform digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch forms
Jotform
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Jotform
Queued
Collections and dashboards
Jotform numbers arrive before anyone asks.
Four metrics, 14 days of submissions created, and a team breakdown, refreshed on a schedule.
Jotform health
Refreshed 4 minutes ago · every 15 minutes · from the forms collection
Forms
1,284 ↓ 12%
Submissions
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Forms created
Last 14 days
By team
Share of activity
Marketing 34%
People Ops 27%
Support 21%
Events 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Jotform to Claude?
Connect Jotform in Elaichi first: you are sent to Jotform's own sign-in page, you approve access, and you are done, with no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and your Jotform forms and submissions are available in the conversation.
Does Jotform work with ChatGPT and Cursor as well as Claude?
Yes. Jotform is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor, any other MCP client, or used by the Elaichi Agent. There is nothing to set up separately for each client.
What can an AI agent actually do with my Jotform data?
It can find a Jotform form by name, read its questions, pull in its submissions, and summarize or compare the responses. It can also create a new form from a description, edit the questions on an existing one, and assign a form to a colleague. Short, concrete asks such as "summarize this week's feedback form" work better than long sentences.
Does connecting Jotform give the AI access to every form in my account?
The AI sees only what the person who signed in to Jotform can see: their own forms, shared forms, and the submissions on them. Elaichi can narrow that further, for example to reading submissions only, but it can never grant anything the person's Jotform account does not already allow.
Can I stop an agent from deleting or changing things in Jotform?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Jotform submissions while blocking form creation, editing, or assignment. A restricted action is never advertised to Claude, ChatGPT, or Cursor at all, so no prompt, however worded, can reach it.
What happens to a Jotform connection when someone leaves?
Offboarding the person in Elaichi ends their access to Jotform through every AI client at once. If they were on a shared Jotform connection, it keeps working for everyone else on the team. Disconnecting Jotform once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client together.
Does the Jotform MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Jotform is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Jotform?
Yes. Both let Claude, ChatGPT or Cursor use Jotform. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Jotform call.
How is Elaichi different from Composio for Jotform?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Jotform: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Jotform in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.