jotform-forms

jotform-forms is a skill for Claude Code from jotform/mcp-server. It costs 82 tokens per session (697 once invoked), scanned A, original, MIT.

A tool for creating, finding, editing, and reviewing Jotform surveys and other forms, including registration, RSVP, and feedback forms.

In plain words
What is it for?
Use it to build or edit forms, preview them, submit data, list responses, or summarize what people answered.
Why use it?
It centralizes form changes and response review instead of making you manage forms and submissions separately.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the form-creator plugin — 1 skill, 1 MCP server shipped together

Good fit Use it to build or edit forms, preview them, submit data, list responses, or summarize what people answered.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jotform/mcp-server/jotform-forms
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add jotform/mcp-server --skill jotform-forms
Clone the repo
git clone --depth 1 https://github.com/jotform/mcp-server

Made for: Claude Code.

Or install form-creator, the plugin that ships this one along with the rest of its 1 skill, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for jotform-forms

README.md
[![agentmods](https://agentmods.dev/badge/skills/jotform/mcp-server/jotform-forms/github.svg)](https://agentmods.dev/skills/jotform/mcp-server/jotform-forms)
Your own site
<a href="https://agentmods.dev/skills/jotform/mcp-server/jotform-forms"><img src="https://agentmods.dev/badge/skills/jotform/mcp-server/jotform-forms/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for jotform-forms

Your own site · 80×15
<a href="https://agentmods.dev/skills/jotform/mcp-server/jotform-forms"><img src="https://agentmods.dev/badge/skills/jotform/mcp-server/jotform-forms.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 697 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00082 $0.00697
Opus 5.5 $0.00033 $0.00279
Sonnet 5.5 $0.00016 $0.00139
Haiku 4.5 $0.00008 $0.00070

Measured 2d ago against content hash ea21c02fae56, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

jotform-forms scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

integrations/claude/form-creator/skills/jotform-forms/SKILL.md · 33 lines

How it starts

The opening of the file, as written. The whole thing — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Jotform forms

Use tools from the jotform connector. When another connector exposes the same short tool name, choose the tool that belongs to jotform.

Do the task

  1. Treat the connected server's current tool definitions as the contract. If the connector is unavailable, name the connection the user needs. Never ask for a password or token in chat.
  2. For an existing form, use the form ID the user supplied or this connector's search. Ask which form they mean only when more than one match is plausible. Do not create a new form to satisfy an edit.
  3. Use create_form for a new form, edit_form for changes, and display_form for a preview. Use fetch, list_submissions, or analyze_submissions for retrieval and analysis. Call create_submission only when the user asked to submit data and the required values are known.
  4. Put the user's requirements in description. For create_form, use workspace_type: "personal" and team_id: "" unless the user asks for a team. Resolve a named team with this connector's get_teams, then pass its numeric ID and workspace_type: "team". Follow the live schema for every other tool.
  5. Pass a file only when the live schema has an input for it. Do not invent file IDs or download URLs. If the file cannot be supplied, say so and ask for the form content another way.

A create or edit that is still running

Do not call create_form or edit_form again to check progress. If the response says the work is still running (for example url: "in_progress"), keep the returned form ID, including related_asset.asset_id when it is present, and call this connector's fetch.

  • If metadata.build_status is processing, wait for metadata.poll_after_seconds when that value is present, then fetch the same ID. If no retry timing is given, report that the operation is pending.
  • If the status is completed, summarize the verified result.
  • If it is awaiting_confirmation, show the question and choices and wait for the user's answer before another edit.
  • If it is failed, stop and explain the reported failure.
  • If the response has no status and no ID, say the outcome is unknown. Do not start another creation.

Read the full file on GitHub · 33 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 33 lines · 82 tokens per session scan A ea21c02fae56

Subscribe to this mod's changes

jotform-forms is a skill published in the GitHub repository jotform/mcp-server (29 stars, last pushed 3d ago), licensed MIT. It adds 82 tokens to every session and 697 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-23.