Dokku Mcp Server

Created By
dokku-MCP8 months ago
This server exposes Dokku's management capabilities through the standardized Model Context Protocol (MCP), allowing Large Language Models (LLMs) to interact with and manage a Dokku instance.
Overview

What is Dokku MCP Server?

Dokku MCP Server is a server that exposes Dokku's management capabilities through the standardized Model Context Protocol (MCP), enabling Large Language Models (LLMs) to interact with and manage a Dokku instance.

How to use Dokku MCP Server?

To use the Dokku MCP Server, follow the installation instructions provided in the documentation or download a prebuilt binary. You can start the server using the command make start if you have Go installed locally.

Key features of Dokku MCP Server?

  • Exposes Dokku management capabilities via MCP.
  • Compatible with any MCP-compatible client.
  • Provides an MCP Inspector Playground for quick testing and validation.

Use cases of Dokku MCP Server?

  1. Managing Dokku instances through LLMs.
  2. Integrating with IDEs and internal tools for enhanced management.
  3. Validating setups before full integration with MCP clients.

FAQ from Dokku MCP Server?

  • Is Dokku MCP Server ready for production use?

No, it is currently in early development and not recommended for production use.

  • How can I connect MCP clients to the server?

You can connect by adding the server configuration to your MCP client configuration files.

Server Config

{
  "mcpServers": {
    "dokku": {
      "command": "/home/user/dokku-mcp/build/dokku-mcp",
      "args": [],
      "env": {
        "DOKKU_MCP_SECURITY_BLACKLIST": "destroy,uninstall,remove",
        "DOKKU_MCP_SSH_HOST": "127.0.0.1",
        "DOKKU_MCP_SSH_KEY_PATH": "/home/user/.ssh/id_rsa",
        "DOKKU_MCP_SSH_PORT": "22",
        "DOKKU_MCP_SSH_USER": "dokku"
      }
    }
  }
}
Project Info
Created At
8 months ago
Updated At
8 months ago
Author Name
dokku-MCP
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago