Connect Jotform to Claude Code

Let Claude build forms and triage submissions in Jotform. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Jotform to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Jotform, you add a Jotform MCP server: a small hosted service that exposes Jotform's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Jotform account. No API keys pasted into config files.

claude mcp add --transport http jotform https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Jotform once connected?

Full read-write Jotform access lets Claude build a form from a description, add or reorder fields, edit confirmation settings, tag and update submissions, and route responses where they need to go. The form changes and triage that used to mean clicking through the builder happen in the conversation, once you approve.

Create a new form from a plain-language description of the fields you need
Add, reorder, or edit fields and validation on an existing form
Update a submission's status or fields as you process responses
Search submissions matching a query and propose batched follow-ups
Adjust confirmation messages and notification settings on a form
Clone an existing form as a starting point for a new one

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Jotform access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Jotform API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Jotform changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Jotform connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Jotform connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Jotform account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Jotform's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Jotform?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Jotform account it signs in with. Revoking access is one click in Jotform.

More on the Jotform connector

Jotform connector for claude.ai Typeform + Claude Code Google Forms + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us