모든 Dokploy API 엔드포인트를 도구로 노출하여 AI 클라이언트가 프로젝트, 애플리케이션, 데이터베이스 및 Docker 설정을 관리할 수 있도록 합니다.
다른 이름 Dokploy/mcp, @ahdev/dokploy-mcp, @dokploy/mcp, nd-dokploy-mcp
- 스타
- 431
- Tools
- 6
- 다운로드, 30일
- 11,515
- 최신 버전
- —
- 마지막 커밋
- 2026년 11월 13일
- 라이선스
- —
Dokploy MCP란?
모든 Dokploy API 엔드포인트를 도구로 노출하여 AI 클라이언트가 프로젝트, 애플리케이션, 데이터베이스 및 Docker 설정을 관리할 수 있도록 합니다. 6개 도구를 제공합니다. 예: all, minimal, core.
프로젝트 README에서 생성된 요약
Dokploy MCP server 정보
이 서버는 모든 Dokploy API 엔드포인트를 도구로 노출하여 AI 기반 인터페이스를 통해 인프라와 배포를 관리할 수 있게 합니다. Claude Desktop, Cursor, VS Code, Windsurf, Zed와 같은 MCP 호환 클라이언트를 사용하는 개발자가 Dokploy 인스턴스를 프로그래밍 방식으로 제어할 수 있도록 설계되었습니다. Dokploy 서버에 연결하면 AI 클라이언트가 49개의 다양한 카테고리에 걸친 복잡한 작업을 처리할 수 있습니다.
사용자는 npx, bunx, Deno를 사용하여 서버를 설정하거나 Docker를 통해 stdio 또는 HTTP 트랜스포트 모드로 실행할 수 있습니다. 서버가 작동하려면 DOKPLOY_URL 및 DOKPLOY_API_KEY 환경 변수가 필요합니다. 프로젝트, 애플리케이션, 데이터베이스, Docker 설정, 백업 및 SSO 설정에 대해 광범위한 제어 기능을 제공합니다. 보안을 위해 서버에는 기본적으로 비밀번호나 토큰과 같은 민감한 필드를 AI 컨텍스트에서 숨기는 redaction 기능이 포함되어 있습니다.
활용 사례
- 1자동화된 인프라 관리AI 클라이언트가 프로젝트, 애플리케이션, 데이터베이스를 포함한 전체 배포 라이프사이클을 관리할 수 있습니다.
- 2안전한 API 상호작용개발자는 내장된 redaction 기능을 사용하여 민감한 자격 증명이 LLM으로 전송되는 것을 방지할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Dokploy MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Dokploy MCP 설치
$ claude mcp add mcp -- npx -y @ahdev/dokploy-mcpCursor에 Dokploy MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@ahdev/dokploy-mcp"
]
}
}
}VS Code에 Dokploy MCP 설치
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ahdev/dokploy-mcp"
]
}
}
}VS Code CLI에 Dokploy MCP 설치
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@ahdev/dokploy-mcp"]}'Claude Desktop에 Dokploy MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@ahdev/dokploy-mcp"
]
}
}
}Codex에 Dokploy MCP 설치
$ codex mcp add mcp -- npx -y @ahdev/dokploy-mcpCodex config.toml에 Dokploy MCP 설치
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@ahdev/dokploy-mcp"]
Gemini CLI에 Dokploy MCP 설치
$ gemini mcp add -s user mcp npx -- -y @ahdev/dokploy-mcpGemini settings.json에 Dokploy MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@ahdev/dokploy-mcp"
]
}
}
}시작하려면 키가 필요
2026년 11월 16일에 키 없이 실행하자 멈추고 키를 요구했습니다. 위 변수를 설정하기 전까지 클라이언트에는 도구가 보이지 않습니다.
Dokploy MCP 도구 6
README에서 감지됨allminimalcoredeploydatabasesgit
| all | — | |
| minimal | — | |
| core | — | |
| deploy | — | |
| databases | — | |
| git | — |
구성
DOKPLOY_API_KEYDOKPLOY_CUSTOM_HEADERSDOKPLOY_DISABLED_TAGSDOKPLOY_ENABLED_TAGSDOKPLOY_TOOL_PRESETDOKPLOY_URLMCP_TRANSPORT
| 이름 | 설명 | 유형 |
|---|---|---|
| DOKPLOY_API_KEY | — | |
| DOKPLOY_CUSTOM_HEADERS | — | |
| DOKPLOY_DISABLED_TAGS | — | |
| DOKPLOY_ENABLED_TAGS | — | |
| DOKPLOY_TOOL_PRESET | — | |
| DOKPLOY_URL | — | |
| MCP_TRANSPORT | — |
자동 검사
2026년 11월 12일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능통과
- 오픈 소스 라이선스 (OSI)No license결함 발견
- 최근 1년 내 커밋 또는 릴리스통과
- 패키지 이름이 인기 패키지와 유사하지 않음통과
- 원격 엔드포인트가 HTTPS 사용검사되지 않음
- 파괴적인 도구에 라벨 표시됨통과
- 모델에 대한 숨겨진 지침 없음통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
README
GitHub에서 보기Dokploy MCP Server
Dokploy MCP Server exposes all Dokploy API endpoints as tools consumable via the Model Context Protocol (MCP). It allows MCP-compatible clients (e.g., AI models, other applications) to interact with your Dokploy server programmatically.
With 508 tools across 49 categories, this server provides complete coverage of the Dokploy API — from project and application management to databases, notifications, SSO, Docker, backups, and more.
Getting Started
Requirements
- Node.js >= v18.0.0 (or Docker)
- Cursor, VS Code, Claude Desktop, or another MCP Client
- A running Dokploy server instance
Install in Cursor
Go to: Settings -> Cursor Settings -> MCP -> Add new global MCP server
Add this to your Cursor ~/.cursor/mcp.json file. You may also install in a specific project by creating .cursor/mcp.json in your project folder. See Cursor MCP docs for more info.
{
"mcpServers": {
"dokploy-mcp": {
"command": "npx",
"args": ["-y", "@dokploy/mcp"],
"env": {
"DOKPLOY_URL": "https://your-dokploy-server.com",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
}
}
}
}
{
"mcpServers": {
"dokploy-mcp": {
"command": "bunx",
"args": ["-y", "@dokploy/mcp"],
"env": {
"DOKPLOY_URL": "https://your-dokploy-server.com",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
}
}
}
}
{
"mcpServers": {
"dokploy-mcp": {
"command": "deno",
"args": ["run", "--allow-env", "--allow-net", "npm:@dokploy/mcp"],
"env": {
"DOKPLOY_URL": "https://your-dokploy-server.com",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
}
}
}
}
Install in Windsurf
Add this to your Windsurf MCP config file. See Windsurf MCP docs for more info.
{
"mcpServers": {
"dokploy-mcp": {
"command": "npx",
"args": ["-y", "@dokploy/mcp"],
"env": {
"DOKPLOY_URL": "https://your-dokploy-server.com",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
}
}
}
}
Install in VS Code
Add this to your VS Code MCP config file. See VS Code MCP docs for more info.
{
"servers": {
"dokploy-mcp": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@dokploy/mcp"],
"env": {
"DOKPLOY_URL": "https://your-dokploy-server.com",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
}
}
}
}
Install in Claude Code
Add the MCP server to Claude Code using the CLI:
claude mcp add dokploy-mcp -- npx -y @dokploy/mcp
Then set the environment variables in your .claude/settings.json or pass them inline:
DOKPLOY_URL=https://your-dokploy-server.com DOKPLOY_API_KEY=your-token claude
Install in Zed
Add this to your Zed settings.json. See Zed Context Server docs for more info.
{
"context_servers": {
"dokploy-mcp": {
"command": "npx",
"args": ["-y", "@dokploy/mcp"],
"env": {
"DOKPLOY_URL": "https://your-dokploy-server.com",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
}
}
}
}
Install in Claude Desktop
Add this to your Claude Desktop claude_desktop_config.json file. See Claude Desktop MCP docs for more info.
{
"mcpServers": {
"dokploy-mcp": {
"command": "npx",
"args": ["-y", "@dokploy/mcp"],
"env": {
"DOKPLOY_URL": "https://your-dokploy-server.com",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
}
}
}
}
Install in BoltAI
Open the "Settings" page of the app, navigate to "Plugins," and enter the following 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"
}
}
}
}
Install in Opencode
Add this to your OpenCode configuration (located by default in ~/.config/opencode/opencode.json or opencode.json for local/project config). See Opencode MCP config for more info.
{
"mcp": {
"dokploy": {
"type": "local",
"command": ["npx", "-y", "@dokploy/mcp"],
"environment": {
"DOKPLOY_URL": "https://your-dokploy-server.com",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
},
"enabled": true
}
}
}
Using Docker
The Docker container supports both stdio and HTTP transport modes, making it flexible for different deployment scenarios.
-
Build the Docker Image:
git clone https://github.com/Dokploy/mcp.git cd mcp docker build -t dokploy-mcp . -
Manual Docker Commands:
Stdio Mode (for MCP clients):
docker run -it --rm \ -e DOKPLOY_URL=https://your-dokploy-server.com \ -e DOKPLOY_API_KEY=your_token_here \ dokploy-mcpHTTP Mode (for web applications):
docker run -it --rm \ -p 8080:3000 \ -e MCP_TRANSPORT=http \ -e DOKPLOY_URL=https://your-dokploy-server.com \ -e DOKPLOY_API_KEY=your_token_here \ dokploy-mcp -
Docker Compose:
Use the provided
docker-compose.ymlfor production deployments:# Start HTTP service docker-compose up -d dokploy-mcp-http # View logs docker-compose logs -f dokploy-mcp-http -
MCP Client Configuration:
For stdio mode (Claude Desktop, VS Code, etc.):
{ "mcpServers": { "dokploy-mcp": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "DOKPLOY_URL=https://your-dokploy-server.com", "-e", "DOKPLOY_API_KEY=your_token_here", "dokploy-mcp" ] } } }For HTTP mode (web applications):
Start the HTTP server first, then configure your client to connect to
http://localhost:3000/mcp.
Install in Windows
The configuration on Windows is slightly different compared to Linux or macOS. Use cmd as the command wrapper:
{
"mcpServers": {
"dokploy-mcp": {
"command": "cmd",
"args": ["/c", "npx", "-y", "@dokploy/mcp"],
"env": {
"DOKPLOY_URL": "https://your-dokploy-server.com",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
}
}
}
}
Environment Variables
| Variable | Required | Description |
|---|---|---|
DOKPLOY_URL |
Yes | Your Dokploy server URL (e.g., https://your-dokploy-server.com) |
DOKPLOY_API_KEY |
Yes | Your Dokploy API authentication token |
DOKPLOY_CUSTOM_HEADERS |
No | JSON object of additional upstream request headers. Header names and values must be strings. Reserved headers cannot be set here: x-api-key, content-type, accept. |
DOKPLOY_TOOL_PRESET |
No | Predefined toolset to load: all (default), minimal, core, deploy, databases, or git. Useful for clients/providers that struggle with very large tool lists. |
DOKPLOY_ENABLED_TAGS |
No | Comma-separated list of tags to filter which tools are loaded (e.g., project,application,postgres) |
DOKPLOY_DISABLED_TAGS |
No | Comma-separated list of tags to exclude from the selected toolset. Applied after DOKPLOY_TOOL_PRESET or DOKPLOY_ENABLED_TAGS. |
DOKPLOY_TIMEOUT |
No | Request timeout in milliseconds (default: 30000) |
DOKPLOY_RETRY_ATTEMPTS |
No | Number of retry attempts (default: 3) |
DOKPLOY_RETRY_DELAY |
No | Delay between retries in milliseconds (default: 1000) |
DOKPLOY_REDACT_ENV |
No | Redacts secret-bearing fields (env vars, compose files, passwords, tokens, keys) from API responses before they reach the MCP client (default: true). Set to false only if you explicitly need raw secret values in LLM context. |
DOKPLOY_REDACT_FIELDS |
No | Comma-separated list of response field names to redact when DOKPLOY_REDACT_ENV=true. Matched case-insensitively at any nesting depth. Defaults to: env, buildArgs, composeFile, dockerCompose, environment, buildSecrets, previewBuildSecrets, password, currentPassword, appPassword, databasePassword, databaseRootPassword, redisPassword, mariadbPassword, mongoPassword, mysqlPassword, postgresPassword, registryPassword, token, accessToken, appToken, apiToken, botToken, refreshToken, secret, clientSecret, apiKey, secretAccessKey, accessKey, licenseKey, userKey, privateKey, privateKeyPass, encPrivateKey, encPrivateKeyPass, sshKey, sshPrivateKey, customGitSSHKey, dockerAuth. |
For Dokploy instances behind Cloudflare Access or a similar reverse proxy, pass service-token headers with placeholder values like this:
DOKPLOY_CUSTOM_HEADERS='{"CF-Access-Client-Id":"your-client-id.access","CF-Access-Client-Secret":"your-client-secret"}'
Transport Modes
This MCP server supports multiple transport modes to suit different use cases:
Stdio Mode (Default)
The default mode uses stdio for direct process communication, ideal for desktop applications and command-line usage.
# Run with stdio (default)
npx -y @dokploy/mcp
HTTP Mode (Streamable HTTP + Legacy SSE)
Modern HTTP mode exposes the server via HTTP/HTTPS supporting both modern and legacy protocols for maximum compatibility:
- Streamable HTTP (MCP 2025-03-26) - Modern protocol with session management
- Legacy SSE (MCP 2024-11-05) - Backwards compatibility for older clients
# Run with HTTP mode
npx -y @dokploy/mcp --http
# or via environment variable
MCP_TRANSPORT=http npx -y @dokploy/mcp
Modern Streamable HTTP Endpoints:
| Endpoint | Method | Description |
|---|---|---|
/mcp |
POST | Client-to-server requests |
/mcp |
GET | Server-to-client notifications (SSE) |
/mcp |
DELETE | Session termination |
/health |
GET | Health check |
Legacy SSE Endpoints (Backwards Compatibility):
| Endpoint | Method | Description |
|---|---|---|
/sse |
GET | SSE stream initialization |
/messages |
POST | Client message posting |
Available Tools (508)
This MCP server provides 508 tools covering the entire Dokploy API, organized into 49 categories:
Core Resources
| Category | Tools | Description |
|---|---|---|
| Project | 8 | Create, list, update, duplicate, search, and delete projects |
| Application | 30 | Full application lifecycle — create, deploy, redeploy, start, stop, build types, git providers (GitHub, GitLab, Bitbucket, Gitea), environment, Traefik config |
| Compose | 29 | Docker Compose management — create, deploy, templates, services, environment, isolated deployments |
| Domain | 9 | Domain CRUD, DNS validation, Traefik.me generation |
| Environment | 7 | Multi-environment support per project |
| Deployment | 8 | Deployment history, queue management, centralized view |
Databases
| Category | Tools | Description |
|---|---|---|
| PostgreSQL | 15 | Full lifecycle — create, deploy, start, stop, rebuild, passwords, external ports, environment |
| MySQL | 15 | Full lifecycle — create, deploy, start, stop, rebuild, passwords, external ports, environment |
| MariaDB | 15 | Full lifecycle — create, deploy, start, stop, rebuild, passwords, external ports, environment |
| MongoDB | 15 | Full lifecycle — create, deploy, start, stop, rebuild, passwords, external ports, environment |
| Redis | 15 | Full lifecycle — create, deploy, start, stop, rebuild, passwords, external ports, environment |
| LibSQL | 13 | Full lifecycle — create, deploy, start, stop, rebuild, external ports, environment |
Infrastructure
| Category | Tools | Description |
|---|---|---|
| Server | 17 | Multi-server management, metrics, security, monitoring setup |
| Docker | 9 | Container management — list, restart, remove, upload files, inspect config |
| Cluster / Swarm | 8 | Swarm node management, container stats, cluster operations |
| Settings | 51 | Server settings, Traefik config, Docker cleanup, GPU, monitoring, Redis, disk usage |
| Registry | 7 | Docker registry management and testing |
Security & Auth
| Category | Tools | Description |
|---|---|---|
| SSO | 10 | Single sign-on providers, trusted origins |
| SSH Keys | 7 | SSH key management — create, generate, list, update, remove |
| Certificates | 5 | SSL/TLS certificate management |
| Security | 4 | Basic auth and security rules per application |
| Custom Roles | 6 | Role-based access control with custom permissions |
| User | 23 | User management, permissions, API keys, invitations, metrics |
| Organization | 11 | Multi-org support, invitations, member roles |
Operations
| Category | Tools | Description |
|---|---|---|
| Backup | 12 | Database backups — Postgres, MySQL, MariaDB, MongoDB, LibSQL, Compose, WebServer |
| Volume Backups | 6 | Volume-level backup scheduling and management |
| Destination | 6 | S3-compatible backup destinations (AWS, Cloudflare R2, etc.) |
| Schedule | 6 | Scheduled tasks — cron-based automation |
| Notification | 41 | Multi-channel alerts — Slack, Discord, Telegram, Email, Teams, Gotify, Ntfy, Pushover, Lark, Mattermost, Resend, Custom webhooks |
| Rollback | 2 | Application rollback management |
Other
| Category | Tools | Description |
|---|---|---|
| AI | 9 | AI-powered suggestions, model management |
| Git Providers | 27 | GitHub, GitLab, Gitea, Bitbucket — branches, repos, connection testing |
| Tag | 8 | Project tagging and bulk assignment |
| Patch | 12 | File patching system for applications |
| Mounts | 6 | Volume and bind mount management |
| Port | 4 | Port mapping configuration |
| Redirects | 4 | URL redirect rules |
| Preview Deployments | 4 | PR preview deployment management |
| Stripe | 7 | Billing and subscription management |
| License Key | 6 | Enterprise license management |
| Whitelabeling | 4 | Custom branding for enterprise |
| Audit Log | 1 | Activity audit trail |
| Admin | 1 | Admin-level monitoring setup |
Tool Filtering
By default, the server exposes all Dokploy API tools. Some MCP clients and LLM providers can be slower or less reliable when very large tool lists are sent to the model. You can reduce the loaded tools with presets or tag filters.
Use DOKPLOY_TOOL_PRESET for common workflows:
| Preset | Included tags |
|---|---|
all |
All tools (default) |
minimal |
project, application |
core |
project, server, application |
deploy |
project, environment, server, application, compose, domain, deployment |
databases |
postgres, redis, mysql, mariadb, mongo, libsql |
git |
github, gitlab, bitbucket, gitea, gitProvider, registry, sshKey |
# Recommended starting point for clients/providers sensitive to large toolsets
DOKPLOY_TOOL_PRESET=minimal
For exact control, set DOKPLOY_ENABLED_TAGS:
# Only load project, application, and postgres tools
DOKPLOY_ENABLED_TAGS=project,application,postgres
You can also remove categories from a preset:
DOKPLOY_TOOL_PRESET=core
DOKPLOY_DISABLED_TAGS=postgres,redis
If DOKPLOY_ENABLED_TAGS is set, it takes precedence over DOKPLOY_TOOL_PRESET. DOKPLOY_DISABLED_TAGS is applied last.
All tools include semantic annotations (readOnlyHint, destructiveHint, idempotentHint) to help MCP clients understand their behavior and safety characteristics.
Architecture
Built with @modelcontextprotocol/sdk, TypeScript, and Zod for type-safe schema validation:
- 508 Tools covering the entire Dokploy API
- Multiple Transports: Stdio (default) and HTTP (Streamable HTTP + legacy SSE)
- Auto-generated Tools: Tools are generated from the Dokploy OpenAPI spec via
pnpm generate:all - Tool Filtering: Load only the categories you need via
DOKPLOY_ENABLED_TAGS - Robust Error Handling: Centralized API client with interceptors and retry logic
- Type Safety: Full TypeScript with Zod schema validation
- Tool Annotations: Semantic hints for MCP client behavior understanding
Development
Clone the project and install dependencies:
git clone https://github.com/Dokploy/mcp.git
cd mcp
pnpm install
Build:
pnpm build
Regenerate tools from the Dokploy OpenAPI spec:
pnpm generate:all
Local Configuration Example
{
"mcpServers": {
"dokploy-mcp": {
"command": "npx",
"args": ["tsx", "/path/to/mcp/src/index.ts"],
"env": {
"DOKPLOY_URL": "https://your-dokploy-server.com",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
}
}
}
}
Testing with MCP Inspector
npx -y @modelcontextprotocol/inspector npx @dokploy/mcp
Troubleshooting
MCP Client Errors
-
Try adding
@latestto the package name. -
Make sure you are using Node v18 or higher to have native fetch support with
npx. -
Verify your
DOKPLOY_URLandDOKPLOY_API_KEYenvironment variables are correctly set. -
If too many tools are loading or your provider times out while processing tools, start with
DOKPLOY_TOOL_PRESET=minimal, then useDOKPLOY_ENABLED_TAGSfor exact category filtering if needed.
Contributing
We welcome contributions! If you'd like to contribute to the Dokploy MCP Server, please check out our Contributing Guide.
Support
If you encounter any issues, have questions, or want to suggest a feature, please open an issue in our GitHub repository.
License
This project is licensed under the Apache License.
Dokploy MCP 질문
Dokploy MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add mcp -- npx -y @ahdev/dokploy-mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Dokploy MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Dokploy MCP는 어떤 도구를 제공하나요?
6개 도구를 제공합니다. 예: all, minimal, core, deploy, databases.
이 서버가 HTTP 트랜스포트를 지원하나요?
네, 데스크톱 애플리케이션을 위한 stdio와 최신 Streamable HTTP 및 기존 SSE를 포함하여 웹 애플리케이션을 위한 HTTP/HTTPS를 모두 지원합니다.