How to integrate Bannerbear MCP with Claude Agent SDK

This guide walks you through connecting Bannerbear to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Bannerbear agent that can merge multiple marketing pdfs into one file, list all video assets created this week, get available fonts for instagram templates through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Bannerbear account through Composio's Bannerbear MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Bannerbear logoBannerbear
Api Key

Bannerbear is an API-driven platform for generating images and videos automatically at scale. It helps businesses create custom graphics, social visuals, and marketing assets using powerful templates.

33 Tools

Introduction

This guide walks you through connecting Bannerbear to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Bannerbear agent that can merge multiple marketing pdfs into one file, list all video assets created this week, get available fonts for instagram templates through natural language commands.

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

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

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

The Bannerbear MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Bannerbear account. It provides structured and secure access to your Bannerbear workspace, so your agent can generate images, create videos, manage templates, merge PDFs, and retrieve creative assets on your behalf.

  • Automated image and video generation: Enable your agent to create customized graphics or videos at scale using your Bannerbear templates and project assets.
  • Template browsing and management: Let your agent list, inspect, and select templates or template sets for creative projects, making it easy to automate content workflows.
  • Font and asset discovery: Have your agent retrieve available fonts and signed bases, ensuring the right design elements are used for every creative output.
  • PDF merging automation: Direct your agent to combine multiple PDFs into a single document, streamlining report or collateral creation.
  • Account and usage monitoring: Allow your agent to fetch current account status, API usage, and quota information to keep your creative operations running smoothly.

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

Create Project

Creates a new Bannerbear project with the specified name and optional settings.

Create Signed Base

Tool to create a signed URL base for a template.

Create Template

Create a new blank template in a Bannerbear project.

Create Template Set

Tool to create a new template set by grouping multiple templates together.

Create Video Template

Tool to create a new video template for video generation in Bannerbear.

Create Webhook

Create a project-level webhook that fires for all events of a specific type.

Delete Template

Tool to delete a template referenced by its unique ID.

Delete Webhook

Tool to delete a webhook referenced by its unique ID.

Get Account Info

Retrieves Bannerbear account information including subscription plan, API usage, and quota limits.

Get Animated GIF

Tool to retrieve a single Animated Gif object by its unique identifier (UID).

Get Auth Status

Verify API authentication and check which project the API key is scoped to.

Get Available Fonts

This tool retrieves a list of all available fonts in Bannerbear.

Get Image

Retrieves a single Image object by its unique identifier (UID).

Get Project

Retrieves detailed information about a specific Bannerbear project by its unique identifier (UID).

Get Screenshot

Retrieve a single Screenshot object referenced by its unique ID.

Get Signed Bases

This tool retrieves a list of signed bases for a specific template.

Get Template

Tool to retrieve a single template by its unique ID with layer defaults.

Get Template Set Details

This tool retrieves detailed information about a specific template set using its unique identifier (UID).

Get Webhook

Retrieves a single Webhook object by its unique ID.

Hydrate Project

Hydrate a project by copying templates from another project.

Import Template

Tool to import templates from the Bannerbear template library or from other projects.

Join PDFs

Merges multiple PDF files into a single combined PDF document.

List Animated GIFs

Lists all animated GIFs in a Bannerbear project.

List Collections

Lists all collections in a Bannerbear project.

List Effects

Tool to list all available image effects in Bannerbear.

List Images

Lists all images in a Bannerbear project.

List Projects

Lists all projects in a Bannerbear account.

List Screenshots

Lists all screenshots in a Bannerbear project.

List Templates

This action retrieves a list of all templates available in your Bannerbear project.

List Template Sets

Tool to list all template sets inside a project with pagination support.

List Videos

This action retrieves a list of all videos created in your Bannerbear account.

List Video Templates

This action retrieves a list of all video templates available in your Bannerbear project.

Update Template Set

Tool to update a template set by modifying its list of templates.

FAQ

Frequently asked questions

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

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

Start with Bannerbear.It takes 30 seconds.

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

Start building