Can I use Unbounce as a CLI?

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

Can I expose Unbounce through MCP?

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

Where are Unbounce credentials stored?

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

Can I deny write access for Unbounce MCP tools?

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

marketing

Unbounce CLI for AI Agents

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

6 functions 6 read 0 write Bearer token auth

Submit Unbounce feedback View package source

Unbounce CLI Setup

Unbounce can be configured headlessly with `kosmokrator integrations:configure unbounce`.

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

Credentials

Authentication type: Bearer token bearer_token. 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
`access_token`	`UNBOUNCE_ACCESS_TOKEN`	Secret `secret`	yes	Access Token
`url`	`UNBOUNCE_URL`	URL `url`	no	API Base URL

Call Unbounce Headlessly

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

kosmo integrations:call unbounce.unbounce_list_pages '{
  "limit": 1,
  "offset": 1,
  "sort": "example_sort"
}' --json

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

kosmo integrations:unbounce unbounce_list_pages '{
  "limit": 1,
  "offset": 1,
  "sort": "example_sort"
}' --json

Agent Discovery Commands

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

kosmo integrations:docs unbounce --json
kosmo integrations:docs unbounce.unbounce_list_pages --json
kosmo integrations:schema unbounce.unbounce_list_pages --json
kosmo integrations:search "Unbounce" --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 Unbounce.

`unbounce.unbounce_list_pages`

Read read

List landing pages in Unbounce. Returns page IDs, names, URLs, and metadata. Use this to discover available pages before querying leads or page details.

Parameters: limit, offset, sort

Generic CLI call

kosmo integrations:call unbounce.unbounce_list_pages '{"limit":1,"offset":1,"sort":"example_sort"}' --json

Provider shortcut

kosmo integrations:unbounce unbounce_list_pages '{"limit":1,"offset":1,"sort":"example_sort"}' --json

`unbounce.unbounce_get_page`

Read read

Get details of a specific Unbounce landing page by its ID. Returns the page name, URL, variants, conversion rates, and other metadata.

Parameters: page_id

Generic CLI call

kosmo integrations:call unbounce.unbounce_get_page '{"page_id":"example_page_id"}' --json

Provider shortcut

kosmo integrations:unbounce unbounce_get_page '{"page_id":"example_page_id"}' --json

`unbounce.unbounce_list_leads`

Read read

List form submissions (leads) for a specific Unbounce landing page. Returns lead data including form field values, submission timestamps, and conversion details.

Parameters: page_id, limit, offset

Generic CLI call

kosmo integrations:call unbounce.unbounce_list_leads '{"page_id":"example_page_id","limit":1,"offset":1}' --json

Provider shortcut

kosmo integrations:unbounce unbounce_list_leads '{"page_id":"example_page_id","limit":1,"offset":1}' --json

`unbounce.unbounce_get_lead`

Read read

Get details of a specific Unbounce lead (form submission) by its ID. Returns all submitted form field values, metadata, and conversion information.

Parameters: lead_id

Generic CLI call

kosmo integrations:call unbounce.unbounce_get_lead '{"lead_id":"example_lead_id"}' --json

Provider shortcut

kosmo integrations:unbounce unbounce_get_lead '{"lead_id":"example_lead_id"}' --json

`unbounce.unbounce_list_sub_accounts`

Read read

List sub-accounts in Unbounce. Sub-accounts group pages and are useful for organizing landing pages by client, brand, or campaign.

Parameters: limit, offset

Generic CLI call

kosmo integrations:call unbounce.unbounce_list_sub_accounts '{"limit":1,"offset":1}' --json

Provider shortcut

kosmo integrations:unbounce unbounce_list_sub_accounts '{"limit":1,"offset":1}' --json

`unbounce.unbounce_get_current_user`

Read read

Get the currently authenticated Unbounce user profile. Returns account name, email, and other account details.

Parameters: none

Generic CLI call

kosmo integrations:call unbounce.unbounce_get_current_user '{}' --json

Provider shortcut

kosmo integrations:unbounce unbounce_get_current_user '{}' --json

Function Schemas

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

`unbounce.unbounce_list_pages`

List landing pages in Unbounce. Returns page IDs, names, URLs, and metadata. Use this to discover available pages before querying leads or page details.

Operation: Read read
Schema command: kosmo integrations:schema unbounce.unbounce_list_pages --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of pages to return (default: 50, max: 1000).
`offset`	integer	no	Offset for pagination (default: 0).
`sort`	string	no	Sort order. Prefix with "-" for descending (e.g., "created_at", "-created_at").

`unbounce.unbounce_get_page`

Get details of a specific Unbounce landing page by its ID. Returns the page name, URL, variants, conversion rates, and other metadata.

Operation: Read read
Schema command: kosmo integrations:schema unbounce.unbounce_get_page --json

Parameter	Type	Required	Description
`page_id`	string	yes	The Unbounce page ID (e.g., "a2834fde-1234-5678-abcd-1234567890ab").

`unbounce.unbounce_list_leads`

List form submissions (leads) for a specific Unbounce landing page. Returns lead data including form field values, submission timestamps, and conversion details.

Operation: Read read
Schema command: kosmo integrations:schema unbounce.unbounce_list_leads --json

Parameter	Type	Required	Description
`page_id`	string	yes	The Unbounce page ID to list leads for.
`limit`	integer	no	Maximum number of leads to return (default: 50, max: 1000).
`offset`	integer	no	Offset for pagination (default: 0).

`unbounce.unbounce_get_lead`

Get details of a specific Unbounce lead (form submission) by its ID. Returns all submitted form field values, metadata, and conversion information.

Operation: Read read
Schema command: kosmo integrations:schema unbounce.unbounce_get_lead --json

Parameter	Type	Required	Description
`lead_id`	string	yes	The Unbounce lead ID.

`unbounce.unbounce_list_sub_accounts`

List sub-accounts in Unbounce. Sub-accounts group pages and are useful for organizing landing pages by client, brand, or campaign.

Operation: Read read
Schema command: kosmo integrations:schema unbounce.unbounce_list_sub_accounts --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of sub-accounts to return (default: 50, max: 1000).
`offset`	integer	no	Offset for pagination (default: 0).

`unbounce.unbounce_get_current_user`

Get the currently authenticated Unbounce user profile. Returns account name, email, and other account details.

Operation: Read read
Schema command: kosmo integrations:schema unbounce.unbounce_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.