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.

sales

Qualifying CLI for Headless Automation

Use the Qualifying CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

6 functions 6 read 0 write Bearer token auth

Submit Qualifying feedback View package source

Qualifying CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Qualifying CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Qualifying CLI for Headless Automation
kosmokrator integrations:configure qualifying --set access_token="$QUALIFYING_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call qualifying.qualifying_list_accounts '{"limit":1,"page":1}' --json

Discovery Before Execution

Agents and scripts can inspect Qualifying docs and schemas before choosing a function.

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

Useful Qualifying CLI Functions

Function	Type	Parameters	Description
`qualifying.qualifying_list_accounts`	Read	limit, page	List sales accounts from Qualifying. Returns a paginated list of accounts with their details. Use limit and page parameters to navigate through results.
`qualifying.qualifying_get_account`	Read	id	Get detailed information about a specific sales account in Qualifying. Returns the account's full profile including name, industry, website, and associated metadata.
`qualifying.qualifying_list_contacts`	Read	limit, page, account_id	List contacts from Qualifying. Returns a paginated list of contacts. Optionally filter by account to see contacts belonging to a specific account.
`qualifying.qualifying_get_contact`	Read	id	Get detailed information about a specific contact in Qualifying. Returns the contact's full profile including name, email, phone, associated account, and other metadata.
`qualifying.qualifying_list_deals`	Read	limit, page, stage	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").
`qualifying.qualifying_get_current_user`	Read	none	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.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Qualifying CLI Pages

CI Qualifying CLI for CI. Cron Jobs Qualifying CLI for cron jobs. Shell Scripts Qualifying CLI for shell scripts. Coding Agents Qualifying CLI for coding agents.