Docker Forge MCP
Generate Docker Compose stacks that include Celery as a task queue service, with healthchecks and resource limits.
Generate Docker Compose stacks that include Django with PostgreSQL, with production-ready settings.
Generate and audit Docker Compose stacks with best-practice configurations for security and reliability.
Generate Docker Compose stacks that include FastAPI with PostgreSQL and optional Redis/Celery.
Generate Docker Compose stacks for monitoring with Grafana, Prometheus, and node-exporter.
Generate Docker Compose stacks that include MySQL as the database for WordPress.
Generate Docker Compose stacks that include Next.js standalone with PostgreSQL.
Generate Docker Compose stacks for a simple Nginx static server.
Generate Docker Compose stacks that include Node.js services with PostgreSQL and/or Redis.
Generate Docker Compose stacks that include PostgreSQL (16-alpine) with healthchecks and named volumes.
Generate Docker Compose stacks for monitoring with Prometheus and Grafana.
Generate multi-stage Dockerfiles for Python applications, and compose stacks with Python services.
Generate Docker Compose stacks that include Redis (7-alpine) with healthchecks and resource limits.
Generate Docker Compose stacks that include WordPress with MySQL.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Docker Forge MCP Generate a Docker Compose for a Node.js API with PostgreSQL"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Docker Forge MCP
Generate, audit, and tune Docker Compose stacks inside Claude Code — before you copy-paste anything.
Most DevOps work in AI assistants means prompting for a compose file, getting something almost-right, then spending 30 minutes fixing healthchecks, resource limits, and Traefik labels by hand. Docker Forge does all that before the compose file lands in your project.
Pure logic, no API keys, $0 to run.
4 tools
Tool | What it does | Tier |
| Generate a production-ready Docker Compose from a description | Free |
| Audit your compose for security & best-practice issues (scored 0-100) | Free |
| Generate Traefik v3 labels with middlewares | Free |
| List all available stack templates | Free |
| Multi-stage, hardened Dockerfile for Node/Python/Go | Pro |
| Extract all | Pro |
Related MCP server: Docker MCP
Quick start
npx -y docker-forge-mcpOr add to your Claude Code MCP config:
{
"mcpServers": {
"docker-forge": {
"command": "npx",
"args": ["-y", "docker-forge-mcp"]
}
}
}Usage examples
Generate a stack:
"Generate a Docker Compose for a Node.js API with PostgreSQL and Redis, domain api.myapp.com"
Audit an existing compose:
"Audit this docker-compose.yml for security issues" → paste your file
Add Traefik:
"Add Traefik v3 labels for my 'backend' service on port 3000 at api.example.com with rate limiting"
Supported stacks
Stack type | Services |
| Node.js + PostgreSQL + Redis |
| Node.js + PostgreSQL |
| Node.js + Redis |
| FastAPI + PostgreSQL + Redis + Celery |
| FastAPI/Django + PostgreSQL |
| WordPress + MySQL |
| Next.js standalone + PostgreSQL |
| Prometheus + Grafana + node-exporter |
| Nginx static server |
What's in every generated stack
restart: unless-stoppedon all servicesdeploy.resources.limits(CPU + memory) on every containerhealthcheckon every servicedepends_onwithcondition: service_healthyNamed volumes (not anonymous)
PostgreSQL pinned to
16-alpine, Redis to7-alpineOptional Traefik v3 labels + HTTP→HTTPS redirect
Audit checks
Critical (score -20 each): privileged mode, root user, docker socket mounted, plaintext secrets in env, database ports exposed to internet
Warning (score -5 each): missing restart policy, no resource limits, :latest image tag, no healthcheck, bare depends_on without service_healthy
Info (score -1): no network isolation, simple depends_on
Traefik middleware presets
rate-limit, security-headers (HSTS + XSS + nosniff), auth-basic, compress, redirect-https
License
MIT — frederic.suretat.com/lab
Available Tools
6 toolsadd_traefikA
Generate Traefik v3 labels for a Docker service. Produces ready-to-paste labels for docker-compose.yml and a networks section. Supports TLS (Let's Encrypt), HTTP→HTTPS redirect, and optional middleware presets: rate-limit, security-headers, auth-basic, compress.
Inputs: port (required), domain (required), service_name (required), tls, +4 more.
audit_composeA
Audit a Docker Compose YAML string for security vulnerabilities and best-practice violations. Checks: privileged mode, root user, docker socket mounts, plaintext secrets, exposed database ports, missing restart policies, missing resource limits, unpinned image tags, missing healthchecks, and depends_on readiness issues. Returns a score (0-100) and categorized issues (critical/warning/info).
Inputs: compose_yaml (required).
generate_dockerfileA
[PRO] Generate an optimized, security-hardened multi-stage Dockerfile. Supports Node.js (including Next.js standalone), Python (FastAPI/Django), and Go. Features: multi-stage builds, non-root user, minimal final image, HEALTHCHECK.
Inputs: runtime (required), port, version, app_type, +1 more.
generate_envA
[PRO] Extract all environment variable placeholders (${VAR}) from a Docker Compose YAML and generate a .env template file with categorized comments (database, auth/secrets, app). Includes generation hints for secrets.
Inputs: compose_yaml (required).
generate_stackA
Generate a production-ready Docker Compose stack from a natural language description or stack type. Includes security best practices: resource limits, healthchecks, restart policies, non-root users, named volumes. Optionally adds Traefik v3 labels for reverse proxy + HTTPS.
Inputs: domain, db_name, app_name, stack_type, +4 more.
list_stacksA
List all available Docker Compose stack templates with descriptions and tags.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool has a unique, clearly defined purpose: Traefik labels, compose auditing, Dockerfile generation, env template extraction, stack generation, and listing templates. No functional overlap exists.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., add_traefik, audit_compose, list_stacks). No mixing of conventions or vague verbs.
With 6 tools, the server is tightly scoped to Docker/Compose utilities. Every tool addresses a distinct need; no excess and no trivial tools.
The set covers generation, auditing, and listing for common Docker workflows. Missing a tool for deploying or modifying stacks, but the existing tools handle core creation and validation tasks.
Related MCP Connectors
Claude Code / MCP skills for the dev pipeline: discover, spec, design, build, ship, operate.
Source-checked CLI guides and model-aware planning for Claude Code, Codex, and Grok Build.
Work on your own computers from Claude or ChatGPT: run commands, edit and search files.
Multi-brand AI code review for Claude: up to 12 reviewers and a judge, no install.
Related MCP Servers
- AlicenseBqualityDmaintenanceA powerful Model Context Protocol (MCP) server for Docker operations, enabling seamless container and compose stack management through Claude AI.4504MIT
- FlicenseNot gradedqualityDmaintenanceEnables Docker container management directly through Claude using the Model Context Protocol. Provides 14 tools for managing containers, images, volumes, and Docker Compose deployments through natural language commands.-
- AlicenseAqualityDmaintenanceEnables managing Docker containers (run, list, stop, remove, view logs) through Claude Desktop using natural language commands.586 npmMIT
- AlicenseAqualityDmaintenanceEnables Claude to manage Docker Compose containers by updating, running commands, and viewing status/logs.2MIT