How to integrate Docker hub 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

Docker hub logo
Google ADK logo
divider

Introduction

This guide walks you through connecting Docker hub to Google ADK using the Composio tool router. By the end, you'll have a working Docker hub agent that can create a new docker hub repository, add a member to your docker organization, delete an old image from a repository through natural language commands.

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

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

Also integrate Docker hub with

TL;DR

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

The Docker hub MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Docker Hub account. It provides structured and secure access to your container repositories and organizations, so your agent can perform actions like creating repositories, managing organization members, deleting images, setting up webhooks, and cleaning up tags on your behalf.

  • Repository and image management: Let your agent create new Docker Hub repositories, delete existing ones, and remove specific images or tags as needed.
  • Organization and team automation: Easily add members to organizations, create new Docker Hub organizations, or delete organizations and teams directly from your workflows.
  • Webhook configuration: Set up or remove repository webhooks to automate external integrations and keep your CI/CD pipelines in sync.
  • Tag and resource cleanup: Direct your agent to delete outdated tags or unused resources, helping you maintain a tidy container registry.
  • Secure role management: Invite users with specific roles to your organizations, ensuring the right access for collaborators and teams.

Supported Tools & Triggers

Tools
Add Organization MemberInvite a user to join a Docker Hub organization.
Create Docker Hub OrganizationCreate a new Docker Hub organization.
Create Docker Hub RepositoryCreates a new Docker Hub repository under the specified namespace.
Create Docker Hub WebhookCreate a webhook on a Docker Hub repository to receive notifications on image push events.
Delete Repository ImagesDelete one or more images from your Docker Hub namespace using the bulk delete API.
Delete Docker Hub OrganizationPermanently deletes a Docker Hub organization.
Delete Docker Hub RepositoryPermanently deletes a Docker Hub repository and all its images/tags.
Delete Repository TagPermanently delete a specific tag from a Docker Hub repository.
Delete Docker Hub TeamPermanently deletes a team from a Docker Hub organization.
Delete Docker Hub repository webhookDeletes a specific webhook from a Docker Hub repository.
Get Docker Hub ImageRetrieve details about a specific platform-specific image variant by its digest.
Get Docker Hub RepositoryRetrieves detailed information about a specific Docker Hub repository.
Get Docker Hub TagTool to retrieve details of a specific Docker Hub repository tag.
Get Docker Hub TeamRetrieve details of a specific team (group) within a Docker Hub organization.
Get Docker Hub WebhookRetrieves details of a specific Docker Hub webhook by its ID.
List Organization Access TokensTool to list all organization access tokens for a Docker Hub organization.
List Docker Hub OrganizationsList Docker Hub organizations that the authenticated user belongs to.
List Docker Hub Organization MembersLists members of a Docker Hub organization with their roles and details.
List Docker Hub RepositoriesTool to list repositories under a namespace.
List Team MembersList members of a Docker Hub team (group) within an organization.
List Organization TeamsList all teams (groups) within a Docker Hub organization.
List Docker Hub repository webhooksLists all webhooks configured for a Docker Hub repository.
Remove Organization MemberRemove a member from a Docker Hub organization.
Remove Team MemberRemove a user from a Docker Hub organization team (group).

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 Docker hub 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=["docker_hub"],
)

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 Docker hub 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 Docker hub 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=["docker_hub"],
)

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

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

Conclusion

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

Key takeaways:

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

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Docker hub MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Docker hub MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Docker hub MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Docker hub MCP with Claude Cowork

Codex logo

Codex

Use Docker hub MCP with Codex

OpenClaw logo

OpenClaw

Use Docker hub MCP with OpenClaw

Hermes logo

Hermes

Use Docker hub MCP with Hermes

CLI logo

CLI

Use Docker hub MCP with CLI

LangChain logo

LangChain

Use Docker hub MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Docker hub MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Docker hub MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Docker hub MCP with LlamaIndex

CrewAI logo

CrewAI

Use Docker hub MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Docker hub MCP?

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

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

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