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 AutoGen 10 tools — connect in under 2 minutes

Name: Dokku
Availability: InStock
Author: Vinkius

microsoft.github.io/autogen/docs/tools/mcp-tools

Built by Vinkius GDPR 10 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add Dokku as an MCP tool provider through Vinkius and every agent in the group can access live data and take action.

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.

python

import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="dokku_agent",
            tools=tools,
            system_message=(
                "You help users with Dokku. "
                "10 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())

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.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Dokku tools. Connect 10 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

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 AutoGen 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 AutoGen via MCP

Follow these steps to integrate the Dokku MCP Server with AutoGen.

Install AutoGen

Run pip install "autogen-ext[mcp]"

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

Explore tools

The workbench discovers 10 tools from Dokku automatically

Why Use AutoGen with the Dokku MCP Server

AutoGen provides unique advantages when paired with Dokku through the Model Context Protocol.

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Dokku tools to solve complex tasks

Role-based architecture lets you assign Dokku tool access to specific agents. a data analyst queries while a reviewer validates

Human-in-the-loop support: agents can pause for human approval before executing sensitive Dokku tool calls

Code execution sandbox: AutoGen agents can write and run code that processes Dokku tool responses in an isolated environment

Dokku + AutoGen Use Cases

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

Collaborative analysis: one agent queries Dokku while another validates results and a third generates the final report

Automated review pipelines: a researcher agent fetches data from Dokku, a critic agent evaluates quality, and a writer produces the output

Interactive planning: agents negotiate task allocation using Dokku data to make informed decisions about resource distribution

Code generation with live data: an AutoGen coder agent writes scripts that process Dokku responses in a sandboxed execution environment

Dokku MCP Tools for AutoGen (10)

These 10 tools become available when you connect Dokku to AutoGen 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 AutoGen

Ready-to-use prompts you can give your AutoGen 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 AutoGen

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

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

Dokku + AutoGen FAQ

Common questions about integrating Dokku MCP Server with AutoGen.

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Dokku tools during their conversation turns.

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.