JotForm MCP. Pull form data, submissions, and account reports via API.

Q: How do I list all my active forms using the JotForm MCP Server?

You run the listforms tool. This returns a list of every form ID and title in your account, which is the first step before fetching any data.

Q: What is the difference between listsubmissions and getformsubmissions?

listsubmissions gives you a general list of all entries across all forms. getformsubmissions drills down to get every single submission for one specific form ID.

Q: Can I check my JotForm account usage with the getusage tool?

Yes. Running getusage retrieves your current account usage limits and tells you if you're approaching capacity, helping prevent failed data jobs.

Q: How do I find out what data a form collects before I analyze it?

Run the getform tool. It returns the form's properties and the list of questions/fields, so you know exactly what data is available.

Q: How do I check the history of actions with the listhistory tool?

The listhistory tool provides an audit log of account activity. You can use this to review recent management actions and track who did what within your JotForm account.

Q: What is the difference between listforms and getform?

The listforms tool returns a summary of all your forms (titles, IDs, and counts). Use getform when you need the specific details, like the questions and fields, for one particular form ID.

Q: How can I find all submissions across different forms using listsubmissions?

The listsubmissions tool gathers all entries from every form into one view. This is ideal for monitoring general activity or gathering recent data across multiple, unrelated forms.

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Just plug in your AI agents and start using Vinkius.

JotForm MCP Server connects your AI client to the JotForm API. You can manage forms, track submissions, and audit account activity directly through natural language prompts.

Use the server to list forms, retrieve submissions for analysis, or check account usage limits. It's built for automating data collection and form management workflows.

What your AI agents can do

Get account

Retrieves detailed information about your JotForm account status or identity.

Get form

Returns the questions and properties of a specific form ID, showing exactly what data it collects.

Get form submissions

Retrieves all individual responses for a specific form, allowing deep analysis of its results.

+ 7 more capabilities included

Get Form Data

Retrieves the structure and questions of a specific JotForm, telling you exactly what data the form collects.

Fetch Submissions

Gathers all individual responses (submissions) for a specified form, allowing deep analysis of collected data.

List Forms and Folders

Provides an inventory of all available forms and the folders they are stored in, helping you navigate large accounts.

Check Account Status

Verifies your JotForm account details, including usage limits and historical activity logs, so you know your account health.

Monitor Global Activity

Lists all submissions across every form or provides a general view of account activity for quick monitoring.

Ask AI about this MCP

Ask ChatGPT

Ask Claude

Ask Perplexity

Supported MCP Clients

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

Free for Subscribers

Lists all submission records across every form in your account.

list019d75be

list webhooks

Lists the webhooks configured for a specific form, useful for debugging automation flows.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

Import from OpenAPI, Swagger, or YAML specs
Create Agent Skills with progressive disclosure
Deploy to edge with MCPFusion framework
Built in DLP, auth, and compliance on every call
Real time usage dashboard and cost metering
Publish to catalog or keep private

Start building

Make Your AI Do More

Start with JotForm, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.

Use this MCP plus 4,700+ others, all in one place
Add new capabilities to your AI anytime you want
Every connection is secured and compliant automatically
Track usage and costs across all your servers
Works with Claude, ChatGPT, Cursor, and more
New servers added to the catalog every week

What you can do with this MCP connector

Your AI client connects to the JotForm API through this server. You'll manage forms, track submissions, and audit your account right from your agent. get_account gives you the detailed status and identity of your JotForm account. get_usage checks your current account capacity and usage limits. list_history shows a timeline of every account action and usage event. list_folders lists the organizational folders you use to group forms. list_forms gives you a full list of every form in your account, showing the titles, IDs, and how many responses each one got. get_form returns the specific questions and properties for a form ID, telling you exactly what data that form collects. get_form_submissions fetches every single response for a specific form, letting you analyze the collected data deep down. list_submissions lists all submission records from every form in your account.

You can also list_reports to see all the pre-aggregated reports generated from your data. list_webhooks lists the webhooks set up for a form, which is handy if you're debugging automation. Finally, list_history gives you a chronological record of all account management actions and usage history.

How JotForm MCP Works

1 You ask your AI client to check for form submissions. It uses the list_forms tool to get a list of available forms and their IDs.
2 You then specify the exact form ID and ask for the results. The agent calls get_form_submissions with that ID.
3 The server returns the raw submission data, which your AI client then structures, summarizes, or sends elsewhere.

The bottom line is, you ask your agent for data, and the server delivers the structured API results directly to your workflow.

Who Is JotForm MCP For?

The ops engineer who's tired of clicking through dozens of form dashboards. The market analyst who needs to pull data from dozens of surveys into a single spreadsheet. Project managers who need to audit form usage across departments. If your job involves data coming in through multiple web forms, this is for you.

Operations Engineer

Uses the server to audit form usage (get_usage) and list account activity (list_history) to ensure data pipelines are running smoothly.

Market Analyst

Calls get_form_submissions for specific form IDs to pull raw response data, which they then load into a data warehouse for trend analysis.

Product Manager

Uses list_forms and list_folders to audit which forms exist, ensuring that all necessary data collection points are active and correctly organized.

What Changes When You Connect

