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

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

6 functions 5 read 1 write API key auth

Submit Phantombuster feedback View package source

Connect Phantombuster to Codex

Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy.

Register kosmo mcp:serve as a local stdio server and choose the integration allowlist. The gateway is local, scoped to this integration, and starts with --write=deny so Codex can inspect read-capable tools without receiving write access by default.

Phantombuster MCP Config for Codex

Keep write access denied or ask-based unless the workspace is trusted.

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

Expose only Phantombuster 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.

Phantombuster Tools Visible to Codex

Codex sees stable MCP tool names generated from the Phantombuster integration catalog.

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

Related Phantombuster Pages

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