Can I use Phantombuster as a CLI?

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

Can I expose Phantombuster through MCP?

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

Where are Phantombuster credentials stored?

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

Can I deny write access for Phantombuster MCP tools?

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

automation

Phantombuster CLI for AI Agents

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

6 functions 5 read 1 write API key auth

Submit Phantombuster feedback View package source

Phantombuster CLI Setup

Phantombuster can be configured headlessly with `kosmokrator integrations:configure phantombuster`.

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

Credentials

Authentication type: API key api_key. 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
`api_key`	`PHANTOMBUSTER_API_KEY`	Secret `secret`	yes	API Key
`url`	`PHANTOMBUSTER_URL`	URL `url`	no	API Base URL

Call Phantombuster Headlessly

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

kosmo integrations:call phantombuster.phantombuster_list_agents '{}' --json

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

kosmo integrations:phantombuster phantombuster_list_agents '{}' --json

Agent Discovery Commands

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

kosmo integrations:docs phantombuster --json
kosmo integrations:docs phantombuster.phantombuster_list_agents --json
kosmo integrations:schema phantombuster.phantombuster_list_agents --json
kosmo integrations:search "Phantombuster" --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 Phantombuster.

`phantombuster.phantombuster_list_agents`

Read read

List all Phantombuster agents in your account. Returns agent IDs, names, and status so you can inspect or launch them.

Parameters: none

Generic CLI call

kosmo integrations:call phantombuster.phantombuster_list_agents '{}' --json

Provider shortcut

kosmo integrations:phantombuster phantombuster_list_agents '{}' --json

`phantombuster.phantombuster_get_agent`

Read read

Get details for a specific Phantombuster agent, including its configuration, last run status, and output.

Parameters: id

Generic CLI call

kosmo integrations:call phantombuster.phantombuster_get_agent '{"id":"example_id"}' --json

Provider shortcut

kosmo integrations:phantombuster phantombuster_get_agent '{"id":"example_id"}' --json

`phantombuster.phantombuster_launch_agent`

Write write

Launch a Phantombuster agent to start an automation. Returns the container ID for tracking execution progress.

Parameters: id

Generic CLI call

kosmo integrations:call phantombuster.phantombuster_launch_agent '{"id":"example_id"}' --json

Provider shortcut

kosmo integrations:phantombuster phantombuster_launch_agent '{"id":"example_id"}' --json

`phantombuster.phantombuster_list_containers`

Read read

List all Phantombuster containers (execution runs). Returns container IDs, associated agent IDs, status, and timestamps.

Parameters: none

Generic CLI call

kosmo integrations:call phantombuster.phantombuster_list_containers '{}' --json

Provider shortcut

kosmo integrations:phantombuster phantombuster_list_containers '{}' --json

`phantombuster.phantombuster_get_container`

Read read

Get details for a specific Phantombuster container (execution run), including its status, output, and logs.

Parameters: id

Generic CLI call

kosmo integrations:call phantombuster.phantombuster_get_container '{"id":"example_id"}' --json

Provider shortcut

kosmo integrations:phantombuster phantombuster_get_container '{"id":"example_id"}' --json

`phantombuster.phantombuster_get_current_user`

Read read

Get the authenticated Phantombuster user profile, including account info and plan details.

Parameters: none

Generic CLI call

kosmo integrations:call phantombuster.phantombuster_get_current_user '{}' --json

Provider shortcut

kosmo integrations:phantombuster phantombuster_get_current_user '{}' --json

Function Schemas

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

`phantombuster.phantombuster_list_agents`

List all Phantombuster agents in your account. Returns agent IDs, names, and status so you can inspect or launch them.

Operation: Read read
Schema command: kosmo integrations:schema phantombuster.phantombuster_list_agents --json

Parameter	Type	Required	Description
No parameters.

`phantombuster.phantombuster_get_agent`

Get details for a specific Phantombuster agent, including its configuration, last run status, and output.

Operation: Read read
Schema command: kosmo integrations:schema phantombuster.phantombuster_get_agent --json

Parameter	Type	Required	Description
`id`	string	yes	The agent ID (e.g., "1234567890123456789").

`phantombuster.phantombuster_launch_agent`

Launch a Phantombuster agent to start an automation. Returns the container ID for tracking execution progress.

Operation: Write write
Schema command: kosmo integrations:schema phantombuster.phantombuster_launch_agent --json

Parameter	Type	Required	Description
`id`	string	yes	The agent ID to launch (e.g., "1234567890123456789").

`phantombuster.phantombuster_list_containers`

List all Phantombuster containers (execution runs). Returns container IDs, associated agent IDs, status, and timestamps.

Operation: Read read
Schema command: kosmo integrations:schema phantombuster.phantombuster_list_containers --json

Parameter	Type	Required	Description
No parameters.

`phantombuster.phantombuster_get_container`

Get details for a specific Phantombuster container (execution run), including its status, output, and logs.

Operation: Read read
Schema command: kosmo integrations:schema phantombuster.phantombuster_get_container --json

Parameter	Type	Required	Description
`id`	string	yes	The container ID (e.g., "9876543210987654321").

`phantombuster.phantombuster_get_current_user`

Get the authenticated Phantombuster user profile, including account info and plan details.

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