Access Specific Form Data: Instead of navigating to a single form's dashboard, use get_form_submissions to pull all responses for a given form ID instantly. This speeds up analysis cycles and eliminates manual data export.
Map Out Your Data Inventory: Need to know which forms exist? Use list_forms or list_folders to get a full inventory of your JotForm account. This is better than manually checking folder names and is critical for initial data mapping.
Audit Account Health: Before running large data queries, check your limits. The get_usage tool tells you exactly if you're approaching your plan capacity, stopping failed jobs before they start.
Centralized Submission View: Don't want to filter by form? list_submissions gives you a master list of every entry across your entire account, perfect for high-level monitoring.
Trace Account Changes: Need to know who did what and when? list_history provides an audit log of all management actions, which is essential for compliance and debugging.
Check Automation Status: If a form isn't sending data where it should, use list_webhooks to see the configured automation triggers and debug the flow.

Real-World Use Cases

Analyzing a Campaign's Results

A marketing analyst needs to understand the results of a recent survey. They ask their agent to run list_forms first to identify the correct ID. Then, they call get_form_submissions with that ID. The agent pulls all the raw data, which the analyst can then summarize and send to the stakeholder.

Building a Master Data Feed

An ops engineer needs a single feed of all incoming leads, regardless of which form they used. They use list_submissions to get a master list of all recent entries. This feed bypasses the need to query every form's submission dashboard individually.

Compliance and Auditing

A compliance officer needs proof of who changed settings and when. They use list_history to pull the full audit log. This ensures full data lineage tracking, a manual task that takes hours otherwise.

Debugging Broken Integrations

A developer notices a form isn't triggering its webhook. Instead of guessing, they use list_webhooks on the form ID. This instantly shows the configured endpoints, letting them fix the automation flow quickly.

The Tradeoffs

Assuming Data is Simple

Trying to manually combine data from 15 different forms because you think they all track the same thing. This is a time sink and misses context.

→ Don't copy-paste. Use list_forms to get the IDs, then call get_form_submissions for each one. Feed all those structured outputs into your agent for a unified view.

Ignoring Account Limits

Running a massive query like list_reports when the account is near its usage cap, resulting in a failed job and lost time.

→ Always check get_usage first. This prevents failed jobs and lets you know if you need to adjust your query scope or wait for the next cycle.

Getting Lost in Structure

Only knowing the form name but not the underlying field structure. You don't know if the form even asked for the right data points.

→ First, run get_form to retrieve the form's properties and question list. This confirms the data structure before you pull any submissions.

When It Fits, When It Doesn't

Use this server if your job relies on automated data intake from web forms and requires programmatic access to the raw data. You need to pull submissions, list form structures, or audit account usage. You're dealing with many forms or needing a single source of truth for data history.

Don't use this if you just need to look at one form's data on the JotForm website. For that, logging into the site is faster. Also, if your goal is to build a complex, multi-step form that needs complex validation, you'll need the form builder itself, not just the data export tools.

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by JotForm. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

How we secure it →

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

get_account get_form get_form_submissions get_usage list_folders list_forms list_history list_reports list_submissions list_webhooks

Collecting data from web forms is usually a painful, multi-step process.

Today, collecting data means logging into JotForm, finding the specific form, clicking the 'Submissions' tab, and then exporting the data to a CSV. If you have twenty forms, you repeat that process twenty times, then you have to manually clean up the spreadsheet and merge the sheets.

With the JotForm MCP Server, you ask your agent to list all forms and their IDs. Then, you tell it to run `get_form_submissions` for all relevant IDs. The agent pulls all the structured data directly, giving you a clean, aggregated dataset ready for analysis.

JotForm MCP Server: Manage forms, submissions & reports

You no longer have to switch between the JotForm dashboard, a spreadsheet, and your analysis tool. The agent pulls the raw form data using `get_form` and then uses `list_reports` to find pre-aggregated views. All the data context stays within your AI workflow.

This means you move from data collection and manual cleanup to actual insights. You're analyzing data immediately, not days later after the data export process.

Common Questions About JotForm MCP

How do I list all my active forms using the JotForm MCP Server? +

You run the list_forms tool. This returns a list of every form ID and title in your account, which is the first step before fetching any data.

What is the difference between `list_submissions` and `get_form_submissions`? +

list_submissions gives you a general list of all entries across all forms. get_form_submissions drills down to get every single submission for one specific form ID.

Can I check my JotForm account usage with the `get_usage` tool? +

Yes. Running get_usage retrieves your current account usage limits and tells you if you're approaching capacity, helping prevent failed data jobs.

How do I find out what data a form collects before I analyze it? +

Run the get_form tool. It returns the form's properties and the list of questions/fields, so you know exactly what data is available.

Does the JotForm MCP Server handle form authentication? +

The server interacts with the JotForm API to manage data. Your AI client handles the authentication flow required to access the necessary tools.

How do I check the history of actions with the `list_history` tool? +

The list_history tool provides an audit log of account activity. You can use this to review recent management actions and track who did what within your JotForm account.

What is the difference between `list_forms` and `get_form`? +

The list_forms tool returns a summary of all your forms (titles, IDs, and counts). Use get_form when you need the specific details, like the questions and fields, for one particular form ID.

How can I find all submissions across different forms using `list_submissions`? +

The list_submissions tool gathers all entries from every form into one view. This is ideal for monitoring general activity or gathering recent data across multiple, unrelated forms.

How do I get JotForm API credentials? +

Can I see form questions? +

Yes, the get_form tool retrieves the full structure and details of a specific form, including its questions.

Does it support submission tracking? +

Yes, you can list all submissions or retrieve submissions for a specific form using the corresponding tools.

View all recipes →