dokploy-mcp
by kennethreitz
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Bind address. Default 127.0.0.1. The Docker image sets 0.0.0.0. | 127.0.0.1 |
| MCP_PORT | No | Port for HTTP mode. Default 8765. | 8765 |
| DOKPLOY_URL | No | The Dokploy panel URL, for example https://dokploy.example.com. A path is fine if Dokploy is not at the root. If the URL already ends in /api, it is used as-is. | |
| MCP_LOG_LEVEL | No | Uvicorn log level. Default info. | info |
| MCP_AUTH_TOKEN | No | Bearer token for /mcp. Required in HTTP mode; every request except GET /health must send Authorization: Bearer <MCP_AUTH_TOKEN>. | |
| DOKPLOY_API_KEY | No | The Dokploy API key, sent as x-api-key. Generate it in the panel under Settings → Profile → API/CLI (or Settings → API Keys). | |
| MCP_ALLOWED_HOSTS | No | Comma-separated Host allowlist. Turns DNS-rebinding protection on. | |
| FORWARDED_ALLOW_IPS | No | Who may set X-Forwarded-* headers. Default *. | * |
| MCP_ALLOWED_ORIGINS | No | Comma-separated Origin allowlist, used with MCP_ALLOWED_HOSTS. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues