How to integrate Api2pdf MCP with Google ADK

GET STARTED FOR FREE
Api2pdf logo
Google ADK logo
divider

Introduction

This guide walks you through connecting Api2pdf to Google ADK using the Composio tool router. By the end, you'll have a working Api2pdf agent that can merge monthly invoices into one pdf, extract specific pages from a large pdf, add custom header and footer to document through natural language commands.

This guide will help you understand how to give your Google ADK agent real control over a Api2pdf account through Composio's Api2pdf MCP server.

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

Also integrate Api2pdf with

TL;DR

Here's what you'll learn:
  • Get a Api2pdf account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Api2pdf
  • Build an agent that connects to Api2pdf through MCP
  • Interact with Api2pdf 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 Api2pdf MCP server, and what's possible with it?

The Api2pdf MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Api2pdf account. It provides structured and secure access to powerful PDF generation and manipulation features, so your agent can generate PDFs from HTML or URLs, merge or optimize documents, extract or reorder pages, and more—automatically and on your behalf.

  • PDF generation from web content: Instruct your agent to convert HTML or URLs into high-quality PDFs using engines like wkhtmltopdf or Headless Chrome.
  • Merge and optimize PDFs: Have your agent combine multiple PDFs into a single file or optimize existing documents to reduce file size without sacrificing quality.
  • Advanced PDF manipulation: Direct your agent to extract specific pages, reorder existing pages, or add custom headers and footers for consistent branding or page numbering.
  • Barcode and QR code generation: Let your agent instantly create barcode or QR code images from any text value, ready to embed in documents or use elsewhere.
  • Document conversion and preview: Ask your agent to convert PDFs to HTML with LibreOffice or generate thumbnail previews for quick visual reference.

Supported Tools & Triggers

Tools
Add Header FooterTool to add headers and footers to a pdf document.
Delete PDFTool to delete a previously generated pdf.
Extract PDF PagesTool to extract specific pages from a pdf document.
LibreOffice PDF to HTMLTool to convert a pdf document to html using libreoffice.
LibreOffice ThumbnailTool to generate a thumbnail image of a document using libreoffice.
Merge PDFsTool to merge multiple pdf documents into a single pdf.
Optimize PDFTool to optimize a pdf document to reduce file size while maintaining quality.
Reorder PDF PagesTool to reorder pages of a pdf document.
Generate Barcode or QR CodeTool to generate barcodes or qr codes using zebra crossing (zxing).

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 Api2pdf 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=["api2pdf"],
)

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 Api2pdf 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 Api2pdf 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=["api2pdf"],
)

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 Api2pdf operations."
    ),  
    tools=[composio_toolset],
)

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

Conclusion

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

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Api2pdf 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 Api2pdf MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Api2pdf MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Api2pdf MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Api2pdf MCP with Claude Code

Codex logo

Codex

Use Api2pdf MCP with Codex

OpenClaw logo

OpenClaw

Use Api2pdf MCP with OpenClaw

CLI logo

CLI

Use Api2pdf MCP with CLI

LangChain logo

LangChain

Use Api2pdf MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Api2pdf MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Api2pdf MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Api2pdf MCP with LlamaIndex

CrewAI logo

CrewAI

Use Api2pdf MCP with CrewAI

FAQ

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

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

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

Yes, absolutely. You can configure which Api2pdf 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 Api2pdf 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.

Book a call↗Get started for free