How to integrate Phantombuster MCP with Claude Agent SDK

This guide walks you through connecting Phantombuster to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Phantombuster agent that can download agent usage csv for last month, list all active agents in your account, get the country for this ip address through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Phantombuster account through Composio's Phantombuster MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Phantombuster logoPhantombuster
Api Key

Phantombuster is a cloud-based automation platform for extracting web data and automating actions online. It helps you automate lead generation, web scraping, and social media workflows at scale.

53 Tools

Introduction

This guide walks you through connecting Phantombuster to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Phantombuster agent that can download agent usage csv for last month, list all active agents in your account, get the country for this ip address through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Phantombuster account through Composio's Phantombuster MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Phantombuster with

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Phantombuster
  • Configure an AI agent that can use Phantombuster as a tool
  • Run a live chat session where you can ask the agent to perform Phantombuster operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the Phantombuster MCP server, and what's possible with it?

The Phantombuster MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Phantombuster account. It provides structured and secure access to your web automation and data extraction tools, so your agent can perform actions like running agents, fetching reports, exporting usage data, and managing your automations on your behalf.

  • Agent management and monitoring: Instantly list, audit, or fetch details about all your Phantombuster agents and see which are active, deleted, or grouped together.
  • Data extraction and export: Have your agent export detailed usage reports or download CSVs of agent and container activity for analytics and compliance.
  • Automation workflow insight: Get visibility into branches, containers, and deployment differences—helping you track automation changes and resource usage.
  • Organization and account overview: Let your agent retrieve comprehensive organization information or check current API key associations for security and collaboration.
  • IP geolocation support: Enable your agent to look up the physical location of specific IP addresses for auditing or compliance checks.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Phantombuster account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Phantombuster functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Phantombuster
  const session = await composio.create(USER_ID, {
    toolkits: ['phantombuster'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Phantombuster
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Phantombuster tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Phantombuster
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Phantombuster and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['phantombuster']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Phantombuster tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Phantombuster through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

Every Phantombuster action and event your agent gets out of the box.

Abort Agent (v1)

Tool to abort all running instances of an agent using the legacy v1 API.

Delete Agent

Tool to delete an agent by id.

Delete Lead Objects

Tool to delete one or more lead objects from organization storage.

Delete Many Leads

Tool to delete multiple leads from organization storage.

Delete List

Tool to delete a storage list by id (Beta).

Delete Script

Tool to delete a script by id.

Get Agent

Tool to get an agent by its ID.

Get Agent Containers (v1)

Tool to get a list of ended containers for an agent, ordered by date.

Get Agent Output (v1)

Tool to get incremental data from an agent including console output, status, progress and messages.

Get All Agents

Tool to fetch all agents associated with the current user or organization.

Get Deleted Agents

Tool to get deleted agents for the current user or organization.

Get Branches Diff

Tool to get the length difference between the staging and release branch of all scripts.

Get All Branches

Tool to fetch all branches associated with the current organization.

Get Containers Fetch All

Tool to get all containers associated with a specified agent.

Get Leads By List

Tool to fetch leads by their list ID.

Get IP Location

Tool to retrieve the country of a given or environment IP address.

Export Agent Usage CSV

Tool to export agent usage CSV for current organization.

Export Container Usage CSV

Tool to export container usage CSV for current organization.

Get Organization

Tool to fetch current organization details.

Get Agent Groups

Tool to get agent groups and order for the current organization.

Get Organization Resources

Tool to get current organization's resources and usage.

Get Org Running Containers

Tool to get the current organization's running containers.

Get Org Storage Lists Fetch All

Tool to fetch all storage lists for the authenticated organization.

Get Script

Tool to fetch a script by its unique ID.

Get Script by Name

Tool to retrieve a script by its name from Phantombuster (Legacy v1 API).

Get Script Code

Tool to get the code of a script.

Get All Scripts

Tool to fetch all scripts for the current user.

Get User Information

Tool to get information about your PhantomBuster account and your agents using the legacy v1 API.

Unschedule All Agent Launches

Tool to unschedule all scheduled launches for agents.

Request AI Completion

Tool to request a text completion from the AI module.

Create Branch

Tool to create a new branch.

Delete Branch

Tool to delete a branch by id.

Solve hCaptcha

Tool to solve an hCaptcha challenge.

Generate Identity Token

Tool to generate an identity token for PhantomBuster.

Save Many Leads

Tool to save multiple leads (1-20) to organization storage in a single batch operation (Beta).

Solve reCAPTCHA

Tool to solve a reCAPTCHA challenge (v2 or v3).

Update Script Visibility

Tool to update the visibility of a script.

Release Branch

Tool to release a script branch.

Save Agent

Tool to create a new agent or update an existing one.

Save Agent Groups

Tool to update agent groups and order for the current user's organization.

Save Company Object

Tool to save one company object to the organization storage.

Save Many Company Objects

Tool to save many company objects to organization storage.

Save Identity Event

Tool to save an identity event to Phantombuster.

Save Lead

Tool to save or update a lead in Phantombuster org storage.

Save Lead Object

Tool to save a lead object to organization storage.

Save Many Lead Objects

Tool to save multiple lead objects to Phantombuster's organization storage.

Save List

Tool to save (create or update) a list with filter criteria.

Save Script

Tool to create a new script or update an existing one.

Search Company Objects

Tool to search company objects in Phantombuster's organizational storage.

Search Lead Objects

Tool to search lead objects in Phantombuster org storage.

Stop Agent

Tool to stop a running agent.

Update Script (v1 API)

Tool to update an existing script or create a new one if it does not exist (Legacy v1 API).

Update Script Access List

Tool to update the access list of a script.

FAQ

Frequently asked questions

With a standalone Phantombuster MCP server, the agents and LLMs can only access a fixed set of Phantombuster tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Phantombuster and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Agent SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Phantombuster tools.

Yes, absolutely. You can configure which Phantombuster scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Phantombuster data and credentials are handled as safely as possible.

Start with Phantombuster.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Phantombuster tool your agent needs.Free to start.

Start building