Prerequisites
Before installing Dokploy MCP Server, ensure you have:Node.js or Docker
Node.js >= v18.0.0 for native fetch support with npx, or Docker for containerized deployment
Dokploy Server
A running Dokploy instance with API access. You’ll need:
- Your Dokploy server URL (e.g.,
https://your-dokploy-server.com/api) - A valid API key/token from your Dokploy account
Installation by Client
- Cursor
- VS Code
- Windsurf
- Zed
- Claude Desktop
- BoltAI
Install in Cursor
-
Go to:
Settings→Cursor Settings→MCP→Add new global MCP server -
Add this configuration to your Cursor
~/.cursor/mcp.jsonfile:
- Replace
your-dokploy-server.com/apiwith your Dokploy API URL - Replace
your-dokploy-api-tokenwith your API key
Project-specific installation
Project-specific installation
You can also install in a specific project by creating
.cursor/mcp.json in your project folder instead of using the global config.Alternative: Use Bun
Alternative: Use Bun
Alternative: Use Deno
Alternative: Use Deno
Docker Installation
The Docker container supports both stdio and HTTP transport modes for flexible deployment.MCP Client Configuration with Docker
For stdio mode (Claude Desktop, VS Code, etc.):http://localhost:3000/mcp.
Docker Compose
Docker Compose
Use the provided
docker-compose.yml for production deployments:Windows Installation
The configuration on Windows requires usingcmd as the command wrapper:
Environment Variables
Your Dokploy server API URL. Must include the
/api path.Example: https://dokploy.yourdomain.com/apiYour Dokploy API authentication token. Generate this from your Dokploy dashboard under Settings → API Keys.
Transport mode for the MCP server. Set to
http or sse to enable HTTP mode.Options: stdio (default), http, sseExternal port for HTTP mode. Only used when
MCP_TRANSPORT=http.Troubleshooting
MCP client shows connection errors
MCP client shows connection errors
- Try adding
@latestto the package name:@ahdev/dokploy-mcp@latest - Verify you’re using Node.js v18 or higher:
node --version - Check your environment variables are correctly set in the config file
- Ensure your Dokploy server is accessible from your machine
Authentication failed / 401 errors
Authentication failed / 401 errors
- Verify your
DOKPLOY_API_KEYis correct - Check that the API key hasn’t expired in your Dokploy dashboard
- Ensure your
DOKPLOY_URLends with/api(e.g.,https://dokploy.yourdomain.com/api)
Tools not showing in MCP client
Tools not showing in MCP client
- Restart your MCP client after adding the configuration
- Check the MCP client logs for error messages
- Try running the server manually to test:
npx @ahdev/dokploy-mcp
npx command not found
npx command not found
- Install Node.js v18 or higher from nodejs.org
- Verify installation with:
npx --version - On Windows, you may need to restart your terminal after installing Node.js
Docker container exits immediately
Docker container exits immediately
- Check Docker logs:
docker logs <container-id> - Verify environment variables are set correctly
- Ensure the Dokploy server is reachable from within the Docker network
Next Steps
Now that you’ve installed Dokploy MCP Server, let’s verify it’s working and deploy your first application:Quickstart Guide
Get started with your first deployment in minutes