Dokku MCP Server

Most monitoring and observability work still happens through a UI a human drives. Dokku MCP MCP server moves it into the conversation instead. This server exposes Dokku's management capabilities through the standardized Model Context Protocol (MCP), allowing Large Language Models (LLMs) to interact with and manage a Dokku instance.

The short version

• Core — server info and plugin list resources; optional server logs tool
• Apps — create, deploy (Git URL + ref), scale, env config, status; app list resource; troubleshooting prompt
• Deployments — async deploys with IDs and background status

The tools it exposes

The server publishes 4 tools. What each one is for:

• Highlights — The Highlights tool exposed by this server
• NEXT — The NEXT tool exposed by this server
• IDEAS — The IDEAS tool exposed by this server
• Testing — The Testing tool exposed by this server

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What it needs from you

Configuration is passed through the environment: DOKKU_MCP_SECURITY_BLACKLIST, DOKKU_MCP_SSH_HOST, DOKKU_MCP_SSH_KEY_PATH, DOKKU_MCP_SSH_PORT, DOKKU_MCP_SSH_USER, DOKKU_MCP_LOG_LEVEL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Dokku MCP's toolset — Highlights, NEXT, IDEAS and 1 more — is a fair guide to whether it matches your workflow. It is maintained by alex-galey; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.