Connect Jotform to Claude Code

Read Jotform forms and submissions, and manage submissions, form copies and webhooks. Add Toolspoke to Claude Code once and it can use 17 Jotform actions. Your Jotform credential stays in Toolspoke, and you choose which actions Claude Code may call.

Set it up in Claude Code

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Claude Code

    Run it in your project, then /mcp to sign in

    claude mcp add --transport http toolspoke https://toolspoke.com/mcp

    The sign-in opens in your browser, and Toolspoke asks you to approve it.

  2. Install Jotform and connect it

    Add Jotform to a project in your Toolspoke workspace.

    API key. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

    API key
    Jotform → My Account → API (jotform.com/myaccount/api) → Create New Key. Set its permission to Full Access for the write operations; Read Access covers every read.
  3. Choose what Claude Code may do

    All 17 actions start on. Switch off any of the 7 actions that change something in Jotform, and Claude Code gets a refusal if it tries.

What you can ask Claude Code for

A few of the Jotform actions that only read, so they are safe to try first.

  • Read the account the key belongs to, including its plan and limits
  • Read this month's usage against the plan's limits, such as submissions, uploads and payments
  • List your forms with their status, URL and submission counts
  • Read one form's basic information

What Claude Code can do in Jotform

10 actions read, 2 write and 5 delete or permanently change something.

Reads

  • Get user

    Read the account the key belongs to, including its plan and limits.

  • Get usage

    Read this month's usage against the plan's limits, such as submissions, uploads and payments.

  • List forms

    List your forms with their status, URL and submission counts. filter is an object such as {"status":"ENABLED"} or {"title:matches":"Survey"}. Proves the key reads real data, which is why an install tests itself with it.

  • Get form

    Read one form's basic information. The form id is the number in its URL (form.jotform.com/<formId>).

  • List questions

    List a form's questions, keyed by question id. Those ids are the keys of a submission's answers and of create_submission's submission object.

  • List form submissions

    List a form's submissions with every answer. filter is an object such as {"created_at:gt":"2026-10-01 00:00:00"}. Answers are what respondents typed, so the response is not written to the audit log.

  • List submissions

    List submissions across all your forms, newest first. Not written to the audit log.

  • Get submission

    Read one submission with every answer. Not written to the audit log.

  • List form reports

    List the reports built on a form, with their URLs.

  • List webhooks

    List the webhook URLs a form posts its submissions to, keyed by webhook id.

Writes

  • Edit submission

    Change answers on an existing submission. submission maps question ids to the new answers; questions left out keep their answers.

  • Clone form

    Make a copy of a form in your account. Returns the new form.

Deletes or permanently changes

  • Create submission

    Submit a response to a form, as if a respondent had filled it in. submission maps question ids to answers, e.g. {"3":"Ada","4":{"first":"Ada","last":"Lovelace"}}. Destructive because it runs the form's side effects: notification and autoresponder emails, integrations and webhooks.

  • Delete submission

    Delete one submission. A respondent's answers cannot be recovered afterwards.

  • Delete form

    Delete a form. Its link stops working for respondents at once.

  • Create webhook

    Send a form's submissions to a URL. Destructive because from then on every respondent's answers leave Jotform for that address, which may be outside your organization.

  • Delete webhook

    Delete a form's webhook. Whatever relied on it stops receiving submissions.

Jotform in Claude Code: questions

Does Claude Code see my Jotform credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Claude Code from changing things in Jotform?

Yes. Each of the 17 actions can be switched off for a project. Turn off the 7 that change something and Claude Code can only read.

Will 17 actions crowd Claude Code's context?

No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Jotform action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Can I add it once for every project?

Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.

What does it cost?

Tool calls are free on every plan, and a Jotform call does not run in a sandbox, so it bills nothing.

Try Jotform in Claude Code

Free to start, and tool calls cost nothing on any plan.