How to integrate Supportbee MCP with Claude Agent SDK

This guide walks you through connecting Supportbee to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Supportbee agent that can archive all tickets resolved this week, assign new tickets to the support team, create a reusable snippet for refund replies through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Supportbee account through Composio's Supportbee MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Supportbee logoSupportbee
Api Key

SupportBee is a web-based email support tool for organizing customer support emails. It streamlines team collaboration and keeps customer conversations efficient and accessible.

41 Tools

Introduction

This guide walks you through connecting Supportbee to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Supportbee agent that can archive all tickets resolved this week, assign new tickets to the support team, create a reusable snippet for refund replies through natural language commands.

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

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

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

The Supportbee MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Supportbee account. It provides structured and secure access to your support ticketing system, so your agent can perform actions like creating and replying to tickets, managing team assignments, organizing tickets, and automating support workflows on your behalf.

  • Automated ticket creation and updates: Instantly open new support tickets, update their content, or post replies to customer inquiries without leaving your workflow.
  • Team assignment and ticket routing: Direct your agent to assign tickets to the right team or agent, ensuring every request is handled by the appropriate group.
  • Archiving and deleting tickets: Keep your helpdesk organized by having the agent archive resolved tickets or permanently remove unwanted ones from the system.
  • Reusable response snippets: Let your agent create, manage, and delete response templates so your team can reply faster and more consistently.
  • Rule-based workflow automation: Empower your agent to create new automation rules that streamline ticket routing, escalation, and handling based on custom conditions.

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

Add Label to Ticket

Tool to add a label to a ticket.

Archive SupportBee Ticket

Tool to archive a SupportBee ticket by its ID.

Assign Ticket to Team

Assigns a ticket to a team in SupportBee.

Create Ticket Comment

Creates an internal comment on a ticket in SupportBee.

Create Consequence

Creates a new consequence for rules automation in SupportBee.

Create Forwarding Email

Create a new forwarding email address for the company in SupportBee.

Create Filter

Creates a filter in SupportBee by linking a rule with a consequence.

Create Rule

Creates a new automation rule in SupportBee to automatically process tickets based on conditions.

Create Snippet

Create a reusable snippet (canned response) in SupportBee.

Create SupportBee Ticket

Creates a new support ticket in SupportBee with a subject, content, and requester details.

Create Ticket Reply

Create a reply to a support ticket in SupportBee.

Create SupportBee User

Invites a new user to your SupportBee account.

Delete Snippet

Permanently delete a snippet by its ID from SupportBee.

Delete SupportBee Ticket

Permanently delete a trashed ticket from SupportBee.

Fetch Forwarding Emails

Retrieve all forwarding email addresses configured for the company.

Fetch SupportBee Labels

Tool to retrieve all custom labels.

Fetch Snippets

Fetches saved response snippets (canned responses/templates) from SupportBee.

Fetch SupportBee Teams

Retrieves all teams in the SupportBee account.

Get Avg First Response Time Report

Tool to retrieve average first response time data points over time.

Get Replies Count Report

Retrieves replies count report data for the company.

Get Ticket

Tool to retrieve a specific SupportBee ticket by its ID.

Get Tickets Count Report

Tool to get ticket count data points over time.

List Ticket Comments

Retrieves all internal comments (private agent notes) for a specific ticket.

List Ticket Replies

Lists all replies on a specific support ticket in SupportBee.

List Tickets

Tool to list tickets from SupportBee.

List SupportBee Users

Retrieves all users and customer groups in your SupportBee company.

Mark SupportBee Ticket as Answered

Marks a SupportBee ticket as answered by adding the 'answered' status.

Mark SupportBee Ticket as Spam

Tool to mark a SupportBee ticket as spam.

Mark SupportBee Ticket as Unanswered

Marks a SupportBee ticket as unanswered by removing its 'answered' status.

Remove Label From Ticket

Tool to remove a label from a ticket.

Search SupportBee Tickets

Tool to search SupportBee tickets.

Show Ticket Reply

Tool to fetch a specific reply for a SupportBee ticket.

Show SupportBee User or Customer Group

Retrieves details of a SupportBee user (agent/admin) or customer group by their ID.

Trash SupportBee Ticket

Tool to trash a SupportBee ticket by its ID.

Unarchive SupportBee Ticket

Tool to unarchive a SupportBee ticket by its ID.

Unassign Ticket from Team

Tool to un-assign a ticket from its assigned team.

Unassign User From Ticket

Tool to un-assign a ticket from its assigned user/agent.

Unmark SupportBee Ticket as Spam

Tool to unmark a SupportBee ticket as spam.

Untrash SupportBee Ticket

Restores a trashed SupportBee ticket back to active status.

Update Snippet

Update an existing snippet (canned response) in SupportBee.

Update SupportBee User

Update an existing SupportBee user's profile information including name, email, role, avatar, or signature.

FAQ

Frequently asked questions

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

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

Start with Supportbee.It takes 30 seconds.

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

Start building