Can my agent scale my Dokku processes automatically?

Yes. Use the 'ps_scale' tool. You can specify the application name and the target replica count for processes like 'web' or 'worker'. The agent will manipulate the explicit counts within your Dokku cluster instantly.

How do I update environment variables via chat?

Use the 'set_config' tool. Provide the app name, key, and value. The agent will inject the pair into the Docker environment mapping, which typically triggers a rolling deployment to apply the new configuration safely.

Can I run database migrations through the agent?

Absolutely. Use the 'run_command' tool. It boots an ephemeral isolated container cloning your production image, allowing you to run maintenance commands like 'rake db:migrate' or custom scripts without affecting live traffic.

Dokku MCP Server for Claude Desktop 10 tools — connect in under 2 minutes

Name: Dokku
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 10 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Dokku and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "dokku": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Dokku MCP Server

Connect your Dokku instance to any AI agent and take full control of your self-hosted PaaS and container orchestration through natural conversation.

Claude Desktop is the definitive way to connect Dokku to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

Application Lifecycle — List all managed apps and retrieve the overarching directory of deployments on your own infrastructure bypassing standard PaaS fees
Provisioning & Deallocation — Barely instantiate new application repositories or irreversibly dismantle all bound containers and DNS routing records
Environment Auditing — Retrieve the exact .env dictionary bound dynamically via the config plugin to observe runtime inputs and SQL credentials
Configuration Mutation — Inject or remove sensitive environment variables securely, triggering rolling app deployments natively across your cluster
Process Scaling — Manipulate explicit replica counts dynamically, determining whether web or worker containers spool up to meet demand
Live Log Streaming — Pull precise system execution tails to investigate explicit request stack traces and crashing node backtraces without SSH
One-off Executions — Launch raw commands inside ephemeral isolated containers for maintenance tasks like DB migrations or custom scripts

The Dokku MCP Server exposes 10 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Dokku to Claude Desktop via MCP

Follow these steps to integrate the Dokku MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Dokku

Look for the 🔌 icon in the chat. your 10 tools are now available

Why Use Claude Desktop with the Dokku MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Dokku through the Model Context Protocol.

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

Dokku + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Dokku MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Dokku MCP Tools for Claude Desktop (10)

These 10 tools become available when you connect Dokku to Claude Desktop via MCP:

create_app

Performs the structural network allocations setting up reverse-proxy hooks (Nginx/Traefik) preceding the actual codebase transfer. Provision a root App boundary wrapper on the Dokku VM

destroy_app

Instantly shuts down bound running docker containers orchestrating web/worker traffic, detaches volumes seamlessly, and removes explicit DNS routing records from the local VHOST mappings. Deallocate an App and dismantle all bound containers completely

get_logs

Bypasses SSH to investigate explicit request stack traces, crashing node backtraces, or slow SQL queries happening inside the closed containers. Stream Dokku Application Docker stdout and stderr logs

list_apps

Determines exactly which Docker containers are orchestrated internally by Dokku Core scaling plugins. List self-hosted Git-push Apps deployed via Dokku

list_config

env` or `ENV` dictionary bound dynamically via the `dokku config` plugin. Used strictly to observe runtime inputs (SQL credentials, external REST API tokens, Node_ENV bindings) governing app execution. Extract internal Environment variables loaded into the App

ps_restart

Dokku tears down old running docker processes spanning the App UUID, allocating updated dynamic ports tied via standard proxies (Nginx), ensuring zero downtime deploys if multiple replicas are alive. Bounce the application container dynamically

ps_scale

Determines whether the "web" container spins zero replicas (suspension), or if "worker" background tasks spool up to 10 endpoints. Scale structural internal application containers

run_command

Boots a brand new isolated Docker container cloning the production image layers for a single execution cycle. Useful for running `rake db:migrate`, `npm run script` safely disconnected from web traffic. Launch a raw one-off command inside an ephemeral container

set_config

Triggers a mandatory rolling app deployment unless the `--no-restart` daemon flag applies natively to the process. Critical for updating expired API auth tokens. Inject Environment Variables into a running Dokku Application

unset_config

Immediately triggers the executing Docker cluster to orchestrate a rapid replacement cycle to strip out the revoked value. Removes stale credentials safely. Remove sensitive Environment Variables disrupting App config

Example Prompts for Dokku in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Dokku immediately.

"List all apps on my Dokku host"

"Scale the 'web' process of app 'api-server' to 3 replicas"

"Get the last 50 lines of logs for 'frontend-web'"

Troubleshooting Dokku MCP Server with Claude Desktop

Common issues when connecting Dokku to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Dokku + Claude Desktop FAQ

Common questions about integrating Dokku MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.