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 CI

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

6 functions 5 read 1 write API key auth

Submit Phantombuster feedback View package source

Phantombuster CLI for CI

Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status.

Use this shape when a pipeline needs to read or update an external service. The Phantombuster CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Phantombuster CLI for CI
kosmokrator integrations:configure phantombuster --set api_key="$PHANTOMBUSTER_API_KEY" --enable --read allow --write ask --json
kosmo integrations:call phantombuster.phantombuster_list_agents '{}' --json

Discovery Before Execution

Agents and scripts can inspect Phantombuster docs and schemas 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

Useful Phantombuster CLI Functions

Function	Type	Parameters	Description
`phantombuster.phantombuster_list_agents`	Read	none	List all Phantombuster agents in your account. Returns agent IDs, names, and status so you can inspect or launch them.
`phantombuster.phantombuster_get_agent`	Read	id	Get details for a specific Phantombuster agent, including its configuration, last run status, and output.
`phantombuster.phantombuster_launch_agent`	Write	id	Launch a Phantombuster agent to start an automation. Returns the container ID for tracking execution progress.
`phantombuster.phantombuster_list_containers`	Read	none	List all Phantombuster containers (execution runs). Returns container IDs, associated agent IDs, status, and timestamps.
`phantombuster.phantombuster_get_container`	Read	id	Get details for a specific Phantombuster container (execution run), including its status, output, and logs.
`phantombuster.phantombuster_get_current_user`	Read	none	Get the authenticated Phantombuster user profile, including account info and plan details.

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 Phantombuster CLI Pages

Cron Jobs Phantombuster CLI for cron jobs. Shell Scripts Phantombuster CLI for shell scripts. Headless Automation Phantombuster CLI for headless automation. Coding Agents Phantombuster CLI for coding agents.