Multi-instance Dokploy API proxy MCP - single tool, skill-driven, 445 endpoints
Multi-instance Dokploy API proxy MCP - single tool, skill-driven, 445 endpoints. That is what the mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Multi-instance Dokploy API proxy MCP. 1 tool, ~200 tokens instead of 67+ tools consuming ~35,000 tokens per conversation. Supports multiple Dokploy instances via config file.
Installation goes through your MCP client rather than a global install: point it at mcp-dokploy-fullapi-proxy on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
The server publishes 3 tools. What each one is for:
Cursor — The Cursor tool exposed by this serverWindsurf — The Windsurf tool exposed by this serverCline — Add MCP via Cline -> MCP Servers -> Edit. Paste SKILL.md into .clinerulesConfiguration is passed through the environment: DOKPLOY_URL, DOKPLOY_TOKEN, DOKPLOY_SRV01_URL, DOKPLOY_SRV01_TOKEN, DOKPLOY_HSH_URL, DOKPLOY_HSH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — Cursor, Windsurf, Cline — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Cursor | The Cursor tool exposed by this server. |
| Windsurf | The Windsurf tool exposed by this server. |
| Cline | Add MCP via Cline -> MCP Servers -> Edit. Paste SKILL.md into .clinerules. |
**With env vars (single instance):**
```json
{
"mcpServers": {
"dokploy-fullapi-proxy": {
"command": "npx",
"args": ["-y", "mcp-dokploy-fullapi-proxy"],
"env": {
"DOKPLOY_URL": "https://your-dokploy-instance.com/api",
"DOKPLOY_TOKEN": "your-api-token"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DOKPLOY_URL | Endpoint or connection string the server talks to. | Yes |
| DOKPLOY_TOKEN | Credential the server authenticates with. | Yes |
| DOKPLOY_SRV01_URL | Endpoint or connection string the server talks to. | Yes |
| DOKPLOY_SRV01_TOKEN | Credential the server authenticates with. | Yes |
| DOKPLOY_HSH_URL | Endpoint or connection string the server talks to. | Yes |
| DOKPLOY_HSH_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.