How to integrate Control d 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

Control d logo
Google ADK logo
divider

Introduction

This guide walks you through connecting Control d to Google ADK using the Composio tool router. By the end, you'll have a working Control d agent that can list all devices connected to your account, remove a device by its id, show known access ips for your network through natural language commands.

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

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

Also integrate Control d with

TL;DR

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

The Control d MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Control d account. It provides structured and secure access to your DNS filtering and device management environment, so your agent can perform actions like managing devices, enforcing policies, retrieving analytics, and monitoring network access on your behalf.

  • Device inventory management: Easily list all devices on your account or remove specific devices by their identifier for streamlined device control.
  • Profile and rule administration: Direct your agent to delete profiles, custom rules, or schedules—helping you maintain and enforce up-to-date network policies.
  • Network access monitoring: Retrieve a list of known access IPs to keep tabs on which endpoints are connecting to your network infrastructure.
  • Analytics endpoints discovery: Quickly fetch available analytics storage regions and endpoints so you can integrate and analyze DNS traffic data efficiently.
  • Organization details access: Have the agent fetch and present your organization's account details for easy reference and auditing.

Supported Tools & Triggers

Tools
Delete Device by IDPermanently delete a Control-D device/endpoint by its ID.
Delete ProfilePermanently deletes a Control D profile by its unique identifier (PK).
Delete Profile Rule by Rule IDDelete a custom DNS rule from a Control D profile by its rule identifier (hostname/domain).
Delete Rule from FolderDelete a custom DNS rule from a specific folder in a Control D profile.
Delete Profile ScheduleTool to delete a specific schedule within a profile.
List Known Access IPsList up to the latest 50 IP addresses that were used to query against a specific Device (resolver).
Get Analytics EndpointsTool to list analytics storage regions and their endpoints.
Get Analytics LevelsTool to retrieve available analytics log levels for Control D devices.
Get Billing PaymentsTool to retrieve billing history of all payments made.
Get Billing ProductsRetrieve all products currently activated on the Control D account.
Get DevicesLists all Control D devices (endpoints) associated with the account.
Get Device TypesList all allowed device types in Control D.
Get IPTool to retrieve the current IP address and datacenter information for the API request.
Get Network StatsTool to retrieve network stats on available services in different POPs (Points of Presence).
Get Organization MembersTool to view organization membership.
Get Organization DetailsTool to view the authenticated organization's details.
Get Sub-OrganizationsTool to view sub-organizations and their details.
Get ProfilesTool to list all profiles associated with the authenticated account.
Get Profile OptionsRetrieves all available configuration options for DNS profiles in Control D.
Get Profile by IDTool to retrieve details of a specific profile by its ID.
Get Profile AnalyticsRetrieve analytics data for a Control D profile.
Get Profile Analytics LogsRetrieves DNS query activity logs for a specific Control D profile.
Get Analytics Log EntryTool to retrieve a specific analytics log entry by its ID.
Get Profile Analytics SummaryTool to fetch a summary of analytics data for a given profile.
Get Profile Analytics Top DomainsTool to fetch top domains accessed within a specific profile.
Get Profile Top ServicesTool to fetch top services accessed within a profile.
Get Profile FiltersList all native (Control D curated) filters for a profile and their current states.
List External Filters for ProfileTool to list third-party filters for a specific profile.
Get Profile FoldersList all rule folders (groups) within a Control D profile.
List Custom DNS Rules for ProfileRetrieve custom DNS rules for a Control D profile.
Get Specific Rule in FolderTool to retrieve a specific rule within a folder by its ID.
Get Profile SchedulesTool to list schedules associated with a specific profile.
Get Profile ScheduleTool to retrieve a specific schedule by its ID within a profile.
Get Profile ServicesTool to list services associated with a specific profile.
Get ProxiesTool to retrieve the list of usable proxy locations that traffic can be redirected through.
Get Service CategoriesList all available service categories in Control D.
List Services by CategoryRetrieves all services within a specific ControlD service category.
Get UsersRetrieve the authenticated user's account information from Control D.
Create DeviceCreate a new device (DNS endpoint) in Control D.
Create ProfileCreate a new blank profile or clone an existing one.
Create Custom DNS RuleCreate custom DNS rules for a profile to control domain resolution.
Create Custom Rules in Profile FolderTool to create custom rules within a specific folder for a profile.
Create Profile ScheduleCreate a new time-based schedule within a Control D profile.
Modify DeviceModify an existing Control D device's settings.
Modify OrganizationModify organization settings such as name, contact details, website, and device limits.
Modify ProfileModify an existing profile by its ID.
Bulk Update Profile FiltersTool to bulk update filters on a specific profile.
Update External Filters for ProfileTool to update external filters for a specific profile.
Modify Profile FilterModify the enabled state of a specific native filter on a profile.
Modify Custom Rule for ProfileModify an existing custom DNS rule for a profile in Control D.
Update Custom Rule by Rule IDTool to update an existing custom rule by its ID.
Move Profile Rule to FolderTool to move a specific custom rule into a different folder.
Update Profile ScheduleTool to update a specific schedule within a profile.
Modify Service for ProfileTool to modify a specific service rule for a profile.

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 Control d 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=["control_d"],
)

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 Control d 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 Control d 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=["control_d"],
)

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

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

Conclusion

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

Key takeaways:

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

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Control d MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Control d MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Control d MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Control d MCP with Claude Cowork

Codex logo

Codex

Use Control d MCP with Codex

OpenClaw logo

OpenClaw

Use Control d MCP with OpenClaw

Hermes logo

Hermes

Use Control d MCP with Hermes

CLI logo

CLI

Use Control d MCP with CLI

LangChain logo

LangChain

Use Control d MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Control d MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Control d MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Control d MCP with LlamaIndex

CrewAI logo

CrewAI

Use Control d MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Control d MCP?

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

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

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