Dokploy MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOKPLOY_URL | Yes | Dokploy panel URL, without /api. | |
| DOKPLOY_API_KEY | Yes | Dokploy API token generated under Settings → Profile → API/CLI. | |
| DOKPLOY_READ_ONLY | No | Set to true to block writes through both API clients. | false |
| DOKPLOY_ALLOW_HTTP | No | Allow HTTP for Dokploy. Only for trusted tunnels or networks; TLS validation is never disabled. | false |
| DOKPLOY_MCP_CONFIG | No | Selects a different configuration file path. | |
| CLOUDFLARE_ZONE_IDS | No | Optional comma-separated allowlist of Cloudflare Zone IDs. Without it, accessible zones are determined by your Cloudflare token. | |
| CLOUDFLARE_API_TOKEN | No | Cloudflare API Token with DNS Edit and Zone Read permissions, restricted to the zones you want to manage. Cloudflare is optional for Dokploy operations. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connection_statusA | Local configuration status without exposing credentials. Does not contact APIs. |
| dokploy_catalogB | Discover supported Dokploy endpoints and exact JSON parameter schemas. Use before dokploy_call. Snapshot compatibility must be checked against installed version. |
| dokploy_callA | Call a catalogued Dokploy endpoint with validated parameters. Supports projects, environments, applications, deployments, Compose, domains, databases, backups and servers. dry_run previews mutations. Destructive actions require explicit user authorization and confirm equal to endpoint. Results redact secret fields; logs may still contain application-generated sensitive text. |
| application_env_patchA | Patch runtime variables preserving other keys and build settings. First dry_run=true, then supply returned revision with dry_run=false. Complex multiline documents are refused. Not an atomic concurrency lock. |
| cloudflare_zonesC | List permitted Cloudflare zones; paginate using page. |
| cloudflare_recordsB | Inspect DNS records before changes; supports page and exact name filter. |
| cloudflare_upsertB | Create or update A/AAAA/CNAME. Defaults to dry run and DNS-only. Existing differing record needs replace_id. Does not alter zone SSL configuration. |
| cloudflare_deleteA | Delete an explicitly authorized A/AAAA/CNAME record. confirm must equal record_id. |
| dns_checkA | Resolve A/AAAA/CNAME using the local system resolver. Does not prove global propagation or HTTPS health. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| dokploy_workflow | Operating guide for Dokploy deployments, environment patches and Cloudflare DNS. Load before multi-step operations. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools target distinct resource+action pairs (cloudflare_records vs cloudflare_zones, upsert vs delete, catalog vs call). Minor overlap exists between dns_check and cloudflare_records (both inspect DNS) and between application_env_patch and the generic dokploy_call, but descriptions clarify the boundaries.
A clear cloudflare_* prefix group exists, but conventions are mixed: some names are noun-first (cloudflare_records, dokploy_catalog) while others are verb-first (cloudflare_upsert, cloudflare_delete, dns_check), and standalone tools lack a prefix. Readable but not a single predictable pattern.
Nine tools is well-scoped for a server spanning Dokploy orchestration and Cloudflare DNS. The catalog/call gateway collapses many potential endpoints into two tools, keeping the surface lean.
Cloudflare DNS covers list zones, list records, upsert, delete, and a resolver check, and Dokploy is broadly covered via the catalog+call passthrough plus a targeted env patch. Only minor gaps (e.g. zone creation or richer Dokploy shortcuts) remain.