Log inSubmit server
Dokploy MCP Server logo

Dokploy MCP Server

Manage Dokploy projects, applications, databases, domains, backups, and infrastructure through compact MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Dokploy MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "dokploy-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "dokploy-mcp-server"
      ],
      "env": {
        "DOKPLOY_URL": "YOUR_VALUE_HERE",
        "DOKPLOY_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y dokploy-mcp-server

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 15d ago.

Overview

The dokploy-mcp-server MCP server connects AI assistants to a Dokploy instance through its API, exposing grouped action-based tools for deployment and operations. It covers projects, applications, Docker, Compose, databases, domains, servers, backups, environments, and related infrastructure. Use it when you want broad Dokploy coverage without loading one MCP tool for every API endpoint. It runs over stdio by default and also supports streamable HTTP through Docker.

Use cases

  • Deploy applications through Dokploy
  • Manage Docker Compose stacks and backups
  • Create and operate supported databases
  • Update application environment variables safely
  • Inspect domains, servers, and infrastructure

Key features

  • Action-based tools for Dokploy operations
  • Unified support for six database types
  • Granular environment variable updates
  • Docker, Compose, and deployment management
  • Domain, server, backup, and infrastructure operations
  • stdio and HTTP streaming transports

Tools9

What Dokploy MCP Server lets your agent do. Expand a tool for its parameters.

Self-reported~215 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

8/8 checks healthy over the last 41d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · dokploy-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
npm downloads499Package downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed9Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Dokploy MCP Server works

What dokploy-mcp-server does

The dokploy-mcp-server MCP server gives an AI assistant an action-based interface to Dokploy, the open-source, self-hosted PaaS. It is intended for managing the deployment and operating surface commonly used by self-hosters: projects, applications, Compose stacks, deployments, Docker resources, databases, domains, servers, backups, environments, schedules, mounts, registries, destinations, SSH keys, and infrastructure settings.

The implementation groups related Dokploy API operations into 27 category tools rather than exposing a separate tool for every endpoint. Each category tool uses an action value, with the remaining parameters selected according to that action.

How it works

Requests are sent to a configured Dokploy URL with an API key. The server translates an action-based MCP call into the corresponding Dokploy API operation and returns the result to the assistant. Project listing and retrieval include nested environments and their applications, Compose resources, and databases, which can help an agent discover service IDs before performing follow-up actions.

The unified database tool handles PostgreSQL, MySQL, MariaDB, MongoDB, Redis, and LibSQL through database type and action parameters. Some database actions have type-specific requirements: MongoDB requires databaseUser, Redis requires only databasePassword, and LibSQL requires appName, dockerImage, and an sqldNode value of primary or replica.

Environment variables have separate safer and more explicit operations. setEnvVars performs server-side read-modify-write updates and returns only changed key names in its confirmation. getEnvKeys returns sorted names without values, while getEnvValuesUnsafe exposes the complete KEY=VALUE content in the transcript. saveEnvironment remains available for full replacement workflows.

Setup and configuration

Configure DOKPLOY_URL with the address of the Dokploy instance and DOKPLOY_API_KEY with an API key from Dokploy settings. The standard MCP configuration launches the package with npx -y dokploy-mcp-server and passes those values through the environment.

The default transport is stdio. Set TRANSPORT_TYPE=httpStream for the HTTP streaming mode; PORT controls its port and defaults to 3000, while HOST defaults to 0.0.0.0.

The dokploy-mcp-server MCP server names Claude Desktop, Claude Code, and Cursor as supported setup targets. Cursor uses its .cursor/mcp.json configuration file; Claude clients use their MCP configuration.

Tools and capabilities

The grouped tools cover:

  • Project creation, updates, duplication, lookup, listing, and removal.
  • Application lifecycle and deployment operations, including environment updates.
  • Compose stacks, Docker containers, images, volumes, networks, and volume backups.
  • PostgreSQL, MySQL, MariaDB, MongoDB, Redis, and LibSQL database operations.
  • Domains, redirects, DNS providers, vault providers, registries, and destinations.
  • Server management, web server backups, infrastructure, mounts, and SSH keys.
  • Deployments, preview deployments, schedules, audit logs, settings, and environments.

Compose supports whole-stack backups, and the webServer backup operation handles Dokploy server backups. Status labels such as DONE describe deployment status, not whether a container is currently running; container state should be checked through the Docker container operation.

Limitations and notes

The dokploy-mcp-server MCP server does not represent every Dokploy API endpoint. The README identifies notifications, user and organization administration, roles, SSO and SCIM, Git provider configuration, AI providers, cluster and Swarm operations, patch, tags, rollback, some admin operations, and Dokploy Cloud commercial features as areas without equivalent coverage. Workflows requiring those areas may need Dokploy's official MCP server or both servers.

API behavior may therefore depend on the Dokploy version being operated. Treat getEnvValuesUnsafe as sensitive: returned values enter the tool transcript and may remain in retained agent logs. Prefer key-name inspection and granular updates when full values are not required.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Dokploy MCP Server

dokploy-mcp-server is an MCP server that connects AI assistants to a Dokploy instance through its API. Its main tools manage projects, applications, Docker and Compose resources, six database types, domains, servers, backups, environments, and infrastructure through grouped action-based operations.

Install it by launching `npx -y dokploy-mcp-server` from your MCP client configuration and setting `DOKPLOY_URL` plus `DOKPLOY_API_KEY`. The README provides configurations for Claude Desktop, Claude Code, and Cursor, as well as a Docker command.

Yes, dokploy-mcp-server works with Cursor through `.cursor/mcp.json`. Add the server command, pass `DOKPLOY_URL` and `DOKPLOY_API_KEY` in its environment, and launch it with `npx -y dokploy-mcp-server`.

It provides granular updates through `setEnvVars`, which merges specified keys server-side and confirms only changed key names. `getEnvKeys` returns names without values, while `getEnvValuesUnsafe` returns the full blob and should be used only when those values can enter transcripts or retained logs.

Notifications, user and organization administration, roles, SSO and SCIM, Git provider configuration, AI providers, cluster and Swarm operations, patch, tags, rollback, some admin functions, and Dokploy Cloud commercial features are listed as uncovered areas.

Related MCP servers

All in Cloud Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDokploy MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/dokploy-mcp-server?style=directory)](https://allmcps.com/mcp/dokploy-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/dokploy-mcp-server"><img src="https://allmcps.com/api/badge/dokploy-mcp-server?style=directory" alt="Dokploy MCP Server on AllMCPs" /></a>