Dokku

Download the latest release for your platform:

# Linux (amd64; also available: arm64, arm) curl -L -o dokku-mcp https://github.com/dokku-mcp/dokku-mcp/releases/latest/download/dokku-mcp-linux-amd64 chmod +x dokku-mcp sudo mv dokku-mcp /usr/local/bin/ # macOS (amd64; also available: arm64) curl -L -o dokku-mcp https://github.com/dokku-mcp/dokku-mcp/releases/latest/download/dokku-mcp-darwin-amd64 chmod +x dokku-mcp sudo mv dokku-mcp /usr/local/bin/

Compressed archives (dokku-mcp-<os>-<arch>.tar.gz) are also published with each release.

git clone https://github.com/dokku-mcp/dokku-mcp.git cd dokku-mcp make build

The server can be configured in two ways: using aconfig.yamlfile or via environment variables.

Create a configuration file at one of the following locations:

- System-wide:/etc/dokku-mcp/config.yaml
- User-specific:~/.dokku-mcp/config.yaml
- Local:config.yamlin the same directory as the binary.

ssh: host: "your-dokku-host.com" user: "dokku" # key_path: "/path/to/your/ssh/private/key" # Optional, uses ssh-agent if empty log_level: "info"

All configuration settings can be overridden with environment variables prefixed withDOKKU_MCP_. For example:

export DOKKU_MCP_SSH_HOST="your-dokku-host.com" export DOKKU_MCP_SSH_USER="dokku" export DOKKU_MCP_LOG_LEVEL="debug"

Once configured, you can run the server:

The server will start and be ready to accept connections from an MCP client.

For development and testing without needing a remote Dokku instance, you can run a local Dokku server using Docker.

This command will download the necessary Docker images and configure the local Dokku instance. It only needs to be run once.

When the local Dokku container is running, the MCP server (with default config) should be able to connect to it. You can run integration tests against this local instance.

The server supports two transport modes for clients:

- stdio(default):Standard input/output for direct process communication.
- sse(Server-Sent Events):HTTP-based transport for web clients.

DOKKU_MCP_TRANSPORT_TYPE=sse dokku-mcp

For SSE transport, CORS is handled by default withAccess-Control-Allow-Origin: . For remote deployments, you can enable custom CORS middleware:

transport: type: sse cors: enabled: true allowed_origins: - "https://app.example.com" - ".example.com"

This section is for developers who want to contribute to the project or modify the source code.

git clone https://github.com/dokku-mcp/dokku-mcp.git cd dokku-mcp

This command installs all the necessary Go tools for development, linting, and testing.

This command sets up Git hooks to ensure code quality before commits.

# This command builds the binary and starts the server. make start

The project uses aMakefileto automate common tasks.

- make help: Show all available commands.
- make check: Run all code quality checks (linting, formatting, complexity).
- make build: Build the server binary.
- make clean: Clean up build artifacts.

This runs all unit and integration tests and generates an HTML coverage report atcoverage.html.

Run integration tests against local Dokku:Make sure your local Dokku container is running (make dokku-start).

The server followsDomain-Driven Design (DDD)principles, with a clear separation between:

- Domain Layer (internal/domain):Core business logic, entities, and repository interfaces.
- Application Layer (internal/application):Use case orchestration and coordination.
- Infrastructure Layer (internal/infrastructure):Implementations of interfaces, such as the Dokku client, databases, and external services.

It features aplugin-based architecturelocated ininternal/server-plugins, where each plugin encapsulates a specific set of Dokku features (e.g.,app,core,deployment).

For more details, please refer to the documentation in thedocs/directory.

dokku-mcp/ ├── cmd/ # Entry points for the application │ └── server/ # Server main command ├── internal/ # Private application code │ ├── server/ # MCP server and adapter │ ├── server-plugin/ # Plugin system infrastructure │ ├── server-plugins/ # Actual plugin implementations (app, core, etc.) │ ├── dokku-api/ # Dokku CLI client and API │ └── shared/ # Shared domain types and services ├── pkg/ # Reusable packages (config, logger, etc.) ├── docs/ # Project documentation └── scripts/ # Helper scripts

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Create, build, deploy, and manage Netlify resources using natural language.

European cloud hosting. Use your favorite AI coding assistant to easily deploy and manage apps on Ploi Cloud.

Simplifies framework deployments on various hosting environments, with a focus on shared hosting.

Expose the entire ArgoCD API to LLMs via MCP using just 2 auto-generated tools powered by the OpenAPI spec.

Bult.ai MCP Server lets Claude Desktop deploy and manage Bult.ai cloud hosting resources, including projects, services, GitHub and Docker deployments, routes, volumes, templates, logs, and build history.

Integrate with the Coolify API to manage your servers, applications, and databases.

An MCP server for interacting with the Coolify API to manage servers and applications.

An MCP server for integrating with Coolify, the self-hostable alternative to Netlify and Vercel.