StackWiz MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCKER_HOST | No | Docker daemon socket | |
| CF_API_EMAIL | No | Cloudflare email | |
| DEFAULT_USER | No | File owner (default: current user) | |
| STACKWIZ_ENV | No | Environment (development, production) | production |
| DEFAULT_GROUP | No | File group (default: docker) | |
| CF_DNS_API_TOKEN | No | Cloudflare API token | |
| STACKWIZ_BASE_DIR | No | Base directory for stacks | /srv/dockerdata |
| STACKWIZ_LOG_LEVEL | No | Logging level (DEBUG, INFO, WARNING, ERROR) | INFO |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_stackB | Create a new Docker service stack |
| list_stacksA | List all existing Docker stacks |
| manage_stackC | Perform operations on existing stacks |
| create_dns_recordB | Create a DNS record |
| list_dns_recordsB | List DNS records |
| update_dns_proxyA | Enable or disable Cloudflare proxy for a DNS record |
| delete_dns_recordB | Delete a DNS record |
| validate_stack_configC | Validate a stack configuration |
| health_checkA | Check server health and connectivity Returns system health status including Docker, DNS, and filesystem checks. |
| server_infoA | Get server information and capabilities Returns server version, available tools, and configuration details. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| deploy-web-app | Interactive prompt for deploying a web application |
| setup-database | Guided database deployment with best practices |
| create-api-service | API service deployment with monitoring |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_stack_configs | List all stack configurations |
| list_templates | List available templates |
| get_generic_template | Get generic stack template with docker-compose and env files |
| get_pocketbase_template | Get Pocketbase stack template with docker-compose and env files |
| get_supabase_template | Get Supabase stack template with docker-compose and env files |
| list_networks | List available Docker networks |
| list_domains | List configured domains by scanning .env files |
| get_port_usage | Get port usage map by scanning running containers |
TDQS
Scored across 10 tools
Tools are largely distinct but manage_stack is a generic catch-all that could overlap with create_stack or validate_stack_config. DNS tools and stack tools are clearly separated, and utility tools are distinct.
Most tools follow verb_noun pattern (create_stack, list_dns_records), but health_check and server_info break the pattern by being noun-focused. Also pluralization is inconsistent (list_stacks vs list_dns_records).
10 tools is within the ideal 3-15 range. Each tool serves a clear function in stack management, DNS management, or server introspection, with no obvious bloat.
Stack lifecycle is covered (create, list, manage, validate), but there is no full DNS record update (only proxy toggle), and manage_stack is vague about specific operations like delete. Core workflows are covered but some edge operations are missing.