Can I use Gravity Forms as a CLI?

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

Can I expose Gravity Forms through MCP?

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

Where are Gravity Forms credentials stored?

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

Can I deny write access for Gravity Forms MCP tools?

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

productivity

Gravity Forms CLI for AI Agents

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

Gravity Forms CLI Setup

Gravity Forms can be configured headlessly with `kosmokrator integrations:configure gravity`.

Install, configure, and verify

# 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 gravity --set api_key="$GRAVITY_API_KEY" --enable --read allow --write ask --json
kosmokrator integrations:doctor gravity --json
kosmokrator integrations:status --json

Credentials

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

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

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call

kosmo integrations:call gravity.gravity_list_forms '{"limit":1,"offset":1}' --json

Provider shortcut

kosmo integrations:gravity gravity_list_forms '{"limit":1,"offset":1}' --json

Discovery

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

Discovery commands

kosmo integrations:docs gravity --json
kosmo integrations:docs gravity.gravity_list_forms --json
kosmo integrations:schema gravity.gravity_list_forms --json
kosmo integrations:search "Gravity Forms" --json
kosmo integrations:list --json

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CI Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status. Cron Jobs Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config. Shell Scripts Call integration functions from shell scripts with stable JSON input and output. Headless Automation Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers. Coding Agents Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

`gravity.gravity_list_forms`

List forms available in Gravity with optional pagination.

Read read

Parameters: limit, offset

Generic call

kosmo integrations:call gravity.gravity_list_forms '{"limit":1,"offset":1}' --json

Shortcut

kosmo integrations:gravity gravity_list_forms '{"limit":1,"offset":1}' --json

`gravity.gravity_get_form`

Get details for a specific Gravity form.

Read read

Parameters: form_id

Generic call

kosmo integrations:call gravity.gravity_get_form '{"form_id":"example_form_id"}' --json

Shortcut

kosmo integrations:gravity gravity_get_form '{"form_id":"example_form_id"}' --json

`gravity.gravity_submit_form`

Submit a Gravity form with field values.

Write write

Parameters: form_id, data

Generic call

kosmo integrations:call gravity.gravity_submit_form '{"form_id":"example_form_id","data":"example_data"}' --json

Shortcut

kosmo integrations:gravity gravity_submit_form '{"form_id":"example_form_id","data":"example_data"}' --json

`gravity.gravity_list_submissions`

List submissions for a specific Gravity form.

Read read

Parameters: form_id, limit, offset

Generic call

kosmo integrations:call gravity.gravity_list_submissions '{"form_id":"example_form_id","limit":1,"offset":1}' --json

Shortcut

kosmo integrations:gravity gravity_list_submissions '{"form_id":"example_form_id","limit":1,"offset":1}' --json

`gravity.gravity_list_entries`

List entries for a specific Gravity form.

Read read

Parameters: form_id, limit, offset

Generic call

kosmo integrations:call gravity.gravity_list_entries '{"form_id":"example_form_id","limit":1,"offset":1}' --json

Shortcut

kosmo integrations:gravity gravity_list_entries '{"form_id":"example_form_id","limit":1,"offset":1}' --json

`gravity.gravity_get_entry`

Get details for a specific Gravity entry.

Read read

Parameters: entry_id

Generic call

kosmo integrations:call gravity.gravity_get_entry '{"entry_id":"example_entry_id"}' --json

Shortcut

kosmo integrations:gravity gravity_get_entry '{"entry_id":"example_entry_id"}' --json

`gravity.gravity_get_current_user`

Get profile information for the authenticated Gravity user.

Read read

Parameters: none

Generic call

kosmo integrations:call gravity.gravity_get_current_user '{}' --json

Shortcut

kosmo integrations:gravity gravity_get_current_user '{}' --json

Function Schemas

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

gravity.gravity_list_forms 2 parameters

Schema command

kosmo integrations:schema gravity.gravity_list_forms --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of forms to return.
`offset`	integer	no	Pagination offset.

gravity.gravity_get_form 1 parameters

Schema command

kosmo integrations:schema gravity.gravity_get_form --json

Parameter	Type	Required	Description
`form_id`	string	yes	The form ID.

gravity.gravity_submit_form 2 parameters

Schema command

kosmo integrations:schema gravity.gravity_submit_form --json

Parameter	Type	Required	Description
`form_id`	string	yes	The form ID.
`data`	object	yes	Form field values keyed by field name or ID.

gravity.gravity_list_submissions 3 parameters

Schema command

kosmo integrations:schema gravity.gravity_list_submissions --json

Parameter	Type	Required	Description
`form_id`	string	yes	The form ID.
`limit`	integer	no	Maximum number of submissions to return.
`offset`	integer	no	Pagination offset.

gravity.gravity_list_entries 3 parameters

Schema command

kosmo integrations:schema gravity.gravity_list_entries --json

Parameter	Type	Required	Description
`form_id`	string	yes	The form ID.
`limit`	integer	no	Maximum number of entries to return.
`offset`	integer	no	Pagination offset.

gravity.gravity_get_entry 1 parameters

Schema command

kosmo integrations:schema gravity.gravity_get_entry --json

Parameter	Type	Required	Description
`entry_id`	string	yes	The entry ID.

gravity.gravity_get_current_user 0 parameters

Schema command

kosmo integrations:schema gravity.gravity_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.