Can I use Jotform as a CLI?

Yes. KosmoKrator exposes a Jotform CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Jotform through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Jotform tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Jotform credentials stored?

Jotform credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Jotform MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

forms

Jotform CLI for AI Agents

Use the Jotform CLI from KosmoKrator to call Jotform tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

7 functions 6 read 1 write API key auth

Submit Jotform feedback View package source

Jotform CLI Setup

Jotform can be configured headlessly with `kosmokrator integrations:configure jotform`.

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure jotform --set api_key="$JOTFORM_API_KEY" --enable --read allow --write ask --json
kosmokrator integrations:doctor jotform --json
kosmokrator integrations:status --json

Credentials

Authentication type: API key api_key. Configure credentials once, then use the same stored profile from scripts, coding CLIs, Lua code mode, and the MCP gateway.

Key	Env var	Type	Required	Label
`api_key`	`JOTFORM_API_KEY`	Secret `secret`	yes	API Key
`url`	`JOTFORM_URL`	URL `url`	no	API Base URL

Call Jotform Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

kosmo integrations:call jotform.jotform_list_forms '{
  "limit": 1,
  "offset": 1,
  "orderby": "example_orderby",
  "status": "example_status",
  "title": "example_title"
}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:jotform jotform_list_forms '{
  "limit": 1,
  "offset": 1,
  "orderby": "example_orderby",
  "status": "example_status",
  "title": "example_title"
}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

kosmo integrations:docs jotform --json
kosmo integrations:docs jotform.jotform_list_forms --json
kosmo integrations:schema jotform.jotform_list_forms --json
kosmo integrations:search "Jotform" --json
kosmo integrations:list --json

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Jotform.

`jotform.jotform_list_forms`

Read read

List all forms owned by the authenticated Jotform user. Returns form IDs, titles, creation dates, and status. Supports pagination and filtering.

Parameters: limit, offset, orderby, status, title

Generic CLI call

kosmo integrations:call jotform.jotform_list_forms '{"limit":1,"offset":1,"orderby":"example_orderby","status":"example_status","title":"example_title"}' --json

Provider shortcut

kosmo integrations:jotform jotform_list_forms '{"limit":1,"offset":1,"orderby":"example_orderby","status":"example_status","title":"example_title"}' --json

`jotform.jotform_get_form`

Read read

Get detailed information about a specific Jotform form, including its properties, status, URL, and creation date.

Parameters: form_id

Generic CLI call

kosmo integrations:call jotform.jotform_get_form '{"form_id":"example_form_id"}' --json

Provider shortcut

kosmo integrations:jotform jotform_get_form '{"form_id":"example_form_id"}' --json

`jotform.jotform_list_submissions`

Read read

List submissions for a specific Jotform form. Returns submission IDs, timestamps, and answers. Supports pagination, filtering by date, and ordering.

Parameters: form_id, limit, offset, orderby, created_at, status

Generic CLI call

kosmo integrations:call jotform.jotform_list_submissions '{"form_id":"example_form_id","limit":1,"offset":1,"orderby":"example_orderby","created_at":"example_created_at","status":"example_status"}' --json

Provider shortcut

kosmo integrations:jotform jotform_list_submissions '{"form_id":"example_form_id","limit":1,"offset":1,"orderby":"example_orderby","created_at":"example_created_at","status":"example_status"}' --json

`jotform.jotform_get_submission`

Read read

Get detailed information about a specific Jotform submission, including all form answers, metadata, and timestamps.

Parameters: submission_id

Generic CLI call

kosmo integrations:call jotform.jotform_get_submission '{"submission_id":"example_submission_id"}' --json

Provider shortcut

kosmo integrations:jotform jotform_get_submission '{"submission_id":"example_submission_id"}' --json

`jotform.jotform_create_form`

Write write

Create a new form in Jotform. Provide form properties such as title, questions (fields), and other settings. Returns the created form with its ID and URL.

Parameters: title, questions, properties

Generic CLI call

kosmo integrations:call jotform.jotform_create_form '{"title":"example_title","questions":"example_questions","properties":"example_properties"}' --json

Provider shortcut

