How to integrate Proabono MCP with Google ADK

Framework Integration Gradient
Proabono Logo
Google ADK Logo
divider

Introduction

This guide walks you through connecting Proabono to Google ADK using the Composio tool router. By the end, you'll have a working Proabono agent that can list all active subscriptions for a customer, create a new subscription for acme corp, show overdue invoices for a specific customer through natural language commands.

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

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

TL;DR

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

The Proabono MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Proabono account. It provides structured and secure access so your agent can perform Proabono operations on your behalf.

Supported Tools & Triggers

Tools
Anonymize CustomerTool to anonymize a customer for GDPR compliance.
Bill CustomerTool to trigger billing for a customer.
Create CustomerTool to create or declare a customer in ProAbono via the Backoffice API.
Create FeatureTool to create a new feature in ProAbono via the Backoffice API.
Delete CustomerTool to delete a customer from ProAbono by ID.
Delete OfferTool to delete an offer from ProAbono by ID.
Delete Pricing TableTool to delete a pricing table from ProAbono by its ID.
Delete Pricing Table OfferTool to delete a pricing table offer via the ProAbono Backoffice API.
Delete Subscription DiscountTool to delete a subscription discount via the Backoffice API.
Enable WebhookTool to enable a webhook in ProAbono via the Notification API.
Get Customer by IDTool to retrieve a single customer by ID from ProAbono Backoffice API.
Get Customer Billing AddressTool to retrieve a customer's billing address via the Backoffice API.
Get Customer Billing Address by ReferenceTool to retrieve the billing address for a customer by reference from ProAbono API.
Get Customer by ReferenceTool to retrieve a customer by their reference identifier from ProAbono API.
Get Customer Payment SettingsTool to retrieve customer payment settings via the Backoffice API.
Get DiscountTool to retrieve a discount by ID via the Backoffice API.
Get Feature by IDTool to retrieve a feature by ID from ProAbono Backoffice API.
Get Feature by ReferenceTool to retrieve a single feature by its reference from ProAbono API.
Get InvoiceTool to retrieve a specific invoice or credit note by ID from ProAbono.
Get Offer by IDTool to retrieve a single offer by its ID from ProAbono Backoffice API.
Get Subscription by Customer ReferenceTool to retrieve a subscription by customer reference from ProAbono.
Get Subscription Creation QuoteTool to get a pricing quote for creating a new subscription without actually creating it.
Get Usage RecordTool to retrieve a single usage record for a specific feature and customer combination from ProAbono.
Get Usages for CustomerTool to retrieve usage data for customers from ProAbono.
Invalidate CustomerTool to invalidate a customer by their reference.
Invalidate Customer by IDTool to invalidate a customer by their ProAbono internal ID.
List Balance LinesTool to list all balance lines from ProAbono.
List BusinessesTool to list all businesses from ProAbono via the Backoffice API.
List Business LocalizationTool to list localization entries by business from ProAbono via the HostedPages API.
List Customer MovesTool to list all customer balance moves via the ProAbono Backoffice API.
List CustomersTool to list all customers from ProAbono via the Backoffice API.
List Customers by FeatureTool to list customers that have access to a specific feature via the ProAbono API.
List DiscountsTool to list all discounts from ProAbono's Backoffice API.
List FeaturesTool to list all features via the ProAbono Backoffice API.
List Features (V1)Tool to retrieve all features from ProAbono API using the /v1/Features endpoint.
List Gateway AccountsTool to list payment gateway accounts from ProAbono Backoffice API.
List Gateway PermissionsTool to list gateway permissions from ProAbono API.
List Gateway RequestsTool to list gateway requests from ProAbono.
List Gateway TransactionsTool to list gateway transactions from ProAbono.
List Invoice LinesTool to list all invoice lines from ProAbono via the Backoffice API.
List Invoices and Credit NotesTool to list all invoices and credit notes from ProAbono Backoffice API.
List Invoices by Customer ReferenceTool to list invoices for a specific customer by their reference identifier from ProAbono API.
List OffersTool to list all subscription offers (plans) from ProAbono Backoffice API.
List PaymentsTool to list all payments from ProAbono Backoffice API.
List Pricing Table OffersTool to list all pricing table offers via the ProAbono Backoffice API.
List Pricing TablesTool to list all pricing tables from ProAbono Backoffice API.
List Segment LocalizationsTool to list localization entries by segment from ProAbono Backoffice API.
List SegmentsTool to list all segments from ProAbono via the Backoffice API.
List Subscription DiscountsTool to list all subscription discounts via the ProAbono Backoffice API.
List Subscription FeaturesTool to list all subscription features via the ProAbono Backoffice API.
List Subscription PeriodsTool to list all subscription periods (billing cycles) from ProAbono Backoffice API.
List SubscriptionsTool to list all subscriptions from ProAbono via the Backoffice API.
List Subscriptions (V1)Tool to retrieve all subscriptions from ProAbono API using the /v1/Subscriptions endpoint.
List Tax Profile ExceptionsTool to list tax profile exceptions from ProAbono Organization API.
List Tax ProfilesTool to list all tax profiles from ProAbono via the Backoffice API.
List Upgrade OffersTool to retrieve offers available to upgrade an existing customer subscription.
List Webhook NotificationsTool to list webhook notifications from ProAbono via the Notification API.
List WebhooksTool to list webhooks from ProAbono Notification API.
Quote Balance Line CreationTool to get a pricing quote for creating a balance line (one-time charge or credit).
Revoke Customer Portal LinksTool to revoke encrypted customer portal links and generate new ones in ProAbono.
Update Business Billing AddressTool to update business billing address via the Backoffice API.
Update CustomerTool to update an existing customer in ProAbono via the Backoffice API.
Update Customer Billing AddressTool to update the billing address for a customer in ProAbono via the API.
Update Customer Payment SettingsTool to update payment settings for a specific customer in ProAbono.
Update Customer Shipping AddressTool to update customer shipping address via the Backoffice API.
Update FeatureTool to update an existing feature in ProAbono via the Backoffice API.
Update Tax ProfilesTool to update an existing tax profile in ProAbono via the Backoffice API.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router 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 Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router 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 Proabono 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=["proabono"],
)

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 Proabono 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 Proabono 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=["proabono"],
)

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

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

Conclusion

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

Key takeaways:

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

FAQ

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

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

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

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