Release v0.2.0
Changes
- ci: fix auto-tag triggering auto-release
- ci: trigger auto-release from auto-tag
- ci: auto-release on VERSION change
- ci: improve release script
- docs: update version to v0.2.0
- fix: release build stage permissions
- ci: fix release workflow
- fix: simplify ToolResponseData handling in MCP envelope
- fix: typing
- feat: onboarding resources and log visibility
- add onboarding DTOs, Fx module, and plugin handlers for discovery resources
- introduce MCP envelope helpers and log sanitization for resource responses
- wire ring-buffer logging so server logs can be exposed via tools
- update server wiring, configs, and scripts to enable the new plugin
- document onboarding flow and logging controls in README and guides
- feat: dokku client resilience and deployment feedback
- add typed errors for Dokku and update client capabilities, including tests
- adjust application repository behavior with coverage aligned to new error paths
- enhance deployment status polling to surface clearer feedback
- keep domain plugin adapters consistent with new client responses
- refresh build config and dependencies so tooling stays compatible
- feat: implement deployment tracker with async status polling
- ci: reduce dokku compatibility matrix tests
- feat: default build version to current commit hash
- feat: oss-index login required for Nancy
- fix: type safety violations and security vulnerabilities (GO-2025-3900, GO-2025-3956)
-
feat: implement Dokku capabilities management and auto-format command execution- Introduced DokkuCapabilities and CommandRegistry to manage capabilities and command metadata.
- Added asynchronous discovery of Dokku capabilities during client initialization.
- Implemented ExecuteWithAutoFormat method for automatic command output format detection, prioritizing JSON.
- Updated client interface to include capability management methods.
- Enhanced SSH configuration to ensure proper terminal allocation for commands.
- fix: dependency vulnerability issue
- fix: workflow permission
- fix: move letsencrypt to domain plugin
- docs: update version to v0.1.1-alpha
Installation
Download the appropriate binary for your platform from the assets below.
Linux/macOS
# Download and install (replace with actual URL for your architecture)
curl -L -o dokku-mcp https://github.com/alex-galey/dokku-mcp/releases/download/v0.2.0/dokku-mcp-linux-amd64
chmod +x dokku-mcp
sudo mv dokku-mcp /usr/local/bin/Verify installation
dokku-mcp --versionConfiguration
After installing the binary, you need to configure it to connect to your Dokku instance. Configuration can be done using a YAML file or environment variables.
Check config.yaml.example
Using a Configuration File
You can create a configuration file at one of the following locations:
- System-wide:
/etc/dokku-mcp/config.yaml - User-specific:
~/.dokku-mcp/config.yaml
Here is a minimal example to get you started. Create the file and add the following content, adjusting the values for your setup:
# ~/.dokku-mcp/config.yaml
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"For a full list of configuration options, see the config.yaml.example file.
Using Environment Variables
All configuration options can be set using environment variables with the DOKKU_MCP_ prefix. For example:
export DOKKU_MCP_SSH_HOST="your-dokku-host.com"
export DOKKU_MCP_SSH_USER="dokku"
export DOKKU_MCP_LOG_LEVEL="debug"
dokku-mcp