How to integrate Botpress MCP with Claude Agent SDK

This guide walks you through connecting Botpress to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Botpress agent that can list all active conversations for your bot, show issues reported for a specific bot, delete a file from a bot workspace through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Botpress account through Composio's Botpress MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Botpress logoBotpress
Api Key

Botpress is an open-source platform for building, deploying, and managing chatbots. It helps teams automate conversations and deliver rich, interactive messaging experiences.

53 Tools

Introduction

This guide walks you through connecting Botpress to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Botpress agent that can list all active conversations for your bot, show issues reported for a specific bot, delete a file from a bot workspace through natural language commands.

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

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

Also integrate Botpress 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 Botpress
  • Configure an AI agent that can use Botpress as a tool
  • Run a live chat session where you can ask the agent to perform Botpress 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 Botpress MCP server, and what's possible with it?

The Botpress MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Botpress account. It provides structured and secure access to your chatbot platform, so your agent can perform actions like listing conversations, managing bot files, tracking issues, and exploring workspaces on your behalf.

  • Comprehensive conversation management: Retrieve and paginate through all chatbot conversations, making it easy to review chat history and analyze user interactions.
  • Bot issue tracking and diagnostics: List and investigate issues related to specific bots, helping you stay informed about errors or configuration problems as they arise.
  • Workspace discovery and organization: Browse both public and private workspaces, making it seamless to manage your bot environments or explore new collaborative spaces.
  • File and tag oversight: List, manage, and categorize bot files and their associated tags or tag values, streamlining bot asset organization.
  • Account information access: Instantly fetch authenticated account details so your agent always works with the latest profile and permission data.

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 Botpress 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 Botpress 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 Botpress
  const session = await composio.create(USER_ID, {
    toolkits: ['botpress'],
  });
  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 Botpress
  • 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 Botpress 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 Botpress
  • 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 Botpress 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: ['botpress']
  });
  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 Botpress 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 Botpress 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 Botpress action and event your agent gets out of the box.

Break Down Workspace Usage By Bot

Tool to break down workspace usage by bot.

BOTPRESS_CHARGE_WORKSPACE_UNPAID_INVOICES

Tool to charge unpaid invoices for a specific Botpress workspace.

Check Handle Availability

Tool to check if a workspace handle is available in Botpress.

BOTPRESS_CREATE_ADMIN_INTEGRATION

Tool to create a new integration in a Botpress workspace via the Admin API.

BOTPRESS_CREATE_ADMIN_WORKSPACE

Tool to create a new workspace in Botpress via the Admin API.

BOTPRESS_CREATE_BOT

Tool to create a new bot in a Botpress workspace via the Admin API.

BOTPRESS_CREATE_CONVERSATION

Tool to create a new conversation in Botpress via the Runtime API.

Delete Admin Workspace

Tool to permanently delete a workspace from Botpress admin.

Delete File

Permanently deletes a file from a Botpress bot's storage by its file ID.

Delete Integration Shareable ID

Tool to delete a shareable ID for an integration installed in a Botpress bot.

Delete Knowledge Base

Permanently deletes a knowledge base from Botpress by its knowledge base ID.

Get Account

Tool to get details of the authenticated account.

Get Account Preference

Tool to get a preference of the account.

Get All Workspace Quota Completion

Tool to get a map of workspace IDs to their highest quota completion rate.

Get Dereferenced Public Plugin By ID

Tool to get a public plugin by ID with all interface entity references resolved to the corresponding entities as extended by the backing integrations.

Get Integration

Tool to get a specific Botpress integration by name and version.

Get Public Integration

Tool to retrieve a public integration by name and version from the Botpress hub.

Get Public Integration By ID

Tool to retrieve detailed information about a public Botpress integration by its ID.

Get Public Interface

Tool to get a public interface by name and version from the Botpress Hub.

Get Public Interface by ID

Tool to retrieve a public interface by its ID from the Botpress Hub.

Get Public Plugin

Tool to retrieve detailed information about a public plugin from Botpress Hub by name and version.

Get Public Plugin By ID

Tool to retrieve details of a public plugin by its unique ID.

Get Public Plugin Code

Tool to retrieve public plugin code from Botpress Hub.

Get Table Row

Tool to fetch a specific row from a table using the row's unique identifier.

Get Upcoming Invoice

Tool to get the upcoming invoice for a workspace.

Get Workspace

Tool to get detailed information about a specific Botpress workspace by ID.

Get Workspace Quota

Tool to get workspace quota information for a specific usage type.

LIST_ACTION_RUNS

Tool to list action runs for a specific integration of a bot.

LIST_BOT_ISSUES

Tool to list issues associated with a specific bot.

LIST_CONVERSATIONS

Tool to list all Conversations.

LIST_FILE_TAGS

Tool to list all tags used across all bot files.

LIST_FILE_TAG_VALUES

Tool to list all values for a given file tag across all files.

LIST_HUB_INTEGRATIONS

Tool to list public integrations from the Botpress hub.

LIST_INTEGRATION_API_KEYS

Tool to list Integration API Keys (IAKs) for a specific integration.

List Integrations

Tool to list integrations with filtering and sorting capabilities.

LIST_KNOWLEDGE_BASES

Tool to list knowledge bases for a bot.

List Plugins

Tool to list Botpress plugins.

List Public Interfaces

Tool to retrieve a list of public interfaces available in the Botpress Hub.

LIST_PUBLIC_PLUGINS

Tool to retrieve a list of public plugins available in the Botpress hub.

LIST_PUBLIC_WORKSPACES

Tool to retrieve a list of public workspaces.

LIST_USAGE_HISTORY

Tool to retrieve usage history for a bot or workspace.

List Workspace Invoices

Tool to list all invoices billed to a workspace.

LIST_WORKSPACES

List all Botpress workspaces accessible to the authenticated user.

Request Integration Verification

Tool to request verification for a Botpress integration via the Admin API.

BOTPRESS_RUN_VRL

Tool to execute a VRL (Vector Remap Language) script against input data using the Botpress Admin API.

BOTPRESS_SEND_MESSAGE

Tool to send a message to an existing Botpress conversation via the Runtime API.

Set Account Preference

Tool to set a preference for the account.

Set Workspace Preference

Tool to set a preference for a Botpress workspace.

Update Account

Tool to update details of the authenticated account.

BOTPRESS_UPDATE_ADMIN_BOTS

Tool to update an existing bot in a Botpress workspace via the Admin API.

UPDATE_ADMIN_WORKSPACE

Tool to update a Botpress workspace via the Admin API.

BOTPRESS_UPDATE_WORKFLOW

Tool to update a workflow object in Botpress by setting parameter values.

BOTPRESS_VALIDATE_INTEGRATION_UPDATE

Tool to validate an integration update request in Botpress Admin API.

FAQ

Frequently asked questions

With a standalone Botpress MCP server, the agents and LLMs can only access a fixed set of Botpress tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Botpress 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 Botpress tools.

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

Start with Botpress.It takes 30 seconds.

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

Start building