Dokploy MCP server
✓ VerifiedMemungkinkan AI client untuk mengelola deployment, database, domain, dan log Dokploy melalui interface yang ringkas dan hemat token.
Juga dikenal sebagai vcode-sh/dokploy-mcp, dokploy-mcp, @vibetools/dokploy-mcp
- Stars
- 4
- Tools
- —
- Unduhan, 30 hari
- —
- Versi terbaru
- 4.0.0
- Commit terakhir
- 9 Jul 2026
- Lisensi
- MIT
Apa itu Dokploy MCP?
Dokploy adalah MCP server. Memungkinkan AI client untuk mengelola deployment, database, domain, dan log Dokploy melalui interface yang ringkas dan hemat token.
Ringkasan dibuat dari README proyek
Tentang Dokploy MCP server
Dokploy MCP menyediakan cara bagi AI client seperti Claude Desktop, Cursor, Codex, dan Claude Code untuk berinteraksi dengan Dokploy PaaS. Fokus utamanya adalah efisiensi dengan menggunakan interface ringkas yang secara signifikan mengurangi jumlah token yang dikirim ke context window. Alih-alih mengekspos ratusan skema endpoint secara individual, server ini menggunakan tiga tool utama: search, execute, dan list_profiles. Pendekatan ini memungkinkan server untuk mengelola ratusan prosedur di balik layar dengan tetap menjaga footprint yang kecil.
User dapat menyiapkan server via npx menggunakan DOKPLOY_URL dan DOKPLOY_API_KEY yang didapatkan dari pengaturan Dokploy. Server ini mendukung koneksi stdio lokal dan hosted HTTP metadata. Bagi developer yang mengelola banyak organisasi, environment variable DOKPLOY_PROFILES_JSON memungkinkan konfigurasi beberapa profile bernama. Hal ini memungkinkan AI untuk berpindah antar instance Dokploy dengan mengirimkan nama profile ke tool execute, sehingga mempermudah workflow kompleks untuk deployment, database, domain, dan log tanpa mengekspos kredensial sensitif.
Apa yang bisa Anda lakukan dengannya
- 1Mengelola banyak akun DokployInstruksikan AI untuk melakukan tindakan pada organisasi tertentu menggunakan profile yang sudah dinamai.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal Dokploy MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal Dokploy MCP di Claude Code
$ claude mcp add --env 'DOKPLOY_API_KEY=<YOUR_DOKPLOY_API_KEY>' --env 'DOKPLOY_PROFILES_JSON=<YOUR_DOKPLOY_PROFILES_JSON>' dokploy-mcp -- npx -y @vibetools/dokploy-mcpInstal Dokploy MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"dokploy-mcp": {
"command": "npx",
"args": [
"-y",
"@vibetools/dokploy-mcp"
],
"env": {
"DOKPLOY_API_KEY": "<YOUR_DOKPLOY_API_KEY>",
"DOKPLOY_PROFILES_JSON": "<YOUR_DOKPLOY_PROFILES_JSON>"
}
}
}
}Instal Dokploy MCP di VS Code
.vscode/mcp.json
{
"servers": {
"dokploy-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@vibetools/dokploy-mcp"
],
"env": {
"DOKPLOY_API_KEY": "<YOUR_DOKPLOY_API_KEY>",
"DOKPLOY_PROFILES_JSON": "<YOUR_DOKPLOY_PROFILES_JSON>"
}
}
}
}Instal Dokploy MCP di VS Code CLI
$ code --add-mcp '{"name":"dokploy-mcp","type":"stdio","command":"npx","args":["-y","@vibetools/dokploy-mcp"],"env":{"DOKPLOY_API_KEY":"<YOUR_DOKPLOY_API_KEY>","DOKPLOY_PROFILES_JSON":"<YOUR_DOKPLOY_PROFILES_JSON>"}}'Instal Dokploy MCP di Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"dokploy-mcp": {
"command": "npx",
"args": [
"-y",
"@vibetools/dokploy-mcp"
],
"env": {
"DOKPLOY_API_KEY": "<YOUR_DOKPLOY_API_KEY>",
"DOKPLOY_PROFILES_JSON": "<YOUR_DOKPLOY_PROFILES_JSON>"
}
}
}
}Instal Dokploy MCP di Codex
$ codex mcp add dokploy-mcp --env 'DOKPLOY_API_KEY=<YOUR_DOKPLOY_API_KEY>' --env 'DOKPLOY_PROFILES_JSON=<YOUR_DOKPLOY_PROFILES_JSON>' -- npx -y @vibetools/dokploy-mcpInstal Dokploy MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.dokploy-mcp] command = "npx" args = ["-y", "@vibetools/dokploy-mcp"] [mcp_servers.dokploy-mcp.env] DOKPLOY_API_KEY = "<YOUR_DOKPLOY_API_KEY>" DOKPLOY_PROFILES_JSON = "<YOUR_DOKPLOY_PROFILES_JSON>"
Instal Dokploy MCP di Gemini CLI
$ gemini mcp add -s user -e 'DOKPLOY_API_KEY=<YOUR_DOKPLOY_API_KEY>' -e 'DOKPLOY_PROFILES_JSON=<YOUR_DOKPLOY_PROFILES_JSON>' dokploy-mcp npx -- -y @vibetools/dokploy-mcpInstal Dokploy MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"dokploy-mcp": {
"command": "npx",
"args": [
"-y",
"@vibetools/dokploy-mcp"
],
"env": {
"DOKPLOY_API_KEY": "<YOUR_DOKPLOY_API_KEY>",
"DOKPLOY_PROFILES_JSON": "<YOUR_DOKPLOY_PROFILES_JSON>"
}
}
}
}Konfigurasi
DOKPLOY_API_KEYRahasiaOptional when local Dokploy credentials already exist. Otherwise provide the Dokploy API key.
DOKPLOY_PROFILES_JSONRahasiaOptional JSON object of named Dokploy targets. Use this when you want explicit named profiles in addition to the local default target.
DOKPLOY_URLOptional when local Dokploy credentials already exist. Otherwise provide the Dokploy panel URL.
| Nama | Deskripsi | Tipe |
|---|---|---|
| DOKPLOY_API_KEY | Optional when local Dokploy credentials already exist. Otherwise provide the Dokploy API key. | Rahasia |
| DOKPLOY_PROFILES_JSON | Optional JSON object of named Dokploy targets. Use this when you want explicit named profiles in addition to the local default target. | Rahasia |
| DOKPLOY_URL | Optional when local Dokploy credentials already exist. Otherwise provide the Dokploy panel URL. |
Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks · Yang perlu diperbaiki untuk menambah poin
- Source repository terhubung dan dapat dijangkauvcode-sh/dokploy-mcp is public and reachablegithub.com/vcode-sh/dokploy-mcp ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernya@vibetools/dokploy-mcp names vcode-sh/dokploy-mcp as sourcenpmjs.com/package/@vibetools/dokploy-mcp ↗Lolos
- Provenance build (atestasi Sigstore)Sigstore attestation for @vibetools/dokploy-mcpnpmjs.com/package/@vibetools/dokploy-mcp/v/4.0.0#provenance ↗Lolos
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-07-09github.com/vcode-sh/dokploy-mcp ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerNo popular package one edit away from @vibetools/dokploy-mcpLolos
- Tidak ada advisory kritis pada paket atau dependensinya105 resolved dependencies checked; no critical advisoryosv.dev ↗Lolos
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote merespons handshake MCPEndpoint did not answer initialize: unreachableTemuan
README
Lihat di GitHub@vibetools/dokploy-mcp
MCP server for Dokploy that works cleanly with Codex, Cursor, Claude Code, and Claude Desktop.
Three tools up front. Hundreds of Dokploy procedures underneath. Less schema tax, more actual deploys.
Most MCP servers treat your context window like free landfill. This one starts with
search, execute, and list_profiles, then earns the rest.
What that buys you:
- compact default surface instead of hundreds of raw endpoint tools
- generated, broad Dokploy coverage underneath
- real workflows for deploys, compose, logs, domains, databases, and profiles
- local
stdioplus hosted HTTP metadata in the same package
Need proof instead of a sales monologue? Start with docs/live-e2e-proof.md.
Current Fact Snapshot
- Generated API procedures in the pinned catalog:
544 - Generated tags:
50 - Default public MCP tools:
3(search,execute,list_profiles) - Default
tools/listfootprint from the current budget check: about1,681tokens (6,723bytes) - Reduction versus the classic endpoint-per-tool baseline (
92,354tokens):98.2%
| Classic endpoint-per-tool baseline | Current Code Mode default | |
|---|---|---|
| Tool definitions sent | about 92,354 tokens |
about 1,681 tokens |
| Public MCP tools | hundreds of endpoint schemas | 3 |
| Context window tax | wide schema dump | compact fixed surface |
Quick Start
Get your API key from Dokploy Settings > Profile > API/CLI.
For env-based setup, start from .env.example.
If your client uses a JSON-style MCP config, this is the whole block:
{
"mcpServers": {
"dokploy": {
"command": "npx",
"args": ["@vibetools/dokploy-mcp"],
"env": {
"DOKPLOY_URL": "https://panel.example.com",
"DOKPLOY_API_KEY": "dokp_..."
}
}
}
}
If your client uses CLI-based MCP management:
# Codex
codex mcp add dokploy \
--env DOKPLOY_URL=https://panel.example.com \
--env DOKPLOY_API_KEY=dokp_... \
-- npx @vibetools/dokploy-mcp
# Claude Code
claude mcp add --transport stdio \
-e DOKPLOY_URL=https://panel.example.com \
-e DOKPLOY_API_KEY=dokp_... \
dokploy -- npx @vibetools/dokploy-mcp
Already authenticated with the Dokploy CLI or local
dokploy-mcp config?
You may not need the env block at all.
Using multiple Dokploy organizations?
Keep one compact MCP server and configure profiles with DOKPLOY_PROFILES_JSON:
{
"mcpServers": {
"dokploy": {
"command": "npx",
"args": ["@vibetools/dokploy-mcp"],
"env": {
"DOKPLOY_PROFILES_JSON": "{\"redivo\":{\"url\":\"https://redivo.example.com\",\"apiKey\":\"dokp_redivo\"},\"personal\":{\"url\":\"https://personal.example.com\",\"apiKey\":\"dokp_personal\"},\"mezon\":{\"url\":\"https://mezon.example.com\",\"apiKey\":\"dokp_mezon\"}}"
}
}
}
}
Use list_profiles to see the available default and named profile targets without exposing API
keys. Pass profile to execute when you want a named profile instead of the default target:
{
"profile": "redivo",
"code": "return await dokploy.project.all()"
}
search also accepts an optional profile argument for profile-name validation while preserving
the same compact catalog behavior.
Hosted HTTP sessions keep their request-scoped remote credentials bound to the session. Named local profiles are not exposed there.
Want the wizard path instead of manual config?
npx @vibetools/dokploy-mcp setup
Pick Your Client
What You Actually Get
search: discover Dokploy procedures and contractsexecute: run multi-step workflows in one sandboxed calllist_profiles: list configured Dokploy profile names and URLs without secrets- optional
rawmode: one tool per procedure - optional
hybridmode: Code Mode plus selected raw tools - optional hosted HTTP path with
server.jsonmetadata and header-based remote auth
If you are new, use the default mode and stop trying to outsmart a problem that already has a working shape.
Read These Next
- docs/getting-started.md
- docs/guides/profiles.md
- docs/guides/modes.md
- docs/guides/compose.md
- docs/guides/hosted-http.md
- docs/guides/hosted-deploy.md
- docs/guides/troubleshooting.md
- docs/live-e2e-proof.md
CLI
npx @vibetools/dokploy-mcp
npx @vibetools/dokploy-mcp serve-stdio
npx @vibetools/dokploy-mcp serve-http
npx @vibetools/dokploy-mcp setup
npx @vibetools/dokploy-mcp version
Development
git clone https://github.com/vcode-sh/dokploy-mcp.git && cd dokploy-mcp
npm install
npm run build
npm run lint
npm test
npm run docs:check:facts
The rest lives in docs, where it belongs.
Credits
Forked from Dokploy/mcp. Started at 67 tools, mass-refactored to 377, then rebuilt the whole thing into an architecture that makes the tool count irrelevant.
Mauricio Siu built Dokploy itself -- the PaaS this server talks to. Without the platform, this is a very elaborate way to POST into the void.
Henrique Andrade wrote the original MCP server. 15 commits, every PR merged. The kind of contributor who closes issues instead of opening them.
Contributors who shaped the original: Joshua Macauley -- lucasleal-developer -- Nour Eddine Hamaidi -- Corey -- Azil0ne
Unmerged PRs are still blueprints. That's how open source works -- stolen inspiration with better commit messages.
License
MIT - Vibe Code
Original work by Henrique Andrade under Apache 2.0 -- see LICENSE-ORIGINAL.
Pertanyaan tentang Dokploy MCP
Bagaimana cara menambahkan Dokploy MCP ke Claude Code?
Jalankan claude mcp add --env 'DOKPLOY_API_KEY=<YOUR_DOKPLOY_API_KEY>' --env 'DOKPLOY_PROFILES_JSON=<YOUR_DOKPLOY_PROFILES_JSON>' dokploy-mcp -- npx -y @vibetools/dokploy-mcp di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan Dokploy MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Di mana saya bisa menemukan API key saya?
API key Anda dapat ditemukan di dashboard Dokploy pada bagian Settings > Profile > API/CLI.
Apakah saya bisa mengelola beberapa organisasi Dokploy?
Ya, Anda bisa mengonfigurasi beberapa profile menggunakan environment variable DOKPLOY_PROFILES_JSON untuk berpindah antar target yang berbeda.
Tool apa saja yang tersedia secara default?
Server ini menyediakan tiga default public tools: search, execute, dan list_profiles.