JotForm

What it is

A Python server that exposes the Jotform API as tools: forms and their questions, submissions, folders, reports, webhooks and account settings. Every public method of its JotformAPIClient becomes a tool, so the surface is close to the API itself rather than a curated subset.

What you get

• Forms: get_forms, get_form, create_form, clone_form, delete_form, and get_form_properties / set_form_properties for the settings behind them
• Questions: get_form_questions, create_form_question, edit_form_question, delete_form_question, plus the bulk create_form_questions
• Submissions: get_form_submissions lists them for one form, get_submission reads one, edit_submission and delete_submission change them, create_form_submission files a new one
• search_submissions_by_date searches across forms by start_date / end_date or by a named period such as last_7_days or current_accounting_month, with limit_per_form defaulting to 1000
• Folders and reports: get_folders, create_folder, add_form_to_folder, get_reports, create_report
• Webhooks: get_form_webhooks, create_form_webhook, delete_form_webhook
• Account: get_user, get_usage for monthly submission and upload counts, get_history for the activity log, get_plan for the plan details

Requirements

A Jotform API key, created in the API section of your account settings and passed as JOTFORM_API_KEY. The repository is jotform-mcp-server (version 0.1.0), run as python jotform_mcp_server.py after uv pip sync uv.lock or pip install -r requirements.txt, or from the provided Dockerfile. It speaks stdio or SSE — MCP_TRANSPORT picks which, and the SSE server listens on port 8067 by default.

Setup effort

Add the configuration to your client

Tools you get

50 tools named in the project's documentation.

Requires

• cmd on PATH
• JOTFORM_API_KEY in your environment

Where it runs

All 6 documented setups run the server on your machine.