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 MCP Integration for CrewAI

Connect Qualifying to CrewAI through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

6 functions 6 read 0 write Bearer token auth

Submit Qualifying feedback View package source

Connect Qualifying to CrewAI

Expose KosmoKrator integrations to CrewAI workers as scoped local tools.

Wrap kosmo integrations:call for specific tasks or connect workers to a local MCP gateway. The gateway is local, scoped to this integration, and starts with --write=deny so CrewAI can inspect read-capable tools without receiving write access by default.

Qualifying MCP Config for CrewAI

Use per-worker integration scopes to avoid giving every worker every tool.

{
  "mcpServers": {
    "kosmokrator-qualifying": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=qualifying",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=qualifying --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Qualifying instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Qualifying Tools Visible to CrewAI

CrewAI sees stable MCP tool names generated from the Qualifying integration catalog.

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

Related Qualifying Pages

Qualifying CLIUse direct JSON commands instead of MCP discovery. Qualifying MCPFull gateway reference and MCP tool names. KosmoKrator for CrewAIClient-level gateway setup.