Resources · Claude connector

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

Overview

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.

Vocabulary

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.
Connect

Plug Jotform Apps into Claude in three steps

  1. 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.

  2. 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.

  3. 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.

Tools

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 tools

Three 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.

When it helps
an app was requested a minute ago and you want to know if it is ready to share with your team.

Sourcejotform.com · October 1, 2026 ↗

get_teams

Finds the Jotform Enterprise teams you can access and inspects their membership, to choose the right workspace for an app.

When it helps
HR wants the new portal filed under the People team, not in a personal space.
Watch out
Jotform says team data needs an Enterprise account with team access.

Sourcejotform.com · October 1, 2026 ↗

What Claude changes (2)

2 tools

Two 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 rule

Builds 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.

What Claude asks for
no source describes a confirmation specific to this tool, so the general approval rule applies.
When it helps
a consultant needs a client portal for requests and shared resources.

Sourcejotform.com · October 1, 2026 ↗

edit_app

Approval: see the rule

Reworks an app that already exists, following your written instructions: its pages, its elements, its embedded forms, its appearance and its settings.

What Claude asks for
no confirmation is documented for this tool; the default rule in the approvals section covers it.
When it helps
adding attendee registration to an event app the week before the event.

Sourcejotform.com · October 1, 2026 ↗

Not documented (1)

1 tool

The 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.

Watch out
whatever it does, the general approval rule applies to it.
Approvals

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.

Plans

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.

Limits

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

Need help connecting Jotform Apps to Claude?

A person reads every message.

FAQ

Questions about the Claude Jotform Apps connector

01What can Claude do with the Jotform Apps connector?
Claude can create a Jotform app from a description, edit an existing one through written instructions, find apps by title or date, read an app's structure and build status, and list the Enterprise teams you can access. Those are five of the six tools on the directory sheet. The sixth, mcp_app_request, has no official description. Everything happens in the conversation, on the apps your own Jotform account can already reach, and only when you ask for it.
02Can Claude create or change apps in Jotform?
Yes. create_app builds a new app with pages, content elements, embedded forms and a theme, and edit_app changes an existing app's pages, elements, forms, appearance and settings. The other documented tools only search and inspect. The directory description also mentions users, payments and publishing, but no documented tool is tied to those steps, so treat them as unconfirmed until you see them work on your own account. Each change happens on your request, inside the conversation.
03Does Claude ask before changing a Jotform app?
By default, Claude asks for confirmation before each action it takes on an account for you. No source describes a confirmation specific to create_app or edit_app, so that default rule covers both. On Team and Enterprise workspaces, owners decide whether members can skip some confirmations, and they can restrict the connector for the whole organization, for example keeping search open while blocking creation and edits. The official read or write label of each tool only appears in a connected account's settings, never on a public page.
04Which Claude plans include the Jotform Apps connector?
No official source lists which plans include a given connector, and the 819 directory sheets don't show it either. Anthropic's general rule: all users can reach remote connectors on Claude, Cowork, Claude Desktop and mobile. In a Team or Enterprise organization, an Owner or Primary Owner switches the connector on before members sign in. The Jotform Apps sheet in the official directory is the only place showing the current state for your account.
05Can Claude see every app in our Jotform account?
No. Claude works with the rights of the person who connected and nothing beyond them. If your Jotform account can't open an app, Claude can't either. Shared workspaces add a layer on the Jotform side: according to Jotform's developer page, listing teams depends on a Jotform Enterprise account that has access to those teams, and without it the documented home for a new app is your personal space. On the Claude side, a workspace owner can also narrow what the connector is allowed to do.
06Why doesn't Claude publish or set up payments in my app?
Because no documented tool covers those steps. The directory description lists users, permissions, payments, workflows and publishing among the things you can do, but Jotform's developer page only describes creating, editing, searching, inspecting apps and listing teams. Changing app settings is part of editing, yet nothing says which settings. Check the tool list in your own Claude account after connecting before relying on those actions. Jotform's developer page is the only source on this connector: no Claude help article covers it.
07Claude or an automation tool for Jotform Apps?
They do different jobs, so it depends on what you need. Claude fits the building phase: describing an app, adjusting its pages, checking where it stands, all in a conversation. An automation tool fits what must happen without you, such as routing every new submission to a spreadsheet or a CRM. The connector never runs by itself, so anything recurring belongs on the automation side. Claude only touches an app when you ask for it in a conversation.