- Home
- Resources
- Integrations
- Jotform Apps
Claude Jotform Apps connectorWhat Claude can do in your Jotform Apps account.
The Claude Jotform Apps connector shows 6 tools on its directory sheet. 3 read your apps and teams, 2 write by creating or editing an app, and 1 has no official description. This is the app builder, not the Jotform forms connector: below, what it does and where it stops.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can build your Jotform apps
Jotform Apps turns forms, pages and resources into a mobile-friendly app. With the connector, you describe the app to Claude in a sentence or two, and it creates the pages, the elements, the theme and the embedded forms, then lets you refine the result as the conversation goes on.
Start an app from a description. create_app builds a full app from what you explain: who it is for, which pages and content it needs, which forms go inside, and the look you want. On a compatible client, the result shows up as a preview in the conversation.
Rework an existing one. edit_app changes an existing app's pages, elements, embedded forms, appearance and settings from written instructions. The directory gives the flavor of the request: open an onboarding app and add a welcome page and a resource section for new hires.
Find the right app and check its state. search retrieves apps by title or creation date, and fetch reads one app's structure, its metadata and where its build currently stands.
Now the gaps. The sheet's marketing text talks about managing users, payments and publishing, yet none of the documented tools is described for those steps, so this page doesn't promise them. One tool, mcp_app_request, has no description at all. And nothing runs by itself: Claude only touches an app when you ask in a conversation. Sending each submission somewhere else automatically is automation work, a different job, and the Integrations hub covers it.
The vocabulary in one minute
Five words you'll meet as you plug Jotform Apps into Claude.
- Connector
- The link you set up once between Claude and an account you already use, so Claude can work in it while it answers.
- Tool
- A named action the connector makes available to Claude. It picks the ones it needs while answering, and each name appears on the directory sheet.
- Authorization
- The service's own sign-in screen, where you give Claude the access it will use. You grant it once, per person, and can withdraw it.
- Approval
- The confirmation Claude waits for before it finishes something that changes your account, shown in the chat when it counts.
- MCP
- The shared standard behind connectors: it lets an assistant such as Claude exchange with a service outside of it.
Plug Jotform Apps into Claude in three steps
- 01
Find the connector
In Claude's settings, open Customize, then Connectors, and look for Jotform Apps, not the plain Jotform connector. On a Team or Enterprise workspace, an Owner or Primary Owner enables it before members can sign in.
- 02
Sign in to Jotform
Click Connect on its row and log in to Jotform in the window Jotform opens itself. If the link stops working one day, use Disconnect, then connect again from the same row.
- 03
Read the authorization screen
Go through the screen before accepting. It is Jotform's, not Claude's, and it defines what the access covers. You can revoke that access later from your Jotform account as well.
The 6 tools, sorted by what they do
Jotform Apps gives Claude 6 tools: 3 that read your account, 2 that change something in it, and 1 no official source describes.
Three groups: apps and teams Claude can look at, apps it can build or rework, and one name no official source explains. Names stay as Claude shows them.
- 3 read
- 2 write
- 1 not documented
What Claude reads (3)
3 toolsThree tools that look at your apps and teams without changing them.
fetch
Inspects one app from its ID: how it is structured, its metadata, and the current status of its build. The ID it needs is the one search returns.
get_teams
Finds the Jotform Enterprise teams you can access and inspects their membership, to choose the right workspace for an app.
search
Looks up existing apps by title and creation date, and returns their IDs and links so they can be inspected or edited next. On a compatible client, matches appear in an interactive gallery.
What Claude changes (2)
2 toolsTwo tools that create or modify an app. No source describes a confirmation of their own, so the default approval rule covers them.
create_app
Approval: see the ruleBuilds a new mobile-friendly app from your description: several pages, content elements, embedded forms and a visual theme, in your personal space or a team space.
edit_app
Approval: see the ruleReworks an app that already exists, following your written instructions: its pages, its elements, its embedded forms, its appearance and its settings.
Not documented (1)
1 toolThe directory publishes this name and nothing more. No official text says what it does, and the name alone is not evidence.
mcp_app_request
This name shows up in the directory's tool list and nowhere else. Jotform's developer page does not describe it, and no Claude page does either, so nothing more is said about it here.
Before Claude builds or reworks an app
By default, Claude stops and asks for your confirmation before each action it takes on an account for you. You see that request in the chat, right before the change.
On Team and Enterprise, workspace owners decide whether members can let some actions through without a new prompt each time. They can also restrict what a connector may do for everyone, keeping search and inspection open while closing creation and editing. No one bypasses that from their own account. Claude works with the access of the person who connected and nothing more: an app you can't open in Jotform stays closed to it.
Jotform Apps and Claude plans
Out of 819 sheets in the official directory, none lists availability by plan. Nobody publishes that answer for a single connector: a real hole in the catalogue, not a gap in our reading.
Anthropic's general rule is public: all users can reach remote connectors on Claude, Cowork, Claude Desktop and mobile. In a Team or Enterprise organization, an Owner or Primary Owner has to switch the connector on first. For the current state on your account, look at the Jotform Apps sheet in the official directory.
What Jotform Apps leaves out
Connectors don't run as automations. Claude reaches for these tools only while it is answering you; nothing reacts on its own when someone fills in a form inside one of your apps.
Treat the tool list as an observed floor rather than a promise: an administrator can open actions missing from every public sheet. The directory badge isn't a security audit, and Anthropic says on every sheet that it doesn't choose the tools a publisher exposes or guarantee their behavior. Plug in what comes from a publisher you know. Jotform's developer page is the only documentation for this app builder; no Claude help article covers it.
Need help connecting Jotform Apps to Claude?
A person reads every message.