How to integrate Bannerbear MCP with Claude Code

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Bannerbear logo
Claude Code logo
divider

Introduction

Manage your Bannerbear directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Bannerbear with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Bannerbear to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

Supported Tools & Triggers

Tools
Create ProjectCreates a new Bannerbear project with the specified name and optional settings.
Create Signed BaseTool to create a signed URL base for a template.
Create TemplateCreate a new blank template in a Bannerbear project.
Create Template SetTool to create a new template set by grouping multiple templates together.
Create Video TemplateTool to create a new video template for video generation in Bannerbear.
Create WebhookCreate a project-level webhook that fires for all events of a specific type.
Delete TemplateTool to delete a template referenced by its unique ID.
Delete WebhookTool to delete a webhook referenced by its unique ID.
Get Account InfoRetrieves Bannerbear account information including subscription plan, API usage, and quota limits.
Get Animated GIFTool to retrieve a single Animated Gif object by its unique identifier (UID).
Get Auth StatusVerify API authentication and check which project the API key is scoped to.
Get Available FontsThis tool retrieves a list of all available fonts in Bannerbear.
Get ImageRetrieves a single Image object by its unique identifier (UID).
Get ProjectRetrieves detailed information about a specific Bannerbear project by its unique identifier (UID).
Get ScreenshotRetrieve a single Screenshot object referenced by its unique ID.
Get Signed BasesThis tool retrieves a list of signed bases for a specific template.
Get TemplateTool to retrieve a single template by its unique ID with layer defaults.
Get Template Set DetailsThis tool retrieves detailed information about a specific template set using its unique identifier (UID).
Get WebhookRetrieves a single Webhook object by its unique ID.
Hydrate ProjectHydrate a project by copying templates from another project.
Import TemplateTool to import templates from the Bannerbear template library or from other projects.
Join PDFsMerges multiple PDF files into a single combined PDF document.
List Animated GIFsLists all animated GIFs in a Bannerbear project.
List CollectionsLists all collections in a Bannerbear project.
List EffectsTool to list all available image effects in Bannerbear.
List ImagesLists all images in a Bannerbear project.
List ProjectsLists all projects in a Bannerbear account.
List ScreenshotsLists all screenshots in a Bannerbear project.
List TemplatesThis action retrieves a list of all templates available in your Bannerbear project.
List Template SetsTool to list all template sets inside a project with pagination support.
List VideosThis action retrieves a list of all videos created in your Bannerbear account.
List Video TemplatesThis action retrieves a list of all video templates available in your Bannerbear project.
Update Template SetTool to update a template set by modifying its list of templates.

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.

Connecting Bannerbear via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Bannerbear) for even more tool search precision. It's secure and reliable.

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

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Bannerbear account
  • Basic knowledge of Python or TypeScript

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)

Install Composio library

pip install composio-core python-dotenv

Install the Composio Python library to create MCP sessions.

  • composio-core provides the core Composio functionality
  • python-dotenv loads environment variables from your .env file

Generate Composio MCP URL

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["bannerbear"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http bannerbear-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Create a script to generate a Composio MCP URL for Bannerbear. This URL will be used to connect Claude Code to Bannerbear.

What's happening:

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Bannerbear
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it

Run the script and copy the MCP URL

python generate_mcp_url.py

Run your Python script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output

Add Bannerbear MCP to Claude Code

bash
claude mcp add --transport http bannerbear-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (bannerbear-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

Verify the installation

bash
claude mcp list

Check that your Bannerbear MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your bannerbear-composio entry in the list
  • This confirms that Claude Code can now access Bannerbear tools

If everything is wired up, you should see your bannerbear-composio entry listed:

Claude Code MCP list showing the toolkit MCP server

Authenticate Bannerbear

The first time you try to use Bannerbear tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Bannerbear
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Bannerbear authorization flow
  • Return to the terminal and start using Bannerbear through Claude Code

Once authenticated, you can ask Claude Code to perform Bannerbear operations in natural language. For example:

  • "Merge multiple marketing PDFs into one file"
  • "List all video assets created this week"
  • "Get available fonts for Instagram templates"

Complete Code

Here's the complete code to get you started with Bannerbear and Claude Code:

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["bannerbear"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http bannerbear-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Conclusion

You've successfully integrated Bannerbear with Claude Code using Composio's MCP server. Now you can interact with Bannerbear directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Bannerbear operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Bannerbear operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

How to build Bannerbear MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Bannerbear MCP?

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.

Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude Code 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.

Can I manage the permissions and scopes for Bannerbear while using Tool Router?

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.

How safe is my data with Composio Tool Router?

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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.