DockerHub MCP Server
A production-ready Model Context Protocol (MCP) server that provides comprehensive DockerHub integration for AI assistants. This server enables AI assistants to search, analyze, and manage Docker images through standardized MCP tools.
README
DockerHub MCP Server
A production-ready Model Context Protocol (MCP) server that provides comprehensive DockerHub integration for AI assistants. This server enables AI assistants to search, analyze, and manage Docker images through standardized MCP tools.
π Features
Core Docker Hub Tools
- docker_search_images - Search Docker Hub for images
- docker_get_image_details - Get detailed information about an image
- docker_list_tags - List all tags for a repository
- docker_get_manifest - Retrieve image manifest
- docker_analyze_layers - Analyze image layers and sizes
- docker_compare_images - Compare two images (layers, sizes, base images)
- docker_get_dockerfile - Attempt to retrieve Dockerfile (when available)
- docker_get_stats - Get download statistics and star count
Advanced Tools
- docker_get_vulnerabilities - Fetch security scan results
- docker_get_image_history - Get image build history
- docker_track_base_updates - Check if base images have updates
- docker_estimate_pull_size - Calculate download size for an image
- docker_delete_tag - Delete a tag from your private repository
- docker_cache_info - Monitor cache performance and statistics
Key Capabilities
- β MCP Client Compatible - Works with Claude Desktop, Cursor, Cline, and other MCP clients
- β Private Registry Support - Access private DockerHub repositories with JWT authentication
- β Smart Caching System - Intelligent TTL-based caching with LRU eviction for optimal performance
- β Rate Limit Handling - Intelligent request management for DockerHub's API limits
- β Comprehensive Error Handling - Graceful fallbacks and clear error messages
- β TypeScript Implementation - Full type safety and excellent developer experience
- β Extensive Testing - 26 tests covering all functionality and edge cases
π οΈ Installation & Setup
Prerequisites
- Node.js 18+
- npm or yarn
- DockerHub account (for private repositories)
Quick Start
-
Clone the repository:
https://github.com/keshavjha123/DockerhubMCP.git cd DockerhubMCP -
Install dependencies:
npm install -
Configure environment variables:
cp .env.example .env # Edit .env with your DockerHub credentials -
Build the project:
npm run build -
Start the server:
npm start
βοΈ Configuration
Environment Variables
Create a .env file in the project root:
# DockerHub Authentication (for private repositories)
DOCKERHUB_USERNAME=your-username
DOCKERHUB_PASSWORD=your-password (same as personal access token)
DOCKERHUB_TOKEN=your-personal-access-token
# Optional: Custom API endpoints
DOCKERHUB_API_BASE=https://hub.docker.com/v2
DOCKER_REGISTRY_BASE=https://registry-1.docker.io
Authentication Methods
- Username/Password: Traditional login credentials
- Personal Access Token: Recommended for better security
- No Authentication: For public repositories only
π³ Docker Deployment
Quick Start with Docker
# One-command setup (Linux/macOS)
./docker-setup.sh
# One-command setup (Windows PowerShell)
.\docker-setup.ps1
Manual Docker Setup
Prerequisites: Make sure you're logged into Docker Hub to avoid rate limiting:
docker login
For Linux/macOS:
# 1. Configure environment (only if .env doesn't exist)
cp .env.example .env
# Edit .env with your DockerHub credentials
# 2. Build and run
docker-compose build
docker-compose up -d
# 3. Verify running
docker-compose ps
For Windows PowerShell:
# 1. Configure environment (only if .env doesn't exist)
Copy-Item .env.example .env
# Edit .env with your DockerHub credentials
# 2. Build and run
docker-compose build
docker-compose up -d
# 3. Verify running
docker-compose ps
β οΈ Note: Only run the first step if you don't already have a .env file with your credentials. The copy command will overwrite existing files.
β Docker Mode - TESTED & VERIFIED
The Docker deployment has been fully tested with:
- β All 16 MCP tools functioning
- β Private repository access working
- β Smart caching and rate limiting active
- β 26/26 tests passing
For detailed Docker deployment instructions, see Docker Deployment Guide.
π MCP Client Integration
Claude Desktop
Standard Installation:
{
"mcpServers": {
"dockerhub": {
"command": "node",
"args": ["/path/to/pixil-mcp-server/dist/index.js"],
"env": {
"DOCKERHUB_USERNAME": "your-user-name",
"DOCKERHUB_PASSWORD": "your-token-here",
"DOCKERHUB_TOKEN": "your-token-here"
}
}
}
}
To access a private repository, specify the full repository name in your Claude Desktop in your conversation (e.g., keshavmadhav12/keshavprivaterepo).
Alternatively, you can simply mention your DockerHub username to access your private repositories. Use the docker_list_repositories tool to retrieve the exact names of your private repositories.
Cursor/Cline
Configure the MCP server in your IDE settings to enable Docker image analysis capabilities.
π Usage Examples
Search for Images
Find the most popular Python images
Analyze Image Layers
Analyze the layers of nginx:latest and show optimization opportunities
Compare Images
Compare ubuntu:20.04 and ubuntu:22.04 and show the differences
Security Analysis
Check if my-org/my-app:latest has any critical vulnerabilities
Private Repository Management
List all tags for my-private-repo and delete outdated ones
π§ͺ Development & Testing
Development Mode
npm run dev
Run Tests
npm test
Linting
ESLint is configured to handle JavaScript files. TypeScript files are checked by the TypeScript compiler during npm run build.
To run linting:
npm run build # TypeScript checking
### Test with Private Repositories
```bash
# Configure your credentials in .env first
node local_test/mcp-bulk-client-private.mjs
π API Documentation
Tool Schemas
All tools use Zod schemas for validation:
// Example: docker_search_images
inputSchema: z.object({
query: z.string(),
limit: z.number().optional()
})
outputSchema: z.object({
images: z.array(z.object({
name: z.string(),
description: z.string(),
stars: z.number(),
pulls: z.number()
}))
})
Error Handling
All errors are returned in MCP-compliant format:
{
"error": {
"code": "DOCKER_API_ERROR",
"message": "Failed to fetch image details: 404 Not Found"
}
}
π Security Considerations
- Never commit credentials to version control
- Use personal access tokens instead of passwords
- Implement proper secret management in production
- Monitor API usage to prevent rate limit abuse
- Validate all inputs using Zod schemas
π Production Deployment
Environment Setup
# Production environment variables
NODE_ENV=production
DOCKERHUB_TOKEN=production-token
LOG_LEVEL=info
Process Management
# Using PM2
pm2 start dist/index.js --name dockerhub-mcp
# Using systemd
sudo systemctl enable dockerhub-mcp
sudo systemctl start dockerhub-mcp
Monitoring
- Monitor API rate limits
- Track response times
- Log authentication failures
- Alert on service disruptions
π€ Contributing
- Fork the repository
- Create a feature branch
- Make your changes
- Add tests for new functionality
- Run the test suite
- Submit a pull request
π Roadmap
Immediate Priorities
- [ ] Persistent caching with Redis (in-memory caching implemented)
- [ ] Rate limit visualization
- [ ] Batch operations
- [ ] Enhanced error recovery
Future Enhancements
- [ ] StreamableHTTP transport
- [ ] Multi-registry support
- [ ] Web dashboard
- [ ] Prometheus metrics
- [ ] Vulnerability severity filtering
- [ ] License compliance checking
οΏ½ Troubleshooting
Common Issues
Authentication Failures:
- Verify your DockerHub credentials
- Check token permissions and scopes
- Ensure 2FA is properly configured
Rate Limiting:
- Use authenticated requests when possible
- Built-in smart caching reduces API calls automatically
- Intelligent request queuing handles high-volume usage
Connection Issues:
- Verify network connectivity to DockerHub
- Check firewall and proxy settings
- Validate API endpoint URLs
Debug Mode
DEBUG=* npm start
π License
MIT License - see LICENSE file for details.
π Links
π¬ Support
- Create an issue for bug reports
- Start a discussion for feature requests
- Check the documentation for common questions
Made with β€οΈ for the Docker and AI community
π§° MCP Tools Implemented
This server implements the following MCP tools:
- docker_search_images: Search Docker Hub for images
- docker_get_image_details: Get detailed information about an image
- docker_list_tags: List all tags for a repository
- docker_get_manifest: Retrieve image manifest
- docker_analyze_layers: Analyze image layers and sizes
- docker_compare_images: Compare two images (layers, sizes, base images)
- docker_get_dockerfile: Attempt to retrieve Dockerfile (when available)
- docker_get_stats: Get download statistics and star count
Bonus Tools
- docker_get_vulnerabilities: Fetch security scan results (if available)
- docker_get_image_history: Get image build history
- docker_track_base_updates: Check if base images have updates
- docker_estimate_pull_size: Estimate the total download size for a DockerHub image tag (shows total bytes and layer breakdown).
π Tool API Reference
Each tool is available via the MCP protocol. Hereβs a quick summary of what each tool expects and returns:
docker_search_images
Input: { query: string }
Output: { results: any }
docker_get_image_details
Input: { namespace: string, repository: string }
Output: { details: any }
docker_list_tags
Input: { namespace: string, repository: string }
Output: { tags: string[] }
docker_get_manifest
Input: { namespace: string, repository: string, tag: string }
Output: { manifest: any }
docker_analyze_layers
Input: { namespace: string, repository: string, tag: string }
Output: { layers: any[], totalSize: number }
docker_compare_images
Input: { image1: { namespace, repository, tag }, image2: { namespace, repository, tag } }
Output: { comparison: any }
docker_get_dockerfile
Input: { namespace: string, repository: string, tag: string }
Output: { dockerfile: string | null }
docker_get_stats
Input: { namespace: string, repository: string }
Output: { pull_count: number, star_count: number }
π§βπ» Usage Examples
This server is designed to be used by MCP-compatible clients (like Claude Desktop, Cursor, Cline, etc). You can also write your own script to send MCP requests, or use the provided tests as examples.
π Troubleshooting
- Authentication errors? Double-check your
.envfile and DockerHub credentials. - Rate limits? DockerHub enforces strict rate limits. If you hit them, try again later or use authenticated requests.
- Tool not working as expected? Run
npm testto check for issues, and see the logs for error messages.
π Documentation
Setup and Configuration
- Quick Setup Guide - Step-by-step setup for Claude Desktop
- Authentication Guide - Complete authentication setup for private repositories
- Troubleshooting Guide - Common issues and solutions
API Reference
- API Documentation - Complete API reference for all 15 tools
- MCP Schema Explanation - Understanding MCP tool schemas
Technical Documentation
- Implementation Details - Architecture decisions and technical details
- Assignment Checklist - Development completion tracking
π Additional Resources
π License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.