Docker Swarm MCP Server
A production-ready MCP server for Docker Swarm that provides full control over services, stacks, configs, and secrets with smart context preservation to reduce tool clutter.
README
π³ Docker Swarm MCP Server
The missing MCP server for Docker Swarm. Finally, a production-ready MCP that gives you full Docker Swarm control without drowning your AI in tool descriptions.
π― Why This Exists
The Gap: After searching the MCP ecosystem, I found:
- β Regular Docker MCPs with limited functionality (containers only, localhost only)
- β Portainer MCP that only works with CE (not BE/EE)
- β No proper Swarm support anywhere
- β All existing servers dump 20+ tools into your agents context window
The Solution: This server fills that gap with:
- β Full Docker Swarm support - Services, stacks, configs, secrets
- β Smart context preservation - Only shows tools you need (2-6 instead of 23)
- β Production security - Bearer tokens, TLS, remote Docker support, Tailscale Integration (coming soon)
- β No bloat - Just the tools you need, when you need them, filtered by the task at hand.
Note on secrets and client config:
- Do not commit secrets. Use environment variables (e.g., MCP_ACCESS_TOKEN), Docker secrets, or a secret manager.
- The .kilocode/ directory is gitignored. If you need a local MCP client config, copy mcp.client.json.example to your local tooling and set Authorization to use a runtime value like
Bearer ${MCP_ACCESS_TOKEN}.
π Quick Start (2 Minutes)
1οΈβ£ Deploy to Your Swarm
# Save this as docker-swarm-mcp.yml (or use one of the examples below)
# Deploy to your swarm
docker stack deploy -c docker-swarm-mcp.yml mcp-server
# Verify it's running
docker service logs mcp-server_docker-mcp
<details> <summary><b>π Basic Stack Configuration</b></summary>
version: '3.8'
services:
docker-mcp:
image: ghcr.io/khaentertainment/docker-swarm-mcp:latest
environment:
- MCP_ACCESS_TOKEN=${MCP_ACCESS_TOKEN:-change-me-to-secure-token}
- LOG_LEVEL=INFO
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
ports:
- "8000:8000"
deploy:
replicas: 1
restart_policy:
condition: any
delay: 5s
placement:
constraints:
- node.role == manager # Needs Docker socket access
networks:
- mcp-network
networks:
mcp-network:
driver: overlay
attachable: true
</details>
<details> <summary><b>π Production Stack with Secrets</b></summary>
version: '3.8'
services:
docker-mcp:
image: ghcr.io/khaentertainment/docker-swarm-mcp:latest
environment:
- MCP_ACCESS_TOKEN_FILE=/run/secrets/mcp_token
- LOG_LEVEL=INFO
- ALLOWED_ORIGINS=https://claude.ai,http://localhost:*
secrets:
- mcp_token
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
ports:
- "8000:8000"
deploy:
replicas: 1
restart_policy:
condition: any
delay: 5s
placement:
constraints:
- node.role == manager
resources:
limits:
memory: 512M
reservations:
memory: 128M
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:8000/mcp/health"]
interval: 30s
timeout: 3s
retries: 3
networks:
- mcp-network
secrets:
mcp_token:
external: true # Create with: echo "your-secure-token" | docker secret create mcp_token -
networks:
mcp-network:
driver: overlay
attachable: true
encrypted: true
Setup the secret first:
# Generate a secure token
openssl rand -base64 32 | docker secret create mcp_token -
# Or use your own token
echo "your-secure-token-here" | docker secret create mcp_token -
</details>
<details> <summary><b>π Stack with Traefik Integration</b></summary>
version: '3.8'
services:
docker-mcp:
image: ghcr.io/khaentertainment/docker-swarm-mcp:latest
environment:
- MCP_ACCESS_TOKEN_FILE=/run/secrets/mcp_token
- LOG_LEVEL=INFO
- ALLOWED_ORIGINS=https://mcp.yourdomain.com
secrets:
- mcp_token
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
deploy:
replicas: 2 # High availability
restart_policy:
condition: any
delay: 5s
placement:
constraints:
- node.role == manager
update_config:
parallelism: 1
delay: 10s
labels:
- "traefik.enable=true"
- "traefik.http.routers.mcp.rule=Host(`mcp.yourdomain.com`)"
- "traefik.http.routers.mcp.entrypoints=websecure"
- "traefik.http.routers.mcp.tls=true"
- "traefik.http.routers.mcp.tls.certresolver=letsencrypt"
- "traefik.http.services.mcp.loadbalancer.server.port=8000"
- "traefik.http.middlewares.mcp-headers.headers.customrequestheaders.Authorization=Bearer ${MCP_TOKEN}"
- "traefik.http.routers.mcp.middlewares=mcp-headers"
networks:
- traefik-public
- mcp-internal
secrets:
mcp_token:
external: true
networks:
traefik-public:
external: true
mcp-internal:
driver: overlay
encrypted: true
internal: true
</details>
<details> <summary><b>π§ Multi-Node Swarm with Constraints</b></summary>
version: '3.8'
services:
docker-mcp:
image: ghcr.io/khaentertainment/docker-swarm-mcp:latest
environment:
- MCP_ACCESS_TOKEN_FILE=/run/secrets/mcp_token
- LOG_LEVEL=INFO
secrets:
- mcp_token
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
ports:
- target: 8000
published: 8000
protocol: tcp
mode: host # Use host mode for better performance
deploy:
replicas: 1
restart_policy:
condition: any
delay: 5s
placement:
constraints:
- node.role == manager
- node.labels.mcp == true # Only on labeled nodes
preferences:
- spread: node.id
update_config:
parallelism: 1
delay: 10s
failure_action: rollback
rollback_config:
parallelism: 1
delay: 10s
networks:
- mcp-network
configs:
filter_config:
file: ./filter-config.json # Optional: Custom tool filtering
secrets:
mcp_token:
external: true
networks:
mcp-network:
driver: overlay
attachable: true
encrypted: true
Label your node:
docker node update --label-add mcp=true <node-name>
</details>
2. Configure Your AI Assistant
Different AI assistants and code editors configure MCP servers in slightly different ways. Find your client in the groups below and use the corresponding JSON configuration.
Remember to replace <YOUR_SECURE_TOKEN_HERE> with your actual token.
<details open> <summary><b>Group A: Clients with Standard Header Support</b></summary>
These clients use a more structured format that supports passing the API token securely in the request headers. This is the recommended and most secure method.
Example Clients: Claude Desktop Β β’ Copilot Coding Agent Β β’ Gemini CLI Β β’ Visual Studio 2022 Β β’ Crush Β β’ Opencode
Configuration:
{
"mcpServers": {
"docker-swarm-mcp": {
"transport": {
"type": "http",
"url": "http://localhost:8000/mcp/",
"headers": {
"Authorization": "Bearer <YOUR_SECURE_TOKEN_HERE>"
}
}
}
}
}
</details>
β οΈ Security Note: Query parameter authentication (
?accessToken=...) has been removed in v0.5.0 for security reasons. Tokens should never appear in URLs because they end up in server logs, browser history, and referrer headers. Use headers instead.
<details> <summary><b>Group B: Clients with Custom Header Support [Cursor, VS Code, etc.]</b></summary>
These clients support custom headers but may not support the full Authorization: Bearer format. Use the X-Access-Token header for simpler configuration while keeping tokens out of the URL.
- Example Clients: Cursor Β β’ VS Code β’ Rovo Dev CLI β’ Qodo Gen β’ Trae
Configuration:
Note: The key name might be url or serverUrl depending on the client. Most clients accept a headers block for custom headersβcheck your client's documentation if one doesn't work.
Example using url:
{
"mcpServers": {
"docker-swarm-mcp": {
"type": "http",
"url": "http://localhost:8000/mcp/",
"headers": {
"X-Access-Token": "<YOUR_SECURE_TOKEN_HERE>"
}
}
}
}
Example for clients like Windsurf that use serverUrl:
{
"mcpServers": {
"docker-swarm-mcp": {
"serverUrl": "http://localhost:8000/mcp/",
"headers": {
"X-Access-Token": "<YOUR_SECURE_TOKEN_HERE>"
}
}
}
}
</details>
<details>
<summary><b>Group C: Command-Line Installation</b></summary>
The following clients support a streamlined mcp add command, allowing you to register the HTTP server directly from your terminal. π
Claude Code
claude mcp add --transport http docker-swarm-mcp \
--header "X-Access-Token: <your-secure-token-here>" \
http://localhost:8000/mcp/
Gemini CLI
gemini mcp add --transport http docker-swarm-mcp \
--header "X-Access-Token: <your-secure-token-here>" \
http://localhost:8000/mcp/
Codex CLI
codex mcp add --transport http docker-swarm-mcp \
--header "X-Access-Token: <your-secure-token-here>" \
http://localhost:8000/mcp/
Opencode
opencode mcp add --transport http docker-swarm-mcp \
--header "X-Access-Token: <your-secure-token-here>" \
http://localhost:8000/mcp/
Qwen Code
qwen mcp add docker-swarm-mcp \
--header "X-Access-Token: <your-secure-token-here>" \
http://localhost:8000/mcp/
Note: Remember to replace <your-secure-token-here> with your actual access token. If your CLI does not support custom headers, use --header "Authorization: Bearer <your-secure-token-here>" instead.
</details>
Important Note: The examples above show the
docker-swarm-mcpobject being added inside anmcpServersblock. Your client's configuration file might use a different top-level key (e.g.,mcp,servers). Please merge this configuration into your existing settings file structure.
3οΈβ£ Start Using It!
Just ask your AI naturally:
- "What containers are running?"
- "Deploy my app stack"
- "Scale the web service to 5 replicas"
- "Show me the swarm nodes"
The server automatically detects what you're trying to do and provides just the right tools!
π― What Makes This Different
π§ Smart Tool Filtering
Traditional MCP servers dump all their tools into your context. This server is smarter:
| You Say | Tools Returned | Context Saved |
|---|---|---|
| "List my containers" | 4 container tools | 19 tools hidden |
| "Deploy a stack" | 3 compose tools | 20 tools hidden |
| "Check swarm status" | 3 swarm tools | 20 tools hidden |
| "Create a network" | 3 network tools | 20 tools hidden |
Your AI focuses on YOUR project, not on reading documentation.
π³ Real Docker Swarm Support
Unlike other Docker MCPs, this one actually understands Swarm:
- Services - Create, scale, update, rolling deployments
- Stacks - Deploy complete applications
- Configs & Secrets - Secure configuration management
- Networks - Overlay networks, encryption
- Nodes - Manage your swarm cluster
π Production Security
Built for real production use:
- Bearer token authentication
- Docker secrets support
- TLS connections to remote Docker
- CORS configuration
- Rate limiting ready
π Self-Documenting
Your AI can learn the system through meta-tools:
Ask: "How do I discover Docker tools?"
Response: Uses `discover-tools` to explain the 6 categories
π‘ Examples
Container Operations
# Your AI can now:
- List all containers with detailed status
- Create containers with complex configurations
- Start/stop/restart containers
- View logs and exec into containers
- Remove containers safely
Swarm Service Management
# Your AI can now:
- Deploy services with replicas
- Scale services up or down
- Update services with rolling updates
- Check service logs across all replicas
- Manage service constraints and preferences
Stack Deployments
# Your AI can now:
- Deploy complete application stacks
- Update stacks with new configurations
- Remove stacks cleanly
- List all stacks and their services
Network & Volume Management
# Your AI can now:
- Create overlay networks for swarm
- Manage network encryption
- Create and manage volumes
- Connect/disconnect containers from networks
π οΈ Advanced Configuration
<details> <summary><b>Environment Variables</b></summary>
| Variable | Required | Default | Description |
|---|---|---|---|
MCP_ACCESS_TOKEN |
β | - | Bearer token for authentication |
DOCKER_HOST |
β | unix:///var/run/docker.sock |
Docker engine connection |
DOCKER_TLS_VERIFY |
β | 0 |
Enable TLS verification (1/0) |
DOCKER_CERT_PATH |
β | - | Path to TLS certificates |
LOG_LEVEL |
β | INFO |
DEBUG shows context metrics |
ALLOWED_ORIGINS |
β | * |
CORS origins (comma-separated) |
MCP_TRANSPORT |
β | http |
Transport mode (http/sse) |
</details>
<details> <summary><b>Custom Tool Filtering</b></summary>
Edit filter-config.json to customize which tools are available:
{
"task_type_allowlists": {
"container-ops": ["list-containers", "create-container", "start-container"],
"swarm-ops": ["list-services", "create-service", "scale-service"],
"compose-ops": ["deploy-stack", "list-stacks"]
},
"max_tools": 10,
"blocklist": ["remove-volume", "prune-system"]
}
Mount as a config in your stack:
configs:
filter_config:
file: ./filter-config.json
services:
docker-mcp:
configs:
- source: filter_config
target: /app/filter-config.json
</details>
<details> <summary><b>Remote Docker Access</b></summary>
TLS Connection:
export DOCKER_HOST="tcp://remote-host:2376"
export DOCKER_TLS_VERIFY="1"
export DOCKER_CERT_PATH="/path/to/certs"
SSH Connection:
export DOCKER_HOST="ssh://user@remote-host"
Tailscale/Wireguard:
export DOCKER_HOST="tcp://100.x.y.z:2376" # Tailscale IP
</details>
<details> <summary><b>Building From Source</b></summary>
# Clone the repository
git clone https://github.com/KHAEntertainment/docker-swarm-mcp.git
cd docker-swarm-mcp
# Build with Docker
docker build -t docker-swarm-mcp:latest .
# Or build with Docker Compose
docker-compose build
# For development
poetry install
poetry run uvicorn app.main:app --reload
</details>
π§ͺ Testing
# Quick health check
curl http://localhost:8000/mcp/health
# Test authentication (JSON-RPC)
curl -s -X POST http://localhost:8000/mcp/ \
-H "Authorization: Bearer your-token" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":"1","method":"tools/list","params":{}}'
# Test authentication with custom header (JSON-RPC)
curl -s -X POST http://localhost:8000/mcp/ \
-H "X-Access-Token: your-token" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":"1","method":"tools/list","params":{}}'
# Test with intent detection
curl -X POST http://localhost:8000/mcp/ \
-H "Authorization: Bearer your-token" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"method": "tools/list",
"params": {"query": "show me running containers"},
"id": 1
}'
REST API endpoints are now served from
/api/*. SetENABLE_REST_API=trueto expose them during development.
Poetry Shortcuts
poetry run testβ run test suitepoetry run test-fastβ no coveragepoetry run test-covβ with coverage reports
π Documentation
- Client Setup Guide - Configure Claude Desktop, Cursor, etc.
- Quick Reference - Common commands
- JSON-RPC Protocol - API details
- Security - Best practices
- Roadmap - Coming features
π€ Contributing
This fills a real gap in the MCP ecosystem! Contributions welcome:
- Report bugs - Open an issue with reproduction steps
- Suggest features - Check the roadmap first
- Submit PRs - Follow existing patterns
- Improve docs - Always appreciated
- Share your stacks - Add examples to help others
Focus areas:
- More Swarm-specific tools
- Better Portainer BE/EE integration
- Enhanced security features
- Multi-cluster support
π Acknowledgments
- Built on the Model Context Protocol (MCP) by Anthropic with FastAPI MCP.
- Inspired by the need for proper Docker Swarm support in AI workflows
- Thanks to the Docker and Swarm communities
License: MIT | Status: Production Ready | Gap Filled: β
Finally, an MCP server that actually understands Docker Swarm. See docs/dependencies/tailscale.md for detailed Tailscale setup.
π Docker Swarm MCP Server v0.5.0 - Production Ready
Build Status: Sun Oct 12 22:19:46 PDT 2025 All CodeRabbit fixes applied β
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.