Can I use GetResponse as a CLI?

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

Can I expose GetResponse through MCP?

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

Where are GetResponse credentials stored?

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

Can I deny write access for GetResponse MCP tools?

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

productivity

GetResponse CLI for AI Agents

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

GetResponse CLI Setup

GetResponse can be configured headlessly with `kosmokrator integrations:configure getresponse`.

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 getresponse --set api_key="$GETRESPONSE_API_KEY" --enable --read allow --write ask --json
kosmokrator integrations:doctor getresponse --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`	`GETRESPONSE_API_KEY`	Secret `secret`	yes	API Key
`url`	`GETRESPONSE_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 getresponse.getresponse_list_contacts '{"page":1,"perPage":1}' --json

Provider shortcut

kosmo integrations:getresponse getresponse_list_contacts '{"page":1,"perPage":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 getresponse --json
kosmo integrations:docs getresponse.getresponse_list_contacts --json
kosmo integrations:schema getresponse.getresponse_list_contacts --json
kosmo integrations:search "GetResponse" --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.

`getresponse.getresponse_list_contacts`

List contacts in your GetResponse account. Returns paginated results with contact details including email, name, and campaign.

Read read

Parameters: page, perPage

Generic call

kosmo integrations:call getresponse.getresponse_list_contacts '{"page":1,"perPage":1}' --json

Shortcut

kosmo integrations:getresponse getresponse_list_contacts '{"page":1,"perPage":1}' --json

`getresponse.getresponse_get_contact`

Get details of a specific contact in GetResponse by its unique identifier.

Read read

Parameters: id

Generic call

kosmo integrations:call getresponse.getresponse_get_contact '{"id":"example_id"}' --json

Shortcut

kosmo integrations:getresponse getresponse_get_contact '{"id":"example_id"}' --json

`getresponse.getresponse_create_contact`

Create a new contact in GetResponse. Requires an email address. Optionally set the contact name and assign to a campaign.

Write write

Parameters: email, name, campaign

Generic call

kosmo integrations:call getresponse.getresponse_create_contact '{"email":"example_email","name":"example_name","campaign":"example_campaign"}' --json

Shortcut

kosmo integrations:getresponse getresponse_create_contact '{"email":"example_email","name":"example_name","campaign":"example_campaign"}' --json

`getresponse.getresponse_update_contact`

Update an existing contact's details in GetResponse. Provide the contact ID and the fields to update.

Write write

Parameters: id, name

Generic call

kosmo integrations:call getresponse.getresponse_update_contact '{"id":"example_id","name":"example_name"}' --json

Shortcut

kosmo integrations:getresponse getresponse_update_contact '{"id":"example_id","name":"example_name"}' --json

`getresponse.getresponse_delete_contact`

Delete a contact from GetResponse. This action is permanent and cannot be undone.

Write write

Parameters: id

Generic call

kosmo integrations:call getresponse.getresponse_delete_contact '{"id":"example_id"}' --json

Shortcut

kosmo integrations:getresponse getresponse_delete_contact '{"id":"example_id"}' --json

`getresponse.getresponse_list_campaigns`

List all campaigns in your GetResponse account. Returns campaign IDs and names that can be used when creating contacts.

Read read

Parameters: none

Generic call

kosmo integrations:call getresponse.getresponse_list_campaigns '{}' --json

Shortcut

kosmo integrations:getresponse getresponse_list_campaigns '{}' --json

`getresponse.getresponse_get_campaign`

Get details of a specific campaign in GetResponse by its unique identifier.

Read read

Parameters: id

Generic call

kosmo integrations:call getresponse.getresponse_get_campaign '{"id":"example_id"}' --json

Shortcut

kosmo integrations:getresponse getresponse_get_campaign '{"id":"example_id"}' --json

`getresponse.getresponse_create_campaign`

Create a new email campaign in GetResponse. Campaigns are used to organize and send emails to contact lists.

Write write

Parameters: name

Generic call

kosmo integrations:call getresponse.getresponse_create_campaign '{"name":"example_name"}' --json

Shortcut

kosmo integrations:getresponse getresponse_create_campaign '{"name":"example_name"}' --json

`getresponse.getresponse_list_newsletters`

List newsletters in your GetResponse account. Returns newsletter details including subject, status, and send dates.

Read read

Parameters: none

Generic call

kosmo integrations:call getresponse.getresponse_list_newsletters '{}' --json

Shortcut

kosmo integrations:getresponse getresponse_list_newsletters '{}' --json

`getresponse.getresponse_get_current_user`

Get the authenticated user's account information from GetResponse, including email, name, and account details.

Read read

Parameters: none

Generic call

kosmo integrations:call getresponse.getresponse_get_current_user '{}' --json

Shortcut

kosmo integrations:getresponse getresponse_get_current_user '{}' --json

Function Schemas

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

getresponse.getresponse_list_contacts 2 parameters

Schema command

kosmo integrations:schema getresponse.getresponse_list_contacts --json

Parameter	Type	Required	Description
`page`	integer	no	Page number (1-based). Default: 1.
`perPage`	integer	no	Number of contacts per page (max 1000). Default: 50.

getresponse.getresponse_get_contact 1 parameters

Schema command

kosmo integrations:schema getresponse.getresponse_get_contact --json

Parameter	Type	Required	Description
`id`	string	yes	The unique contact identifier.

getresponse.getresponse_create_contact 3 parameters

Schema command

kosmo integrations:schema getresponse.getresponse_create_contact --json

Parameter	Type	Required	Description
`email`	string	yes	The contact's email address.
`name`	string	no	The contact's full name.
`campaign`	string	no	Campaign ID to add the contact to.

getresponse.getresponse_update_contact 2 parameters

Schema command

kosmo integrations:schema getresponse.getresponse_update_contact --json

Parameter	Type	Required	Description
`id`	string	yes	The unique contact identifier.
`name`	string	no	The new name for the contact.

getresponse.getresponse_delete_contact 1 parameters

Schema command

kosmo integrations:schema getresponse.getresponse_delete_contact --json

Parameter	Type	Required	Description
`id`	string	yes	The unique contact identifier to delete.

getresponse.getresponse_list_campaigns 0 parameters

Schema command

kosmo integrations:schema getresponse.getresponse_list_campaigns --json

Parameter	Type	Required	Description
No parameters.

getresponse.getresponse_get_campaign 1 parameters

Schema command

kosmo integrations:schema getresponse.getresponse_get_campaign --json

Parameter	Type	Required	Description
`id`	string	yes	The unique campaign identifier.

getresponse.getresponse_create_campaign 1 parameters

Schema command

kosmo integrations:schema getresponse.getresponse_create_campaign --json

Parameter	Type	Required	Description
`name`	string	yes	The name for the new campaign.

getresponse.getresponse_list_newsletters 0 parameters

Schema command

kosmo integrations:schema getresponse.getresponse_list_newsletters --json

Parameter	Type	Required	Description
No parameters.

getresponse.getresponse_get_current_user 0 parameters

Schema command

kosmo integrations:schema getresponse.getresponse_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.