2,500+ MCP servers ready to use
Vinkius

Dokku MCP Server for Pydantic AI 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools SDK

Pydantic AI brings type-safe agent development to Python with first-class MCP support. Connect Dokku through Vinkius and every tool is automatically validated against Pydantic schemas. catch errors at build time, not in production.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerHTTP

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    server = MCPServerHTTP(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")

    agent = Agent(
        model="openai:gpt-4o",
        mcp_servers=[server],
        system_prompt=(
            "You are an assistant with access to Dokku "
            "(10 tools)."
        ),
    )

    result = await agent.run(
        "What tools are available in Dokku?"
    )
    print(result.data)

asyncio.run(main())
Dokku
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.

Pydantic AI validates every Dokku tool response against typed schemas, catching data inconsistencies at build time. Connect 10 tools through Vinkius and switch between OpenAI, Anthropic, or Gemini without changing your integration code. full type safety, structured output guarantees, and dependency injection for testable agents.

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 Pydantic AI 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 Pydantic AI via MCP

Follow these steps to integrate the Dokku MCP Server with Pydantic AI.

01

Install Pydantic AI

Run pip install pydantic-ai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.py and run: python agent.py

04

Explore tools

The agent discovers 10 tools from Dokku with type-safe schemas

Why Use Pydantic AI with the Dokku MCP Server

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

01

Full type safety: every MCP tool response is validated against Pydantic models, catching data inconsistencies before they reach your application

02

Model-agnostic architecture. switch between OpenAI, Anthropic, or Gemini without changing your Dokku integration code

03

Structured output guarantee: Pydantic AI ensures tool results conform to defined schemas, eliminating runtime type errors

04

Dependency injection system cleanly separates your Dokku connection logic from agent behavior for testable, maintainable code

Dokku + Pydantic AI Use Cases

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

01

Type-safe data pipelines: query Dokku with guaranteed response schemas, feeding validated data into downstream processing

02

API orchestration: chain multiple Dokku tool calls with Pydantic validation at each step to ensure data integrity end-to-end

03

Production monitoring: build validated alert agents that query Dokku and output structured, schema-compliant notifications

04

Testing and QA: use Pydantic AI's dependency injection to mock Dokku responses and write comprehensive agent tests

Dokku MCP Tools for Pydantic AI (10)

These 10 tools become available when you connect Dokku to Pydantic AI via MCP:

01

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

02

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

03

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

04

list_apps

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

05

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

06

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

07

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

08

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

09

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

10

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 Pydantic AI

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

01

"List all apps on my Dokku host"

02

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

03

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

Troubleshooting Dokku MCP Server with Pydantic AI

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

01

MCPServerHTTP not found

Update: pip install --upgrade pydantic-ai

Dokku + Pydantic AI FAQ

Common questions about integrating Dokku MCP Server with Pydantic AI.

01

How does Pydantic AI discover MCP tools?

Create an MCPServerHTTP instance with the server URL. Pydantic AI connects, discovers all tools, and generates typed Python interfaces automatically.
02

Does Pydantic AI validate MCP tool responses?

Yes. When you define result types as Pydantic models, every tool response is validated against the schema. Invalid data raises a clear error instead of silently corrupting your pipeline.
03

Can I switch LLM providers without changing MCP code?

Absolutely. Pydantic AI abstracts the model layer. your Dokku MCP integration works identically with OpenAI, Anthropic, Google, or any supported provider.

Connect Dokku to Pydantic AI

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.