dokku-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOKKU_HOST | Yes | Dokku SSH hostname (required) | |
| DOKKU_MCP_MODE | No | `read-only` or `read-write` | read-only |
| DOKKU_SSH_PORT | No | SSH port | 22 |
| DOKKU_SSH_USER | No | SSH user (Dokku convention) | dokku |
| DOKKU_APP_DENYLIST | No | Comma-separated apps always blocked | |
| DOKKU_SSH_KEY_PATH | No | Path to private key | |
| DOKKU_APP_ALLOWLIST | No | Comma-separated apps; empty = all |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_appsA | List Dokku apps on the host. Side effects: none (read-only). Respects DOKKU_APP_ALLOWLIST / DOKKU_APP_DENYLIST — denied apps are filtered out. |
| app_reportA | Get process report for a Dokku app (running state, scale, etc.). Side effects: none (read-only).
Runs |
| app_configA | Get environment config vars for a Dokku app. Side effects: none (read-only).
Secret-looking keys (PASSWORD, TOKEN, DATABASE_URL, etc.) are masked as |
| app_logsA | Fetch recent logs for a Dokku app. Side effects: none (read-only). Default lines=50; hard maximum is 500. |
| app_domainsA | Get domain / VHOST report for a Dokku app. Side effects: none (read-only).
Runs |
| app_urlB | Derive public URLs for a Dokku app from its domains. Side effects: none (read-only). Convenience wrapper over domains:report; defaults to https:// scheme. |
| create_appA | Create a new Dokku app. Side effects: creates an application on the Dokku host. Requires DOKKU_MCP_MODE=read-write. App names must be lowercase alphanumeric with optional hyphens. |
| set_configA | Set one or more config vars on a Dokku app. Side effects: updates environment variables; restarts the app unless no_restart=True. Requires DOKKU_MCP_MODE=read-write and confirm=True. Values are never echoed back in the response — only keys are returned. |
| restart_appA | Restart all processes for a Dokku app. Side effects: restarts the application (downtime possible). Requires DOKKU_MCP_MODE=read-write and confirm=True. |
| scale_appA | Scale process types for a Dokku app (e.g. web=2, worker=1). Side effects: changes running process counts. Requires DOKKU_MCP_MODE=read-write and confirm=True. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools are clearly distinct: list_apps is the only app-level listing, app_report/app_config/app_logs/app_domains/app_url each target a different aspect of an app, and the write tools (create_app, set_config, restart_app, scale_app) have distinct actions. The only mild overlap is app_domains vs app_url, since app_url is a convenience wrapper over domains:report, but the descriptions make the relationship clear.
The naming pattern is mostly consistent: read operations use app_* (app_report, app_config, app_logs, app_domains, app_url) plus list_apps, and write operations use verb_app (create_app, set_config, restart_app, scale_app). The minor inconsistency is that list_apps breaks the app_* pattern and set_config/restart_app/scale_app use verb_app rather than app_verb, but the overall convention is still predictable.
10 tools is well-scoped for a Dokku MCP server. The read-only surface covers the most common inspection needs (list, report, config, logs, domains, URL), and the write surface covers the core app lifecycle operations (create, config, restart, scale). No tool feels redundant or unnecessary.
The tool surface covers the primary Dokku workflows: listing/creating apps, inspecting app state/config/logs/domains, updating config, restarting, and scaling. Obvious gaps include app deletion, app destruction, and process management (e.g. ps:scale is covered but ps:restart is not), but these are reasonable omissions for a safe MCP server and agents can work around them.