Manage Docker containers, images, volumes, and networks across dev/stg/prod environments — via Cloudflare Tunnel relay.
Use with AI AssistantsMCP
Connect Claude, Cursor, or any MCP-compatible client — then call tools directly
① Add This MCP Server
Paste into your AI client config — then all its tools are available instantly.
{
"mcpServers": {
"docker-engine-cf": {
"url": "https://mcp.aerostack.dev/s/aerostack/mcp-docker-engine-cf",
"headers": {
"Authorization": "Bearer YOUR_AEROSTACK_TOKEN"
}
}
}
}Replace YOUR_AEROSTACK_TOKEN with your API token from the dashboard.
② Call a Tool
Ask your AI assistant to call a specific tool, or send raw JSON-RPC:
Natural Language Prompt
“Use the list_environments tool to list all configured docker environments (dev, stg, prod) and their relay urls”
Using a Workspace?
Add this MCP to your Workspace — your team shares one token, secrets are stored securely, and every AI agent in the workspace can call it without per-user setup.
Manage containers, images, volumes, and networks across dev/stg/prod environments — from any Aerostack agent via Cloudflare Tunnel.
A Cloudflare Worker MCP that calls docker-relay servers running on your infrastructure behind Cloudflare Tunnel. No Docker ports need to be exposed publicly — all traffic flows through signed HTTPS requests over the tunnel.
Live endpoint: https://mcp.aerostack.dev/s/aerostack/mcp-docker-engine-cf
Aerostack Agent
│
▼
mcp-docker-engine-cf (this Worker — on Cloudflare edge)
│ HTTPS + Bearer token
▼
Cloudflare Tunnel endpoint (e.g. docker-dev.yourdomain.com)
│
▼
docker-relay (127.0.0.1:4242 on your server)
│
▼
Docker Engine (local socket)
See docker-relay/README.md for per-server setup instructions.
| Variable | Required | Description |
|---|---|---|
DOCKER_RELAY_SECRET | Yes | Shared Bearer token — set same value in each docker-relay process and here |
DOCKER_DEV_URL | No | Relay HTTPS URL for dev environment (e.g. https://docker-dev.yourdomain.com) |
DOCKER_STG_URL | No | Relay HTTPS URL for staging environment |
DOCKER_PROD_URL | No | Relay HTTPS URL for production environment |
At least one of DOCKER_DEV_URL, DOCKER_STG_URL, or DOCKER_PROD_URL must be set.
"List all running containers on prod"
"Show me the last 200 log lines from the api container on stg"
"What's CPU/memory usage across all containers on dev?"
"Restart the nginx service in the web compose project on prod"
"What images are on dev and when were they pulled?"
curl -X POST https://mcp.aerostack.dev/s/aerostack/mcp-docker-engine-cf \
-H 'Content-Type: application/json' \
-H 'X-Mcp-Secret-DOCKER-RELAY-SECRET: your-relay-secret' \
-H 'X-Mcp-Secret-DOCKER-DEV-URL: https://docker-dev.yourdomain.com' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_containers","arguments":{"environment":"dev"}}}'
| Tool | Description |
|---|---|
list_environments | List configured environments and their relay URLs |
list_containers | List containers with status, image, ports (all or filtered) |
get_container_logs | Tail logs with line count, since filter, and timestamps |
inspect_container | Full container details: config, env vars, mounts, health |
get_container_stats | Live CPU, memory, and network stats |
start_container | Start a stopped container |
stop_container | Stop a running container |
restart_container | Restart a container |
remove_container | Remove a container (force option for running containers) |
exec_in_container | Run a command inside a running container |
list_images | List Docker images with size and age |
pull_image | Pull an image from a registry |
remove_image | Remove a local image |
list_networks | List Docker networks |
inspect_network | Get network details including connected containers |
list_volumes | List Docker volumes |
inspect_volume | Get volume details and mount point |
system_info | Docker daemon info: version, resources, runtime |
disk_usage | Docker disk usage breakdown (images, containers, volumes) |
list_compose_services | List services in a Docker Compose project |
compose_logs | Get logs from a Compose service |
compose_restart | Restart one or all Compose services |
MIT
Live Endpoint
https://mcp.aerostack.dev/s/aerostack/mcp-docker-engine-cf
Sub-50ms globally · Zero cold start
@aerostack
Pre-built functions for the most common MCP tool patterns. Clone, extend, and deploy.
by @aerostack
Tasks, projects, sections, comments, teams, custom fields via Asana's official MCP
by @aerostack
Jira issues, sprints, Confluence pages via Atlassian's official MCP
by @aerostack
Cloudflare Workers, KV, R2, D1, Pages, DNS via Cloudflare's official MCP
by @aerostack
Dashboards, monitors, logs, metrics, incidents, SLOs, APM traces via Datadog's official MCP
by @aerostack
Files, frames, components, comments, variables via Figma's official MCP
by @aerostack
GitHub repos, PRs, issues, branches, code search via GitHub's official hosted MCP
The Docker Engine Cf MCP gives Claude 22 tools covering containers, images, environments. Claude can read, create, update, and manage Docker Engine Cf data directly from a conversation.
Yes. The Docker Engine Cf MCP includes tools to list and retrieve environments from your Docker Engine Cf account. Claude can filter, sort, and summarize environments based on your instructions.
Yes. The Docker Engine Cf MCP uses the open Model Context Protocol standard, so it works in Claude, Cursor, Windsurf, and any other MCP-compatible AI tool. All 22 Docker Engine Cf tools are available everywhere you connect it — install once on Aerostack.
Yes. The Docker Engine Cf MCP includes run and trigger tools that let Claude execute Docker Engine Cf actions on demand. This is useful for automating repetitive Docker Engine Cf tasks directly from a Claude or Cursor session.