Can I use Qualifying as a CLI?

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

Can I expose Qualifying through MCP?

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

Where are Qualifying credentials stored?

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

Can I deny write access for Qualifying MCP tools?

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

productivity

Qualifying CLI for AI Agents

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

Qualifying CLI Setup

Qualifying can be configured headlessly with `kosmokrator integrations:configure qualifying`.

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

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

Key	Env var	Type	Required	Label
`access_token`	`QUALIFYING_ACCESS_TOKEN`	Secret `secret`	yes	Access Token
`url`	`QUALIFYING_URL`	URL `url`	no	API URL

Command Patterns

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

Generic CLI call

kosmo integrations:call qualifying.qualifying_list_accounts '{"limit":1,"page":1}' --json

Provider shortcut

kosmo integrations:qualifying qualifying_list_accounts '{"limit":1,"page":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 qualifying --json
kosmo integrations:docs qualifying.qualifying_list_accounts --json
kosmo integrations:schema qualifying.qualifying_list_accounts --json
kosmo integrations:search "Qualifying" --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.

`qualifying.qualifying_list_accounts`

List sales accounts from Qualifying. Returns a paginated list of accounts with their details. Use limit and page parameters to navigate through results.

Read read

Parameters: limit, page

Generic call

kosmo integrations:call qualifying.qualifying_list_accounts '{"limit":1,"page":1}' --json

Shortcut

kosmo integrations:qualifying qualifying_list_accounts '{"limit":1,"page":1}' --json

`qualifying.qualifying_get_account`

Get detailed information about a specific sales account in Qualifying. Returns the account's full profile including name, industry, website, and associated metadata.

Read read

Parameters: id

Generic call

kosmo integrations:call qualifying.qualifying_get_account '{"id":"example_id"}' --json

Shortcut

kosmo integrations:qualifying qualifying_get_account '{"id":"example_id"}' --json

`qualifying.qualifying_list_contacts`

List contacts from Qualifying. Returns a paginated list of contacts. Optionally filter by account to see contacts belonging to a specific account.

Read read

Parameters: limit, page, account_id

Generic call

kosmo integrations:call qualifying.qualifying_list_contacts '{"limit":1,"page":1,"account_id":"example_account_id"}' --json

Shortcut

kosmo integrations:qualifying qualifying_list_contacts '{"limit":1,"page":1,"account_id":"example_account_id"}' --json

`qualifying.qualifying_get_contact`

Get detailed information about a specific contact in Qualifying. Returns the contact's full profile including name, email, phone, associated account, and other metadata.

Read read

Parameters: id

Generic call

kosmo integrations:call qualifying.qualifying_get_contact '{"id":"example_id"}' --json

Shortcut

kosmo integrations:qualifying qualifying_get_contact '{"id":"example_id"}' --json

`qualifying.qualifying_list_deals`

List deals from Qualifying. Returns a paginated list of deals with their details. Optionally filter by stage to see deals in a specific pipeline stage (e.g., "lead", "qualified", "won", "lost").

Read read

Parameters: limit, page, stage

Generic call

kosmo integrations:call qualifying.qualifying_list_deals '{"limit":1,"page":1,"stage":"example_stage"}' --json

Shortcut

kosmo integrations:qualifying qualifying_list_deals '{"limit":1,"page":1,"stage":"example_stage"}' --json

`qualifying.qualifying_get_current_user`

Get the profile of the currently authenticated Qualifying user. Returns user details such as name, email, and role. Useful for verifying the connection and understanding whose credentials are being used.

Read read

Parameters: none

Generic call

kosmo integrations:call qualifying.qualifying_get_current_user '{}' --json

Shortcut

kosmo integrations:qualifying qualifying_get_current_user '{}' --json

Function Schemas

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

qualifying.qualifying_list_accounts 2 parameters

Schema command

kosmo integrations:schema qualifying.qualifying_list_accounts --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of accounts to return per page (default: 25, max: 100).
`page`	integer	no	Page number for pagination (default: 1).

qualifying.qualifying_get_account 1 parameters

Schema command

kosmo integrations:schema qualifying.qualifying_get_account --json

Parameter	Type	Required	Description
`id`	string	yes	The unique identifier of the account.

qualifying.qualifying_list_contacts 3 parameters

Schema command

kosmo integrations:schema qualifying.qualifying_list_contacts --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of contacts to return per page (default: 25, max: 100).
`page`	integer	no	Page number for pagination (default: 1).
`account_id`	string	no	Filter contacts by account ID to return only contacts associated with a specific account.

qualifying.qualifying_get_contact 1 parameters

Schema command

kosmo integrations:schema qualifying.qualifying_get_contact --json

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

qualifying.qualifying_list_deals 3 parameters

Schema command

kosmo integrations:schema qualifying.qualifying_list_deals --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of deals to return per page (default: 25, max: 100).
`page`	integer	no	Page number for pagination (default: 1).
`stage`	string	no	Filter deals by pipeline stage (e.g., "lead", "qualified", "proposal", "won", "lost").

qualifying.qualifying_get_current_user 0 parameters

Schema command

kosmo integrations:schema qualifying.qualifying_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.