How to integrate Mx toolbox MCP with Google ADK

This guide walks you through connecting Mx toolbox to Google ADK using the Composio tool router. By the end, you'll have a working Mx toolbox agent that can check if your domain is blacklisted, get current mx records for example.com, run a ping test on our mail server through natural language commands. This guide will help you understand how to give your Google ADK agent real control over a Mx toolbox account through Composio's Mx toolbox MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Mx toolbox logoMx toolbox
Api Key

MxToolbox is a network diagnostic and monitoring service with advanced DNS, blacklist, and email health tools. It helps IT teams quickly troubleshoot and ensure reliable email and network performance.

13 Tools

Introduction

This guide walks you through connecting Mx toolbox to Google ADK using the Composio tool router. By the end, you'll have a working Mx toolbox agent that can check if your domain is blacklisted, get current mx records for example.com, run a ping test on our mail server through natural language commands.

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

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

Also integrate Mx toolbox with

TL;DR

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

The Mx toolbox MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Mx toolbox account. It provides structured and secure access to network diagnostic and email health tools, so your agent can perform actions like DNS lookups, blacklist checks, email authentication analysis, and connectivity testing on your behalf.

  • Automated DNS and MX record lookups: Instantly retrieve DNS, MX, DKIM, DMARC, and MTA-STS records for any domain to verify configuration and troubleshoot email delivery issues.
  • Blacklist monitoring and alerting: Check if your domain or IP is listed on common blacklists, helping you stay ahead of email deliverability problems and security risks.
  • Email authentication validation: Validate BIMI, DKIM, and DMARC records to ensure your domain's outgoing emails are properly authenticated and protected against spoofing.
  • Network and SMTP diagnostics: Run ping, HTTP, and SMTP lookups to diagnose connectivity issues, measure latency, or assess mail server responsiveness—no manual testing required.
  • Brand and security checks: Use BIMI and MTA-STS lookups to confirm your brand indicators and mail transport security policies are correctly published and compliant.

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

Step by step09 STEPS
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
2

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

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 Mx toolbox via MCP
  • python-dotenv loads environment variables
4

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
5

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
6

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
7

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

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
8

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 Mx toolbox 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
9

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 Mx toolbox 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=["mx_toolbox"],
)

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

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

Conclusion

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

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Mx toolbox 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.

TOOLS

Supported Tools

Every Mx toolbox action and event your agent gets out of the box.

Lookup BIMI Record

Retrieves BIMI (Brand Indicators for Message Identification) record and diagnostic information for a domain.

Lookup Blacklist

Tool to perform a blacklist check on a domain or IP.

Lookup DKIM Record

Tool to retrieve DKIM (DomainKeys Identified Mail) records for a domain.

Lookup DMARC Record

Retrieves DMARC (Domain-based Message Authentication, Reporting & Conformance) records for a domain and performs validation checks.

Lookup DNS Records

Performs comprehensive DNS health check and retrieves name server records for a domain.

HTTP Lookup

Tool to perform an HTTP test on a domain.

Lookup MTA-STS Record

Tool to lookup MTA-STS record for a domain.

Lookup MX Records

Retrieves MX (Mail Exchange) records for a domain.

Ping Lookup

Performs a ping test to check network connectivity and measure round-trip time to a domain or IP address.

SMTP Lookup

Tool to perform an SMTP connectivity test on a domain.

Lookup SPF Record

Tool to retrieve SPF records for a specified domain.

Monitor Status

Retrieves the current status of all monitors configured in the MX Toolbox account.

Check Usage

Retrieve API usage statistics for DNS and network lookups.

FAQ

Frequently asked questions

With a standalone Mx toolbox MCP server, the agents and LLMs can only access a fixed set of Mx toolbox tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Mx toolbox and many other apps based on the task at hand, all through a single MCP endpoint.

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 Mx toolbox tools.

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

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 Mx toolbox data and credentials are handled as safely as possible.

Start with Mx toolbox.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Mx toolbox tool your agent needs.Free to start.

Start building