# How to integrate Tomba MCP with Google ADK ```json { "title": "How to integrate Tomba MCP with Google ADK", "toolkit": "Tomba", "toolkit_slug": "tomba", "framework": "Google ADK", "framework_slug": "google-adk", "url": "https://composio.dev/toolkits/tomba/framework/google-adk", "markdown_url": "https://composio.dev/toolkits/tomba/framework/google-adk.md", "updated_at": "2026-05-12T10:28:53.541Z" } ``` ## Introduction This guide walks you through connecting Tomba to Google ADK using the Composio tool router. By the end, you'll have a working Tomba agent that can find all leads from example.com domain, check if this email is disposable, list your current api keys in tomba through natural language commands. This guide will help you understand how to give your Google ADK agent real control over a Tomba account through Composio's Tomba MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Tomba with - [OpenAI Agents SDK](https://composio.dev/toolkits/tomba/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/tomba/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/tomba/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/tomba/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/tomba/framework/codex) - [OpenClaw](https://composio.dev/toolkits/tomba/framework/openclaw) - [Hermes](https://composio.dev/toolkits/tomba/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/tomba/framework/cli) - [LangChain](https://composio.dev/toolkits/tomba/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/tomba/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/tomba/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/tomba/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/tomba/framework/crew-ai) ## TL;DR Here's what you'll learn: - Get a Tomba account set up and connected to Composio - Install the Google ADK and Composio packages - Create a Composio Tool Router session for Tomba - Build an agent that connects to Tomba through MCP - Interact with Tomba 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 Tomba MCP server, and what's possible with it? The Tomba MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Tomba account. It provides structured and secure access to your B2B email finding, lead management, and account configuration tools, so your agent can perform actions like discovering leads, managing lists, validating domains, and monitoring account usage on your behalf. - Lead discovery and enrichment: Ask your agent to list available lead attributes or add new leads directly into your Tomba account for streamlined outreach. - Lead list management: Effortlessly retrieve, update, or delete lead lists, helping you stay organized and keep your data current. - Domain validation and status checks: Have your agent check if a domain is webmail or disposable to ensure better deliverability and lead quality. - API key and account management: Direct your agent to list, create, or revoke API keys, and review usage statistics to keep your Tomba integration secure and efficient. - Usage monitoring and reporting: Let your agent fetch up-to-date API usage statistics, keeping you informed about your plan limits and consumption. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `TOMBA_ATTRIBUTES_LIST` | List Lead Attributes | Retrieves all custom lead attributes defined in your Tomba account. Use this action to discover the available attributes that can be used when creating or updating leads. Returns attribute metadata including name, identifier, type, and timestamps. No input parameters required. | | `TOMBA_DOMAIN_STATUS` | Domain Status | Tool to check if a domain is webmail or disposable. Use when validating email deliverability constraints. | | `TOMBA_KEYS_DELETE` | Delete API Key by ID | Tool to delete an API key by its numeric ID. Use when you need to permanently revoke an API key before its expiration. Note: You can get the numeric key ID from the TOMBA_KEYS_LIST action. | | `TOMBA_KEYS_LIST` | List API Keys | Tool to list all API keys. Use when you want to retrieve information about your existing Tomba API keys. | | `TOMBA_LEADS_CREATE` | Create Lead | Create a new lead in Tomba's lead database. Use this to store contact information for a person you want to track. Returns the unique ID of the created lead. Required fields: first_name, email. All other fields are optional. | | `TOMBA_LEADS_LIST` | List Leads | Tool to list all leads. Use when you need to retrieve and paginate your leads list. | | `TOMBA_LISTS_DELETE` | Delete Leads List by ID | Tool to delete a leads list by ID. Use when you need to permanently remove a list after confirming its ID. | | `TOMBA_LISTS_LIST` | List Lead Lists | Tool to list all lead lists. Use when you need to retrieve and paginate your lead lists. | | `TOMBA_LISTS_UPDATE` | Update Leads List | Tool to update a leads list's name by ID. Use when renaming an existing list after obtaining its ID. | | `TOMBA_USAGE_STATS` | Get Usage Statistics | Tool to get API usage statistics. Use when you need to monitor account usage and avoid hitting limits. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Tomba MCP server is an implementation of the Model Context Protocol that connects your AI agent to Tomba. It provides structured and secure access so your agent can perform Tomba operations on your behalf through a secure, permission-based interface. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. 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 ### 1. Getting API Keys for Google and Composio Google API Key - Go to [Google AI Studio](https://aistudio.google.com/app/apikey) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - 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. ### 2. Install dependencies Inside your virtual environment, install the required packages. What's happening: - google-adk is Google's Agents Development Kit - composio connects your agent to Tomba via MCP - python-dotenv loads environment variables ```bash pip install google-adk composio python-dotenv ``` ### 3. Set up ADK project Set up a new Google ADK project. What's happening: - This creates an agent folder with a root agent file and .env file ```bash adk create my_agent ``` ### 4. Set environment variables 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 ```bash GOOGLE_API_KEY=your-google-api-key COMPOSIO_API_KEY=your-composio-api-key COMPOSIO_USER_ID=your-user-id-or-email ``` ### 5. Import modules and validate 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 ```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.") ``` ### 6. Create Composio client and Tool Router session 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 ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=COMPOSIO_USER_ID, toolkits=["tomba"], ) COMPOSIO_MCP_URL = composio_session.mcp.url, print(f"Composio MCP URL: {COMPOSIO_MCP_URL}") ``` ### 7. Set up the McpToolset and create the Agent 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 ```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 Tomba operations." ), tools=[composio_toolset], ) print("\nAgent setup complete. You can now run this agent directly ;)") ``` ### 8. Run the agent 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 ```bash # Run in CLI mode adk run my_agent # Or run in web UI mode adk web ``` ## Complete Code ```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=["tomba"], ) 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 Tomba operations." ), tools=[composio_toolset], ) print("\nAgent setup complete. You can now run this agent directly ;)") ``` ## Conclusion You've successfully integrated Tomba with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Tomba using natural language commands. Key takeaways: - The Tool Router approach dynamically routes requests to the appropriate Tomba 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 Tomba MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/tomba/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/tomba/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/tomba/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/tomba/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/tomba/framework/codex) - [OpenClaw](https://composio.dev/toolkits/tomba/framework/openclaw) - [Hermes](https://composio.dev/toolkits/tomba/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/tomba/framework/cli) - [LangChain](https://composio.dev/toolkits/tomba/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/tomba/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/tomba/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/tomba/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/tomba/framework/crew-ai) ## Related Toolkits - [Aeroleads](https://composio.dev/toolkits/aeroleads) - Aeroleads is a B2B lead generation platform for finding business emails and phone numbers. Grow your sales pipeline faster with powerful prospecting tools. - [Autobound](https://composio.dev/toolkits/autobound) - Autobound is an AI-powered sales engagement platform that crafts hyper-personalized outreach and insights. It helps sales teams boost response rates and close more deals through tailored content and recommendations. - [Better proposals](https://composio.dev/toolkits/better_proposals) - Better Proposals is a web-based tool for crafting and sending professional proposals. It helps teams impress clients and close deals faster with slick, easy-to-use templates. - [Bidsketch](https://composio.dev/toolkits/bidsketch) - Bidsketch is a proposal software that helps businesses create professional proposals quickly and efficiently. It streamlines the proposal process, saving time while boosting client win rates. - [Bolna](https://composio.dev/toolkits/bolna) - Bolna is an AI platform for building conversational voice agents. It helps businesses automate support and streamline interactions through natural, voice-powered conversations. - [Botsonic](https://composio.dev/toolkits/botsonic) - Botsonic is a no-code AI chatbot builder for easily creating and deploying chatbots to your website. It empowers businesses to offer conversational experiences without writing code. - [Botstar](https://composio.dev/toolkits/botstar) - BotStar is a comprehensive chatbot platform for designing, developing, and training chatbots visually on Messenger and websites. It helps businesses automate conversations and customer interactions without coding. - [Callerapi](https://composio.dev/toolkits/callerapi) - CallerAPI is a white-label caller identification platform for branded caller ID and fraud prevention. It helps businesses boost customer trust while stopping spam, fraud, and robocalls. - [Callingly](https://composio.dev/toolkits/callingly) - Callingly is a lead response management platform that automates immediate call and text follow-ups with new leads. It helps sales teams boost response speed and close more deals by connecting seamlessly with CRMs and lead sources. - [Callpage](https://composio.dev/toolkits/callpage) - Callpage is a lead capture platform that lets businesses instantly connect with website visitors via callback. It boosts lead generation and increases your sales conversion rates. - [Clearout](https://composio.dev/toolkits/clearout) - Clearout is an AI-powered service for verifying, finding, and enriching email addresses. It boosts deliverability and helps you discover high-quality leads effortlessly. - [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time. - [Convolo ai](https://composio.dev/toolkits/convolo_ai) - Convolo ai is an AI-powered communications platform for sales teams. It accelerates lead response and improves conversion rates by automating calls and integrating workflows. - [Delighted](https://composio.dev/toolkits/delighted) - Delighted is a customer feedback platform based on the Net Promoter System®. It helps you quickly gather, track, and act on customer sentiment. - [Docsbot ai](https://composio.dev/toolkits/docsbot_ai) - Docsbot ai is a platform that lets you build custom AI chatbots trained on your documentation. It automates customer support and content generation, saving time and improving response quality. - [Emelia](https://composio.dev/toolkits/emelia) - Emelia is an all-in-one B2B prospecting platform for cold-email, LinkedIn outreach, and prospect research. It streamlines outbound campaigns so you can find, engage, and warm up leads faster. - [Findymail](https://composio.dev/toolkits/findymail) - Findymail is a B2B data provider offering verified email and phone contacts for sales prospecting. Enhance outreach with automated exports, email verification, and CRM enrichment. - [Freshdesk](https://composio.dev/toolkits/freshdesk) - Freshdesk is customer support software with ticketing and automation tools. It helps teams streamline helpdesk operations for faster, better customer support. - [Fullenrich](https://composio.dev/toolkits/fullenrich) - FullEnrich is a B2B contact enrichment platform that aggregates emails and phone numbers from 15+ data vendors. Instantly find and verify lead contact data to boost your outreach. - [Gatherup](https://composio.dev/toolkits/gatherup) - GatherUp is a customer feedback and online review management platform. It helps businesses boost their reputation by streamlining how they collect and manage customer feedback. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Tomba MCP? With a standalone Tomba MCP server, the agents and LLMs can only access a fixed set of Tomba tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Tomba 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 Tomba tools. ### Can I manage the permissions and scopes for Tomba while using Tool Router? Yes, absolutely. You can configure which Tomba 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 Tomba data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)