kosmo integrations:jotform jotform_create_form '{"title":"example_title","questions":"example_questions","properties":"example_properties"}' --json

`jotform.jotform_list_questions`

Read read

List all questions (form fields) for a specific Jotform form. Returns field types, labels, names, and configuration options.

Parameters: form_id, offset

Generic CLI call

kosmo integrations:call jotform.jotform_list_questions '{"form_id":"example_form_id","offset":1}' --json

Provider shortcut

kosmo integrations:jotform jotform_list_questions '{"form_id":"example_form_id","offset":1}' --json

`jotform.jotform_get_current_user`

Read read

Get profile information for the currently authenticated Jotform user, including username, email, account type, and usage stats.

Parameters: none

Generic CLI call

kosmo integrations:call jotform.jotform_get_current_user '{}' --json

Provider shortcut

kosmo integrations:jotform jotform_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

`jotform.jotform_list_forms`

List all forms owned by the authenticated Jotform user. Returns form IDs, titles, creation dates, and status. Supports pagination and filtering.

Operation: Read read
Schema command: kosmo integrations:schema jotform.jotform_list_forms --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of forms to return (default: 20, max: 1000).
`offset`	integer	no	Offset for pagination — pass the number of forms to skip.
`orderby`	string	no	Field to order by: "created_at" (default), "title", "id", "updated_at".
`status`	string	no	Filter by status: "ENABLED" or "DISABLED".
`title`	string	no	Filter by form title (partial match).

`jotform.jotform_get_form`

Get detailed information about a specific Jotform form, including its properties, status, URL, and creation date.

Operation: Read read
Schema command: kosmo integrations:schema jotform.jotform_get_form --json

Parameter	Type	Required	Description
`form_id`	string	yes	The form ID (e.g., "231234567890123").

`jotform.jotform_list_submissions`

List submissions for a specific Jotform form. Returns submission IDs, timestamps, and answers. Supports pagination, filtering by date, and ordering.

Operation: Read read
Schema command: kosmo integrations:schema jotform.jotform_list_submissions --json

Parameter	Type	Required	Description
`form_id`	string	yes	The form ID to list submissions for (e.g., "231234567890123").
`limit`	integer	no	Maximum number of submissions to return (default: 20, max: 1000).
`offset`	integer	no	Offset for pagination — pass the number of submissions to skip.
`orderby`	string	no	Field to order by: "created_at" (default) or "id".
`created_at`	string	no	Filter by creation date (format: "YYYY-MM-DD HH:mm:ss" or date range).
`status`	string	no	Filter by submission status: "ACTIVE" or "DELETED".

`jotform.jotform_get_submission`

Get detailed information about a specific Jotform submission, including all form answers, metadata, and timestamps.

Operation: Read read
Schema command: kosmo integrations:schema jotform.jotform_get_submission --json

Parameter	Type	Required	Description
`submission_id`	string	yes	The submission ID (e.g., "512345678901234567").

`jotform.jotform_create_form`

Create a new form in Jotform. Provide form properties such as title, questions (fields), and other settings. Returns the created form with its ID and URL.

Operation: Write write
Schema command: kosmo integrations:schema jotform.jotform_create_form --json

Parameter	Type	Required	Description
`title`	string	yes	The title of the form.
`questions`	array	no	Array of question definitions. Each question should have "type" (e.g., "control_textbox", "control_email", "control_textarea", "control_dropdown", "control_radio", "control_checkbox"), "name" (field label), and "order" (position).
`properties`	object	no	Additional form properties (e.g., "redirect", "thankurl", "form_pagination", "height"). Pass as an object.

`jotform.jotform_list_questions`

List all questions (form fields) for a specific Jotform form. Returns field types, labels, names, and configuration options.

Operation: Read read
Schema command: kosmo integrations:schema jotform.jotform_list_questions --json

Parameter	Type	Required	Description
`form_id`	string	yes	The form ID (e.g., "231234567890123").
`offset`	integer	no	Offset for pagination.

`jotform.jotform_get_current_user`

Get profile information for the currently authenticated Jotform user, including username, email, account type, and usage stats.

Operation: Read read
Schema command: kosmo integrations:schema jotform.jotform_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.