How to integrate Botster MCP with Pydantic AI

This guide walks you through connecting Botster to Pydantic AI using the Composio tool router. By the end, you'll have a working Botster agent that can list your bots, launch bots, check job results, restart jobs, and manage archived jobs through natural language commands. This guide will help you understand how to give your Pydantic AI agent real control over a Botster account through Composio's Botster MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Botster logoBotster
Api Key

Botster is a web automation service for running configurable data collection bots. Use it to collect structured web data without building and maintaining scrapers yourself.

11 Tools

Introduction

This guide walks you through connecting Botster to Pydantic AI using the Composio tool router. By the end, you'll have a working Botster agent that can list your bots, launch bots, check job results, restart jobs, and manage archived jobs through natural language commands.

This guide will help you understand how to give your Pydantic AI agent real control over a Botster account through Composio's Botster MCP server.

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

Also integrate Botster with

TL;DR

Here's what you'll learn:
  • How to set up your Composio API key and User ID
  • How to create a Composio Tool Router session for Botster
  • How to attach an MCP Server to a Pydantic AI agent
  • How to stream responses and maintain chat history
  • How to build a simple REPL-style chat interface to test your Botster workflows

What is Pydantic AI?

Pydantic AI is a Python framework for building AI agents with strong typing and validation. It leverages Pydantic's data validation capabilities to create robust, type-safe AI applications.

Key features include:

  • Type Safety: Built on Pydantic for automatic data validation
  • MCP Support: Native support for Model Context Protocol servers
  • Streaming: Built-in support for streaming responses
  • Async First: Designed for async/await patterns

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

The Botster MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Botster account. It provides structured and secure access to your bots, jobs, credit balance, and run results, so your agent can find bots, estimate costs, launch jobs, monitor progress, and retrieve collected data on your behalf.

  • Bot discovery and cost planning: Have your agent search your available bots and calculate the credit cost of a planned launch before starting it.
  • Bot launches and job restarts: Direct your agent to launch a selected bot or restart an existing job when you need fresh data.
  • Job monitoring and credit checks: Let the agent review your jobs, inspect their current status, and check your available credit balance before running more work.
  • Structured result retrieval: Instruct your agent to fetch the complete collected results from a finished bot run for analysis or use in another workflow.
  • Job and run cleanup: Have your agent archive or restore jobs, delete individual runs, or permanently remove jobs you no longer need.

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:
  • Python 3.9 or higher
  • A Composio account with an active API key
  • Basic familiarity with Python and async programming
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • 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

bash
pip install composio pydantic-ai python-dotenv

Install the required libraries.

What's happening:

  • composio connects your agent to external SaaS tools like Botster
  • pydantic-ai lets you create structured AI agents with tool support
  • python-dotenv loads your environment variables securely from a .env file
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your agent to Composio's API
  • USER_ID associates your session with your account for secure tool access
  • OPENAI_API_KEY to access OpenAI LLMs
5

Import dependencies

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStreamableHTTP

load_dotenv()
What's happening:
  • We load environment variables and import required modules
  • Composio manages connections to Botster
  • MCPServerStreamableHTTP connects to the Botster MCP server endpoint
  • Agent from Pydantic AI lets you define and run the AI assistant
6

Create a Tool Router Session

python
async def main():
    api_key = os.getenv("COMPOSIO_API_KEY")
    user_id = os.getenv("USER_ID")
    if not api_key or not user_id:
        raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment")

    # Create a Composio Tool Router session for Botster
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["botster"],
    )
    url = session.mcp.url
    if not url:
        raise ValueError("Composio session did not return an MCP URL")
What's happening:
  • We're creating a Tool Router session that gives your agent access to Botster tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
7

Initialize the Pydantic AI Agent

python
# Attach the MCP server to a Pydantic AI Agent
botster_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
agent = Agent(
    "openai:gpt-5",
    toolsets=[botster_mcp],
    instructions=(
        "You are a Botster assistant. Use Botster tools to help users "
        "with their requests. Ask clarifying questions when needed."
    ),
)
What's happening:
  • The MCP client connects to the Botster endpoint
  • The agent uses GPT-5 to interpret user commands and perform Botster operations
  • The instructions field defines the agent's role and behavior
8

Build the chat interface

python
# Simple REPL with message history
history = []
print("Chat started! Type 'exit' or 'quit' to end.\n")
print("Try asking the agent to help you with Botster.\n")

