How to integrate Bannerbear MCP with Google ADK

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Bannerbear logo
Google ADK logo
divider

Introduction

This guide walks you through connecting Bannerbear to Google ADK 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 Google ADK 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 a Bannerbear account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Bannerbear
  • Build an agent that connects to Bannerbear through MCP
  • Interact with Bannerbear using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

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.

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 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

Prerequisites

Before starting, make sure you have:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Bannerbear via MCP
  • python-dotenv loads environment variables

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")
What's happening:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

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

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Bannerbear operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.

What's happening:

  • adk run runs the agent in CLI mode
  • adk web . opens a web UI for interactive testing

Complete Code

Here's the complete code to get you started with Bannerbear and Google ADK:

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

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

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Bannerbear operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated Bannerbear with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Bannerbear using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Bannerbear tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

How to build Bannerbear MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Bannerbear MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Bannerbear MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Bannerbear MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Bannerbear MCP with Claude Cowork

Codex logo

Codex

Use Bannerbear MCP with Codex

OpenClaw logo

OpenClaw

Use Bannerbear MCP with OpenClaw

Hermes logo

Hermes

Use Bannerbear MCP with Hermes

CLI logo

CLI

Use Bannerbear MCP with CLI

LangChain logo

LangChain

Use Bannerbear MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Bannerbear MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Bannerbear MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Bannerbear MCP with LlamaIndex

CrewAI logo

CrewAI

Use Bannerbear MCP with CrewAI

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 Google ADK?

Yes, you can. Google ADK 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.

Get started for freeGet a demo↗