Dokploy MCP Server exposes Dokploy functionalities 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.
This server focuses exclusively on tools for direct Dokploy API operations, providing a clean and efficient interface for project and application management.
- Node.js >= v18.0.0 (or Docker)
- Cursor, VS Code, Claude Desktop, or another MCP Client
- A running Dokploy server instance
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", "@ahdev/dokploy-mcp"],
"env": {
"DOKPLOY_URL": "https://your-dokploy-server.com/api",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
}
}
}
}
Alternative: Use Bun
{
"mcpServers": {
"dokploy-mcp": {
"command": "bunx",
"args": ["-y", "@ahdev/dokploy-mcp"],
"env": {
"DOKPLOY_URL": "https://your-dokploy-server.com/api",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
}
}
}
}
Alternative: Use Deno
{
"mcpServers": {
"dokploy-mcp": {
"command": "deno",
"args": ["run", "--allow-env", "--allow-net", "npm:@ahdev/dokploy-mcp"],
"env": {
"DOKPLOY_URL": "https://your-dokploy-server.com/api",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
}
}
}
}
Add this to your Windsurf MCP config file. See Windsurf MCP docs for more info.
{
"mcpServers": {
"dokploy-mcp": {
"command": "npx",
"args": ["-y", "@ahdev/dokploy-mcp"],
"env": {
"DOKPLOY_URL": "https://your-dokploy-server.com/api",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
}
}
}
}
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", "@ahdev/dokploy-mcp"],
"env": {
"DOKPLOY_URL": "https://your-dokploy-server.com/api",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
}
}
}
}
Add this to your Zed settings.json
. See Zed Context Server docs for more info.
{
"context_servers": {
"dokploy-mcp": {
"command": {
"path": "npx",
"args": ["-y", "@ahdev/dokploy-mcp"]
},
"settings": {
"DOKPLOY_URL": "https://your-dokploy-server.com/api",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
}
}
}
}
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", "@ahdev/dokploy-mcp"],
"env": {
"DOKPLOY_URL": "https://your-dokploy-server.com/api",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
}
}
}
}
Open the "Settings" page of the app, navigate to "Plugins," and enter the following JSON:
{
"mcpServers": {
"dokploy-mcp": {
"command": "npx",
"args": ["-y", "@ahdev/dokploy-mcp"],
"env": {
"DOKPLOY_URL": "https://your-dokploy-server.com/api",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
}
}
}
}
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 dokploy-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/api \ -e DOKPLOY_API_KEY=your_token_here \ dokploy-mcp
HTTP Mode (for web applications):
docker run -it --rm \ -p 8080:3000 \ -e MCP_TRANSPORT=http \ -e DOKPLOY_URL=https://your-dokploy-server.com/api \ -e DOKPLOY_API_KEY=your_token_here \ dokploy-mcp
-
Docker Compose:
Use the provided
docker-compose.yml
for 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/api", "-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
.
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", "@ahdev/dokploy-mcp"],
"env": {
"DOKPLOY_URL": "https://your-dokploy-server.com/api",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
}
}
}
}
DOKPLOY_URL
: Your Dokploy server API URL (required)DOKPLOY_API_KEY
: Your Dokploy API authentication token (required)
This MCP server supports multiple transport modes to suit different use cases:
The default mode uses stdio for direct process communication, ideal for desktop applications and command-line usage.
# Run with stdio (default)
npx -y @ahdev/dokploy-mcp
# or
npm run start:stdio
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
npm run start:http
# or
npx -y @ahdev/dokploy-mcp --http
# or via environment variable
MCP_TRANSPORT=http npx -y @ahdev/dokploy-mcp
Modern Streamable HTTP Endpoints:
- POST /mcp - Client-to-server requests
- GET /mcp - Server-to-client notifications
- DELETE /mcp - Session termination
- GET /health - Health check endpoint
Legacy SSE Endpoints (Backwards Compatibility):
- GET /sse - SSE stream initialization
- POST /messages - Client message posting
Configuration:
- Internal port:
3000
(fixed) - External port: configurable via
EXTERNAL_PORT
(default:3000
) - Supports both modern Streamable HTTP (MCP 2025-03-26) and legacy SSE (MCP 2024-11-05)
- Session management with automatic cleanup for both transport types
Client Compatibility:
Modern clients automatically use the Streamable HTTP endpoints, while legacy clients can connect using the SSE endpoints. The server handles both protocols simultaneously, ensuring compatibility with:
- Modern MCP clients (Claude Desktop, Cline, etc.) β Use
/mcp
endpoints - Legacy MCP clients β Use
/sse
and/messages
endpoints - Custom integrations β Choose the appropriate protocol for your needs
For detailed transport mode documentation and client examples, refer to the configuration examples above.
This MCP server provides comprehensive tools for Dokploy project, application, and database management through 43 tools organized into three main categories:
Complete project lifecycle management including creation, updates, duplication, and deletion:
project-all
- List all projectsproject-one
- Get project detailsproject-create
- Create new projectsproject-update
- Update project configurationsproject-duplicate
- Duplicate projects with selective service copyingproject-remove
- Delete projects
Comprehensive application lifecycle and configuration management:
- CRUD Operations: Create, read, update, delete applications
- Lifecycle Management: Deploy, redeploy, start, stop, reload applications
- Utility Operations: Move between projects, clean queues, refresh tokens
Support for multiple Git providers with specific configurations:
- GitHub Provider - Full GitHub integration with webhooks
- GitLab Provider - Complete GitLab project integration
- Bitbucket Provider - Bitbucket repository management
- Gitea Provider - Self-hosted Gitea integration
- Git Provider - Custom Git repository support
- Docker Provider - Direct Docker image deployment
- Build Settings - Configure build types (Dockerfile, Heroku, Nixpacks, etc.)
- Environment Management - Environment variables and build arguments
- Monitoring Integration - Application monitoring and metrics
- Traefik Configuration - Load balancer and reverse proxy settings
Complete PostgreSQL database lifecycle management:
- CRUD Operations: Create, read, update, remove PostgreSQL databases
- Lifecycle Management: Deploy, start, stop, reload, rebuild databases
- Configuration Management: External ports, environment variables, status changes
- Project Management: Move databases between projects
postgres-create
- Create new PostgreSQL databasespostgres-one
- Get database detailspostgres-update
- Update database configurationspostgres-remove
- Delete databasespostgres-deploy
- Deploy databasespostgres-start
- Start database instancespostgres-stop
- Stop database instancespostgres-reload
- Reload database configurationspostgres-rebuild
- Rebuild database instancespostgres-move
- Move databases between projectspostgres-changeStatus
- Change database statuspostgres-saveExternalPort
- Configure external database portspostgres-saveEnvironment
- Manage database environment variables
For detailed information about each tool, including input schemas, required fields, and usage examples, see TOOLS.md.
All tools include semantic annotations to help MCP clients understand their behavior:
- Read-Only Tools (
readOnlyHint: true
): Safe operations that only retrieve data - Destructive Tools (
destructiveHint: true
): Operations that modify or delete resources - Creation Tools (
destructiveHint: false
): Operations that create new resources - Idempotent Tools (
idempotentHint: true
): Operations safe to repeat - External API Tools (
openWorldHint: true
): All tools interact with Dokploy API
The Dokploy MCP Server is built using:
@modelcontextprotocol/sdk
: For creating the MCP server and defining tools- Node.js & TypeScript: As the underlying runtime and language
- Stdio Transport: Communicates with MCP clients over standard input/output (stdio)
- Dokploy API Integration: Direct interaction with Dokploy server's REST API
- Comprehensive Tool Coverage: Complete implementation of all Dokploy application and project endpoints
- Robust Error Handling: Centralized HTTP client with retry logic and structured error responses
- Schema Validation: Full Zod-based input validation matching OpenAPI specifications
- Tool Annotations: Semantic annotations (readOnlyHint, destructiveHint, etc.) for enhanced MCP client understanding
The server architecture supports:
- 43 Tools covering all project, application, and database management operations
- Multiple Git Providers (GitHub, GitLab, Bitbucket, Gitea, custom Git)
- Flexible Configuration for builds, deployments, and monitoring
- Type-Safe Operations with comprehensive TypeScript support
Each tool includes input validation, API integration, and structured response formatting for consistent MCP client interaction.
Clone the project and install dependencies:
git clone https://github.com/Dokploy/mcp.git
cd dokploy-mcp
npm install
Build:
npm run build
{
"mcpServers": {
"dokploy-mcp": {
"command": "npx",
"args": ["tsx", "/path/to/dokploy-mcp/src/index.ts"],
"env": {
"DOKPLOY_URL": "https://your-dokploy-server.com/api",
"DOKPLOY_API_KEY": "your-dokploy-api-token"
}
}
}
}
npx -y @modelcontextprotocol/inspector npx @ahdev/dokploy-mcp
- TOOLS.md - Complete tool reference with schemas and examples
- CONTRIBUTING.md - Contributing guidelines
-
Try adding
@latest
to the package name. -
Make sure you are using Node v18 or higher to have native fetch support with
npx
. -
Verify your
DOKPLOY_URL
andDOKPLOY_API_KEY
environment variables are correctly set.
We welcome contributions! If you'd like to contribute to the Dokploy MCP Server, please check out our Contributing Guide.
If you encounter any issues, have questions, or want to suggest a feature, please open an issue in our GitHub repository.
This project is licensed under the Apache License.