Jotform MCP

Live

API KEY

FORMS

Every form, submission, and workflow your team builds lives in Jotform. Jotform MCP gives your agent authenticated access to form data scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the Jotform MCP account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: User permissions enforced. 90-day audit trail.
Jotform MCP
agent · Acme Q3
Run
How many submissions did our event registration form get this week and which sessions are most popular?
S
jotform_submissions_list
76ms
Data collection agent
284 registrations this week. Most popular sessions: AI & Automation Workshop (94 signups), Enterprise Security Panel (71), Product Roadmap Q&A (68), Customer Stories (51).
Sources: event registration form, this week
jotformmcpmcp
284 submissions
18:29
Message Claude...

Tools your data collection agent reaches for on Jotform MCP, scoped per user.

CALL ANY TOOL
List forms and questions, pull submissions, retrieve individual responses, and analyze form data.
jotform_forms_list
List forms
List all forms in the Jotform account with status filter.
Parameters
Name
Type
Required
Description
status
string
Optional
Status: ENABLED, DISABLED, DELETED
limit
integer
Optional
Max forms
offset
integer
Optional
Pagination offset
jotform_form_get
Get form
jotform_submissions_list
List submissions
jotform_submission_get
Get submission
jotform_questions_list
List questions
Build your Agent
Drop the toolkit in, point it at the user, and your data collection agent can use Jotform MCP from the first run.
import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["jotformmcp"], toolNames: ["jotform_forms_list", "jotform_form_get", "jotform_submissions_list"] },
pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
name: t.tool.definition.name,
description: t.tool.definition.description,
schema: z.object({}).passthrough(),
func: async (args) => {
const { data } = await sk.tools.executeTool({
toolName: t.tool.definition.name,
identifier: "user_123",
params: args,
});
return JSON.stringify(data);
},
}));

const agent = createReactAgent({ llm, tools: lcTools });
import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["jotformmcp"], toolNames: ["jotform_forms_list", "jotform_form_get", "jotform_submissions_list"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
type: "function",
function: {
name: t.tool.definition.name,
description: t.tool.definition.description,
parameters: t.tool.definition.input_schema,
},
}));

const resp = await openai.responses.create({
model: "gpt-4o", input: prompt, tools: llmTools,
});
import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["jotformmcp"], toolNames: ["jotform_forms_list", "jotform_form_get", "jotform_submissions_list"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
name: t.tool.definition.name,
description: t.tool.definition.description,
input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
model: "claude-sonnet-4-6", max_tokens: 1024,
tools: llmTools,
messages: [{ role: "user", content: prompt }],
});
import { Agent } from "@google/adk/agents";
import {
MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
connectionParams: new StreamableHTTPConnectionParams({
url: "https://mcp.scalekit.com/jotformmcp",
headers: { Authorization: `Bearer ${userScopedToken}` },
}),
});

const agent = new Agent({
name: "agent", model: "gemini-2.0-flash",
tools: await toolset.getTools(),
});
Try these prompts
Paste any prompt into your agent to start using Jotform MCP.
Search & responses
Copy the prompt
Copied
List all submissions for [form name] this week.
Copy the prompt
Copied
Get the response to question [name] from [submission].
Copy the prompt
Copied
How many submissions came in today?
Copy the prompt
Copied
Find submissions where [field] equals [value].
Analysis & reporting
Copy the prompt
Copied
Top answers to [question] in [form].
Copy the prompt
Copied
Submission count by day for [form] this month.
Copy the prompt
Copied
List all submissions with [field] blank.
Copy the prompt
Copied
Find registrations from [company domain].
Forms & setup
Copy the prompt
Copied
List all active forms.
Copy the prompt
Copied
Get the questions in [form name].
Copy the prompt
Copied
Find forms with no submissions this month.
Copy the prompt
Copied
List disabled forms.
SEE HOW AUTH WORKS
Users authorize Jotform MCP once. Their credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Jotform MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Jotform MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Jotform MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Jotform MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
Same per-user auth pattern across other data collection agents and MCP connectors. Working code, live demos, fork what fits.
SUPPORT
Freshdesk CSAT follow-up agent
Google ADK agent that watches low CSAT scores in Freshdesk and drafts personalised follow-ups for support leads.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.
// shared token
 audit → bot_service_account
 user_filter → broken

 // scalekit
 audit → user_abc
 scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Jotform MCP today. Others tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions

Does the agent access Jotform MCP as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Jotform MCP api key stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Jotform MCP?
Yes. Pass a tool name filter to listScopedTools so the data collection agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Jotform MCP.

What happens when a user revokes Jotform MCP access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent read submissions from forms the user doesn't own?
Only forms and submissions the authorizing user's API key permits. Keys are scoped to the Jotform account that generated them. Cross-account responses are inaccessible unless explicit sharing is configured.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""jotformmcp"": {
""url"": ""https://mcp.scalekit.com/jotformmcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.jotformmcp]
url = ""https://mcp.scalekit.com/jotformmcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""jotformmcp"": {
""url"": ""https://mcp.scalekit.com/jotformmcp"",
""type"": ""http""
}
}
}