Jotform MCP connector
The Jotform connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, 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.
- Connects over OAuth
- Free 14-day trial
- No credit card
Summarize this week's submissions to the customer feedback form
Working in Jotform with Elaichi
-
Search
-
Get submissions
-
Create form
How to connect Jotform to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
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. 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.
Jotform MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Jotform through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Jotform is logged.
-
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?”
What connecting Jotform gets you
6 screens from Elaichi, each doing one job for your Jotform account.
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, Cursor or Microsoft Copilot
The agent
Ask about your Jotform submissions in plain language.
Three starter prompts pull live answers from your forms and submissions, no export required.
Copy the endpoint
AI apps
One endpoint brings Jotform to every MCP client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, with no SDK and no shared API key.
Tool catalog
7 Jotform tools, ready with no code.
Search, create and edit forms, fetch submissions and analyze them, all cataloged automatically.
Toolboxes
Every team gets its own Jotform toolbox.
Marketing edits forms, Support reads submissions, each team scoped to the work it owns.
Shared connections
Share one Jotform connection, never a password.
Teammates work through the shared account while the credential stays with the person who connected it.
Audit log
Every Jotform call is logged with a name.
When, who, what happened, and which form or submission, in an append-only record.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
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 Jake Morgan
Approve Deny -
Post the digest
Jotform
Queued
Workflows
A schedule turns Jotform submissions into a digest.
New submissions are fetched, grouped, drafted into a summary, approved, then posted back to Jotform.
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%
Collections and dashboards
Jotform numbers arrive before anyone asks.
Four metrics, 14 days of submissions created, and a team breakdown, refreshed on a schedule.
Why connect Jotform's MCP server through Elaichi
Jotform builds and runs this MCP server. Elaichi sits in front of it, so Jotform's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Jotform's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Jotform's tools at the same Elaichi address as every other connected app. Nobody adds Jotform's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own Jotform sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Jotform's server. By default, a tool Jotform does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to Jotform
Jotform builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Jotform team.
For IT and engineering
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 | Free for one person; $15 per user per month on Gold. | 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.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting form creation, editing, or assignment. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot, 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, Microsoft Copilot, 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 of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot