Dokploy MCP Server

Official

Manage Dokploy through MCP.

How to install ↓ Compare GitHub source repository ↗

Category: Dev Tools #315 of 438
Stars: ★ 401 Very popular
Transport: stdio (local process) · Streamable HTTP · SSE
Runtime: Node.js 18+ · Docker
Credentials: API key / credential required
License: Other / unspecified
Last commit: 33 days ago

44FMRS · D

The source identifies this as Dokploy's official MCP package, supporting stdio, Streamable HTTP, and legacy SSE transports with API-token authentication. Because the server manifest was not cached and the source does not list concrete tool identifiers, no tool identifiers are included.

Strongest · Setup experience 13/20 Weakest · Security and permissions 4/20

Reliability

8/20

Security and permissions

4/20

Maintenance

6/20

Documentation

13/20

Setup experience

13/20

Why each score

Reliability 8/20: The README claims 508 tools, stdio and HTTP transports, retries, and centralized error handling, but the server manifest is unavailable and no source files, CI, or committed tests are provided to verify initialization, the tool-list handshake, or consistency between generated tools and real behavior. The happy path is plausible, but key paths and edge failures are unverified, so points are deducted.
Security and permissions 4/20: This triggers a red-line concern: the server exposes the full Dokploy API, including deletion, deployment, remote infrastructure, user, key, billing, and license operations. The material does not establish confirmation before dangerous actions or least-privilege, fine-grained authorization. API keys are passed through environment variables, response redaction is opt-in and disabled by default, and HTTP authentication/access control is not documented. There is no evidence of credential theft or malicious exfiltration, but the broad authority and missing confirmation evidence warrant the red-line score of 4.
Maintenance 6/20: The repository is not archived and has some public activity signals, but stars and open issues are the only maintenance evidence supplied. There is no evidence of release cadence, commit activity, dependency updates, CI, maintainer accountability, or a security-response channel. The metadata says NOASSERTION for the license while the README claims Apache License, so licensing remains unverified; only limited maintenance credit is justified.
Documentation 13/20: The README covers several clients, Node/Bun/Deno/Docker installation paths, environment variables, transport endpoints, tool categories, filtering, and basic troubleshooting, which supports initial use. Deductions apply because the manifest is missing, per-tool parameters and permissions are not documented, limits/costs and secure HTTP deployment are not clearly addressed, and implementation evidence is absent; capability claims rely on the README alone.
Setup experience 13/20: npx, bunx, Deno, Docker, and multiple mainstream client configurations are documented, along with runtime requirements, required environment variables, and stdio/HTTP modes. The setup still requires an existing Dokploy instance and API token; HTTP production authentication and TLS details are missing, and there is no source-level execution evidence. It is reasonably clear but remains manually configured and only partially verifiable.

Static review · not runListed 2026-07-29

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkChanges third-party account dataConnects to a database

Best for

Teams already operating Dokploy and needing API automation
Developers who want centralized Dokploy resource management in an MCP client

Not for

Users without a Dokploy server or API token
Use cases requiring management of platforms other than Dokploy without a corresponding API

Required permissions

Access to the Dokploy server URL is required
A Dokploy API authentication token is required
Depending on the API operation, the server may have permission to create, modify, deploy, stop, delete, and manage security-sensitive resources

Risks and side effects

The server exposes a broad range of Dokploy API operations, including potentially destructive deployment, stop, deletion, password, and security actions
API responses may contain environment variables, tokens, passwords, or other sensitive fields; set DOKPLOY_REDACT_ENV=true to redact them
Protect DOKPLOY_API_KEY and any service tokens supplied through DOKPLOY_CUSTOM_HEADERS

Setup

Before you start

Runtime：Node.js 18+ · Docker

DOKPLOY_URL required Your Dokploy server URL, e.g. https://your-dokploy-server.com.

DOKPLOY_API_KEY requiredsecret Dokploy API authentication token, generated in your running Dokploy instance's user settings.

DOKPLOY_CUSTOM_HEADERS optionalsecret Optional JSON object of extra upstream request headers, e.g. Cloudflare Access service tokens; cannot override x-api-key, content-type, or accept.

Other optional settings (8)

DOKPLOY_TOOL_PRESET optional Optional predefined toolset: all (default), minimal, core, deploy, databases, git.

DOKPLOY_ENABLED_TAGS optional Optional comma-separated tags to load only those tool categories.

DOKPLOY_DISABLED_TAGS optional Optional comma-separated tags to exclude from the selected toolset.

DOKPLOY_TIMEOUT optional Optional request timeout in milliseconds, default 30000.

DOKPLOY_RETRY_ATTEMPTS optional Optional number of retry attempts, default 3.

DOKPLOY_RETRY_DELAY optional Optional delay between retries in milliseconds, default 1000.

DOKPLOY_REDACT_ENV optional Optional, redact secret-bearing fields from API responses before they reach the client, default true.

DOKPLOY_REDACT_FIELDS optional Optional comma-separated list of response field names to redact.

Use Node.js 18 or later and have a running Dokploy server. Add the supplied JSON configuration to an MCP client and set DOKPLOY_URL and DOKPLOY_API_KEY. Bun, Deno, Docker, and HTTP-mode deployments are also documented.

.cursor/mcp.json

{"mcpServers":{"dokploy-mcp":{"command":"npx","args":["-y","@dokploy/mcp"],"env":{"DOKPLOY_URL":"https://your-dokploy-server.com","DOKPLOY_API_KEY":"your-dokploy-api-token"}}}}

Shown for Cursor. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json

{
  "servers": {
    "dokploy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dokploy/mcp"
      ],
      "env": {
        "DOKPLOY_URL": "https://your-dokploy-server.com",
        "DOKPLOY_API_KEY": "your-dokploy-api-token"
      }
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal

claude mcp add dokploy-mcp -e DOKPLOY_URL=https://your-dokploy-server.com -e DOKPLOY_API_KEY=your-dokploy-api-token -- npx -y @dokploy/mcp

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

The client's tool list should show tools from dokploy-mcp (508 by default, or fewer with DOKPLOY_TOOL_PRESET=minimal). Ask "list my projects" — a real project list confirms DOKPLOY_URL and DOKPLOY_API_KEY are correctly configured.

Troubleshooting

Confirm that Node.js is version 18 or later
Verify DOKPLOY_URL and DOKPLOY_API_KEY and ensure the Dokploy server is running
Use DOKPLOY_ENABLED_TAGS to filter categories if too many tools load
Check timeout and retry environment variables
Try @latest and use MCP Inspector when connection diagnosis is needed

Things to try

Once connected, you can ask your AI assistant things like:

List all projects on my Dokploy server
Create and deploy a new PostgreSQL database
Redeploy an application and show its deployment history
Check my server metrics and run Docker cleanup

Use cases

Manage Dokploy project and application lifecycles through an AI client

Operate databases, backups, domains, notifications, and infrastructure settings

Connect Dokploy to MCP clients over stdio or HTTP

Supported clients

Cursor

Windsurf

VS Code

Claude Code

Zed

Claude Desktop

BoltAI

Listed from the project's documentation, not tested by this site.

Overview

The official Dokploy MCP package exposes Dokploy API endpoints as tools for MCP-compatible clients. The README states that it provides 508 tools across 49 categories, covering projects, applications, Compose, databases, servers, Docker, clusters, security, backups, notifications, Git providers, billing, and other Dokploy functions.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 63.3k · Tools 2 Compare with this →

NPM Sentinel MCP Server 79 · B

AI-powered NPM package analysis MCP server

★ 18 · Tools 19 Compare with this →

MartinLoop MCP Server 79 · B

An independent control layer that gives AI coding agents budgets, brakes, and receipts

★ 413 Compare with this →

GitHub MCP Server 76 · B

GitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language

★ 33.7k · Tools 15 Compare with this →

Compare with other MCP servers

Source revision 26799a777e44 Data synced 2026-10-19 Read the FMRS scoring method