{
  "markdown": "# @vibetools/dokploy-mcp\n\n[![npm version](https://img.shields.io/npm/v/@vibetools/dokploy-mcp)](https://www.npmjs.com/package/@vibetools/dokploy-mcp)\n[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)\n[![Node >= 24](https://img.shields.io/badge/node-%3E%3D24-brightgreen)](https://nodejs.org/)\n\nMCP server for [Dokploy](https://dokploy.com) that works cleanly with Codex, Cursor, Claude Code,\nand Claude Desktop.\n\nThree tools up front. Hundreds of Dokploy procedures underneath. Less schema tax, more actual\ndeploys.\n\nMost MCP servers treat your context window like free landfill. This one starts with\n`search`, `execute`, and `list_profiles`, then earns the rest.\n\nWhat that buys you:\n\n- compact default surface instead of hundreds of raw endpoint tools\n- generated, broad Dokploy coverage underneath\n- real workflows for deploys, compose, logs, domains, databases, and profiles\n- local `stdio` plus hosted HTTP metadata in the same package\n\nNeed proof instead of a sales monologue? Start with [docs/live-e2e-proof.md](./docs/live-e2e-proof.md).\n\n<!-- docs-facts:readme:start -->\n## Current Fact Snapshot\n\n- Generated API procedures in the pinned catalog: `544`\n- Generated tags: `50`\n- Default public MCP tools: `3` (`search`, `execute`, `list_profiles`)\n- Default `tools/list` footprint from the current budget check: about `1,681` tokens (`6,723` bytes)\n- Reduction versus the classic endpoint-per-tool baseline (`92,354` tokens): `98.2%`\n\n| | Classic endpoint-per-tool baseline | Current Code Mode default |\n|---|---|---|\n| Tool definitions sent | about `92,354` tokens | about `1,681` tokens |\n| Public MCP tools | hundreds of endpoint schemas | `3` |\n| Context window tax | wide schema dump | compact fixed surface |\n<!-- docs-facts:readme:end -->\n\n## Quick Start\n\nGet your API key from **Dokploy Settings > Profile > API/CLI**.\n\nFor env-based setup, start from [`.env.example`](./.env.example).\n\nIf your client uses a JSON-style MCP config, this is the whole block:\n\n```json\n{\n  \"mcpServers\": {\n    \"dokploy\": {\n      \"command\": \"npx\",\n      \"args\": [\"@vibetools/dokploy-mcp\"],\n      \"env\": {\n        \"DOKPLOY_URL\": \"https://panel.example.com\",\n        \"DOKPLOY_API_KEY\": \"dokp_...\"\n      }\n    }\n  }\n}\n```\n\nIf your client uses CLI-based MCP management:\n\n```bash\n# Codex\ncodex mcp add dokploy \\\n  --env DOKPLOY_URL=https://panel.example.com \\\n  --env DOKPLOY_API_KEY=dokp_... \\\n  -- npx @vibetools/dokploy-mcp\n\n# Claude Code\nclaude mcp add --transport stdio \\\n  -e DOKPLOY_URL=https://panel.example.com \\\n  -e DOKPLOY_API_KEY=dokp_... \\\n  dokploy -- npx @vibetools/dokploy-mcp\n```\n\nAlready authenticated with the [Dokploy CLI](https://github.com/Dokploy/cli) or local\n`dokploy-mcp` config?\n\nYou may not need the env block at all.\n\nUsing multiple Dokploy organizations?\n\nKeep one compact MCP server and configure profiles with `DOKPLOY_PROFILES_JSON`:\n\n```json\n{\n  \"mcpServers\": {\n    \"dokploy\": {\n      \"command\": \"npx\",\n      \"args\": [\"@vibetools/dokploy-mcp\"],\n      \"env\": {\n        \"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\\\"}}\"\n      }\n    }\n  }\n}\n```\n\nUse `list_profiles` to see the available default and named profile targets without exposing API\nkeys. Pass `profile` to `execute` when you want a named profile instead of the default target:\n\n```json\n{\n  \"profile\": \"redivo\",\n  \"code\": \"return await dokploy.project.all()\"\n}\n```\n\n`search` also accepts an optional `profile` argument for profile-name validation while preserving\nthe same compact catalog behavior.\n\nHosted HTTP sessions keep their request-scoped remote credentials bound to the session. Named local\nprofiles are not exposed there.\n\nWant the wizard path instead of manual config?\n\n```bash\nnpx @vibetools/dokploy-mcp setup\n```\n\n## Pick Your Client\n\n- [Docs Home](./docs/README.md)\n- [Getting Started](./docs/getting-started.md)\n- [Cursor](./docs/clients/cursor.md)\n- [Codex](./docs/clients/codex.md)\n- [Claude Code](./docs/clients/claude-code.md)\n- [Claude Desktop](./docs/clients/claude-desktop.md)\n\n## What You Actually Get\n\n- `search`: discover Dokploy procedures and contracts\n- `execute`: run multi-step workflows in one sandboxed call\n- `list_profiles`: list configured Dokploy profile names and URLs without secrets\n- optional `raw` mode: one tool per procedure\n- optional `hybrid` mode: Code Mode plus selected raw tools\n- optional hosted HTTP path with `server.json` metadata and header-based remote auth\n\nIf you are new, use the default mode and stop trying to outsmart a problem that already has a\nworking shape.\n\n## Read These Next\n\n- [docs/getting-started.md](./docs/getting-started.md)\n- [docs/guides/profiles.md](./docs/guides/profiles.md)\n- [docs/guides/modes.md](./docs/guides/modes.md)\n- [docs/guides/compose.md](./docs/guides/compose.md)\n- [docs/guides/hosted-http.md](./docs/guides/hosted-http.md)\n- [docs/guides/hosted-deploy.md](./docs/guides/hosted-deploy.md)\n- [docs/guides/troubleshooting.md](./docs/guides/troubleshooting.md)\n- [docs/live-e2e-proof.md](./docs/live-e2e-proof.md)\n\n## CLI\n\n```bash\nnpx @vibetools/dokploy-mcp\nnpx @vibetools/dokploy-mcp serve-stdio\nnpx @vibetools/dokploy-mcp serve-http\nnpx @vibetools/dokploy-mcp setup\nnpx @vibetools/dokploy-mcp version\n```\n\n## Development\n\n```bash\ngit clone https://github.com/vcode-sh/dokploy-mcp.git && cd dokploy-mcp\nnpm install\nnpm run build\nnpm run lint\nnpm test\nnpm run docs:check:facts\n```\n\nThe rest lives in [docs](./docs/README.md), where it belongs.\n\n## Credits\n\nForked from [Dokploy/mcp](https://github.com/Dokploy/mcp). Started at 67 tools, mass-refactored to 377, then rebuilt the whole thing into an architecture that makes the tool count irrelevant.\n\n[Mauricio Siu](https://github.com/Siumauricio) built [Dokploy](https://dokploy.com) itself -- the PaaS this server talks to. Without the platform, this is a very elaborate way to POST into the void.\n\n[Henrique Andrade](https://github.com/andradehenrique) wrote the original MCP server. 15 commits, every PR merged. The kind of contributor who closes issues instead of opening them.\n\nContributors who shaped the original: [Joshua Macauley](https://github.com/Macawls) -- [lucasleal-developer](https://github.com/lucasleal-developer) -- [Nour Eddine Hamaidi](https://github.com/HenkDz) -- [Corey](https://github.com/limehawk) -- [Azil0ne](https://github.com/Azilone)\n\nUnmerged PRs are still blueprints. That's how open source works -- stolen inspiration with better commit messages.\n\n## License\n\nMIT - [Vibe Code](https://vcode.sh)\n\nOriginal work by [Henrique Andrade](https://github.com/andradehenrique) under Apache 2.0 -- see [LICENSE-ORIGINAL](LICENSE-ORIGINAL).\n",
  "bytes": 6861,
  "sha": "49a1c6c5f7c46023537e7a791c01af57b40fedc51e95013c39576fee3f2d440e",
  "repo_slug": "vcode-sh/dokploy-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_vcode_sh_dokploy_mcp_f5e0fa7f/readme"
}