SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Docker hub MCP with CrewAI

Connect CrewAI to Docker hub MCP. Create a new docker hub repository, add a member to your docker organization, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Docker hub logoDocker hub
Api Key

Docker Hub is a cloud-based registry for finding and sharing container images. It simplifies container collaboration and deployment for individuals and teams.

24 Tools

Introduction

This guide walks you through connecting Docker hub to CrewAI using the Composio tool router. By the end, you'll have a working Docker hub agent that can create and delete repositories, inspect images and tags, manage organizations and teams, and set up webhooks through natural language commands.

This guide will help you understand how to give your CrewAI 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

Claude CodeClaude CoworkOpenAI Agents SDKClaude Agent SDKGrok BotCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • Get a Composio API key and configure your Docker hub connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Docker hub
  • Build a conversational loop where your agent can execute Docker hub operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

  • Agent Roles: Define specialized agents with specific goals and backstories
  • Task Management: Create tasks with clear descriptions and expected outputs
  • Crew Orchestration: Combine agents and tasks into collaborative workflows
  • MCP Integration: Connect to external tools through Model Context Protocol

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.

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 step08 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Docker hub connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

bash
pip install composio crewai crewai-tools[mcp] python-dotenv
What's happening:
  • composio connects your agent to Docker hub via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] includes MCP helpers
  • python-dotenv loads environment variables from .env
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID scopes the session to your account
  • OPENAI_API_KEY lets CrewAI use your chosen OpenAI model
5

Import dependencies

python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • CrewAI classes define agents and tasks, and run the workflow
  • MCPServerHTTP connects the agent to an MCP endpoint
  • Composio will give you a short lived Docker hub MCP URL
6

Create a Composio Tool Router session for Docker hub

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["docker_hub"])

url = session.mcp.url
What's happening:
  • You create a Docker hub only session through Composio
  • Composio returns an MCP HTTP URL that exposes Docker hub tools
7

Initialize the MCP Server

python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
What's Happening:
  • Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
  • MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
  • Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
  • Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
  • Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
8

Create a CLI Chatloop and define the Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
What's Happening:
  • Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
  • Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
  • Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
  • Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
  • Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
  • Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

Here's the complete code to get you started with Docker hub and CrewAI:

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

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.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["docker_hub"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Docker hub through Composio's Tool Router. The agent can perform Docker hub operations through natural language commands.

Next steps:

  • Add role-specific instructions to customize agent behavior
  • Plug in more toolkits for multi-app workflows
  • Chain tasks for complex multi-step operations
TOOLS

Supported Tools

Every Docker hub action and event your agent gets out of the box.

Add Organization Member

Invite a user to join a Docker Hub organization.

Create Docker Hub Organization

Create a new Docker Hub organization.

Create Docker Hub Repository

Creates a new Docker Hub repository under the specified namespace.

Create Docker Hub Webhook

Create a webhook on a Docker Hub repository for image push notifications, then add its hook URL; repository admin permissions are required.

Delete Repository Images

Delete up to 100 image manifests from a Docker Hub namespace by repository and SHA256 digest, or use a dry run to validate the request without deleting.

Delete Docker Hub Organization

Permanently deletes a Docker Hub organization.

Delete Docker Hub Repository

Permanently delete a Docker Hub repository and its images, tags, and metadata.

Delete Repository Tag

Permanently delete a specific tag from a Docker Hub repository.

Delete Docker Hub Team

Permanently deletes a team from a Docker Hub organization.

Delete Docker Hub repository webhook

Deletes a specific webhook from a Docker Hub repository.

Get Docker Hub Image

Retrieve a platform-specific image variant by digest by searching repository tags.

Get Docker Hub Repository

Retrieve detailed metadata for a Docker Hub repository, including available description, counts, permissions, and configuration.

Get Docker Hub Tag

Retrieve details of a specific Docker Hub repository tag by namespace, repository, and tag name.

Get Docker Hub Team

Retrieve details of a specific team (group) within a Docker Hub organization.

Get Docker Hub Webhook

Retrieves details of a specific Docker Hub webhook by its ID.

List Organization Access Tokens

List a page of organization access tokens for a Docker Hub organization, with pagination.

List Docker Hub Organizations

List Docker Hub organizations associated with the authenticated user, with available organization details in paginated results.

List Docker Hub Organization Members

List members of a Docker Hub organization with available roles and details, using paginated results.

List Docker Hub Repositories

List repositories under a Docker Hub namespace with optional filtering and pagination.

List Team Members

List members of a Docker Hub team (group) within an organization, returning paginated user details.

List Organization Teams

List all teams (groups) within a Docker Hub organization.

List Docker Hub repository webhooks

List webhooks configured for a Docker Hub repository, returning paginated configuration details.

Remove Organization Member

Remove a member from a Docker Hub organization.

Remove Team Member

Remove a user from a Docker Hub organization team (group), revoking that team membership.

FRAMEWORKS

How to build Docker hub MCP Agent with another framework

Claude Code logo

Claude Code

Use Docker hub MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Docker hub MCP with Claude Cowork

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

Grok Bot logo

Grok Bot

Use Docker hub MCP with Grok Bot

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

Atomic Agent logo

Atomic Agent

Use Docker hub MCP with Atomic Agent

Google ADK logo

Google ADK

Use Docker hub MCP with Google ADK

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

Pydantic AI logo

Pydantic AI

Use Docker hub MCP with Pydantic AI

AutoGen logo

AutoGen

Use Docker hub MCP with AutoGen

FAQ

Frequently asked questions

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.

Yes, you can. CrewAI 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.

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.

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.

Start with Docker hub.It takes 30 seconds.

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

Start building