How to integrate Docker hub MCP with Codex

GET STARTED FOR FREE
Docker hub logo
Codex logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Docker hub MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

Also integrate Docker hub with

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Docker hub MCP in Codex

Run the setup command

Run this command in your terminal to add the Composio MCP server to Codex.

Terminal

It will initiate the authentication in a browser window, authorize Codex to access your Composio account.

Composio authentication page

(Optional) Authenticate with OAuth

To authenticate manually, run the login command to open a browser window and authorize Codex to access your Composio account.

bash
codex mcp login composio

Verify the connection

Run codex mcp list to confirm Composio appears as a registered MCP server.

bash
codex mcp list

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
  2. Fill the header and Key fields with { "x-consumer-api-key" = "ck_*******" }.
  3. The Key is the Composio API key, that you can find on connect.composio.dev
  4. Click on Authenticate and authorize Codex to your Composio account and you're all set.
Codex App MCP setup
  1. Restart and verify if it's there in .codex/config.toml
bash
[mcp_servers.composio]
url = "https://connect.composio.dev/mcp"
http_headers = { "x-consumer-api-key" = "ck_*******" }

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 MemberTool to send an invitation for a user to join a Docker Hub organization.
Create Docker Hub OrganizationTool to create a Docker Hub organization.
Create Docker Hub RepositoryTool to create a Docker Hub repository under a namespace.
Create Docker Hub WebhookTool to create a webhook on a Docker Hub repository.
Delete Repository ImageTool to delete a specific image within a Docker Hub repository.
Delete Docker Hub OrganizationTool to delete a specific Docker Hub organization.
Delete Docker Hub RepositoryTool to delete a specific Docker Hub repository.
Delete Repository TagTool to delete a specific tag from a Docker Hub repository.
Delete Docker Hub TeamTool to delete a specific team from an organization.
Delete Docker Hub repository webhookTool to delete a specific webhook from a repository.
Get Docker Hub ImageTool to retrieve detailed information about a specific image within a Docker Hub repository.
Get Organization DetailsTool to retrieve details of a specific organization namespace.
Get Docker Hub RepositoryTool to retrieve details of a specific Docker Hub repository.
Get Docker Hub TagTool to retrieve details of a specific Docker Hub repository tag.
Get Docker Hub TeamTool to retrieve a specific Docker Hub team.
Get Docker Hub WebhookTool to retrieve details of a specific Docker Hub webhook.
List Repository ImagesTool to list image variants for a specific Docker Hub repository.
List Docker Hub OrganizationsTool to list organizations (namespaces) for the authenticated user.
List Docker Hub Organization MembersTool to list members of a Docker Hub organization.
List Docker Hub RepositoriesTool to list repositories under a namespace.
List Repository TagsTool to list tags for a Docker Hub repository.
List Team MembersTool to list members of a Docker Hub team.
List Organization TeamsTool to list teams in a specific organization.
List Docker Hub repository webhooksTool to list webhooks for a Docker Hub repository.
Remove Organization MemberTool to remove a user from a Docker Hub organization.
Remove Team MemberTool to remove a user from a Docker Hub team.

Conclusion

You've successfully integrated Docker hub with Codex using Composio's MCP server. Now you can interact with Docker hub directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Docker hub operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Docker hub operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

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

OpenClaw logo

OpenClaw

Use Docker hub MCP with OpenClaw

CLI logo

CLI

Use Docker hub MCP with CLI

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

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 Codex?

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

Book a call↗Get started for free