while True:
    user_input = input("You: ").strip()
    if user_input.lower() in {"exit", "quit", "bye"}:
        print("\nGoodbye!")
        break
    if not user_input:
        continue

    print("\nAgent is thinking...\n", flush=True)

    async with agent.run_stream(user_input, message_history=history) as stream_result:
        collected_text = ""
        async for chunk in stream_result.stream_output():
            text_piece = None
            if isinstance(chunk, str):
                text_piece = chunk
            elif hasattr(chunk, "delta") and isinstance(chunk.delta, str):
                text_piece = chunk.delta
            elif hasattr(chunk, "text"):
                text_piece = chunk.text
            if text_piece:
                collected_text += text_piece
        result = stream_result

    print(f"Agent: {collected_text}\n")
    history = result.all_messages()
What's happening:
  • The agent reads input from the terminal and streams its response
  • Botster API calls happen automatically under the hood
  • The model keeps conversation history to maintain context across turns
9

Run the application

python
if __name__ == "__main__":
    asyncio.run(main())
What's happening:
  • The asyncio loop launches the agent and keeps it running until you exit

Complete Code

Here's the complete code to get you started with Botster and Pydantic AI:

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStreamableHTTP

load_dotenv()

async def main():
    api_key = os.getenv("COMPOSIO_API_KEY")
    user_id = os.getenv("USER_ID")
    if not api_key or not user_id:
        raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment")

    # Create a Composio Tool Router session for Botster
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["botster"],
    )
    url = session.mcp.url
    if not url:
        raise ValueError("Composio session did not return an MCP URL")

    # Attach the MCP server to a Pydantic AI Agent
    botster_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
    agent = Agent(
        "openai:gpt-5",
        toolsets=[botster_mcp],
        instructions=(
            "You are a Botster assistant. Use Botster tools to help users "
            "with their requests. Ask clarifying questions when needed."
        ),
    )

    # Simple REPL with message history
    history = []
    print("Chat started! Type 'exit' or 'quit' to end.\n")
    print("Try asking the agent to help you with Botster.\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "bye"}:
            print("\nGoodbye!")
            break
        if not user_input:
            continue

        print("\nAgent is thinking...\n", flush=True)

        async with agent.run_stream(user_input, message_history=history) as stream_result:
            collected_text = ""
            async for chunk in stream_result.stream_output():
                text_piece = None
                if isinstance(chunk, str):
                    text_piece = chunk
                elif hasattr(chunk, "delta") and isinstance(chunk.delta, str):
                    text_piece = chunk.delta
                elif hasattr(chunk, "text"):
                    text_piece = chunk.text
                if text_piece:
                    collected_text += text_piece
            result = stream_result

        print(f"Agent: {collected_text}\n")
        history = result.all_messages()

if __name__ == "__main__":
    asyncio.run(main())

Conclusion

You've built a Pydantic AI agent that can interact with Botster through Composio's Tool Router. With this setup, your agent can perform real Botster actions through natural language. You can extend this further by:
  • Adding other toolkits like Gmail, HubSpot, or Salesforce
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows (for example, Gmail + Botster for workflow automation)
This architecture makes your AI agent "agent-native", able to securely use APIs in a unified, composable way without custom integrations.
TOOLS

Supported Tools

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

Calculate Bot Cost

Calculate the credit price of one intended bot launch using the same input and bot-specific options, without launching the bot or spending credits.

Delete Job

Permanently delete one Botster job.

Delete Run

Permanently delete one Botster data run and its stored results without deleting the entire job.

Get Credit Balance

Return the connected Botster account's available credit balance; use this before launching or restarting credit-consuming work.

Get Job

Get one job's status and data-run identifiers required to retrieve run results.

Get Run Results

Return the complete bot-specific JSON for one data run identified from GET_JOB in the results field.

Launch Bot

Launch a Botster bot, creating external work that may spend account credits.

List Bots

List or search bots available to the connected account and return their identifiers for cost calculation and launch.

List Jobs

List jobs belonging to the connected Botster account and return job identifiers for inspection or lifecycle actions.

Restart Job

Restart an existing Botster job, creating renewed external work that may repeat the bot's effects and spend additional account credits.

Set Job Archived

Archive a Botster job or restore it from the archive by setting its desired archived state.

FAQ

Frequently asked questions

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

Yes, you can. Pydantic AI 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 Botster tools.

Yes, absolutely. You can configure which Botster 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 Botster data and credentials are handled as safely as possible.

Start with Botster.It takes 30 seconds.

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

Start building