| FMRS | 44 / 100 · D | 79 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 |
|---|
| Security and permissions | 4 / 20 | 18 / 20 |
|---|
| Maintenance | 6 / 20 | 16 / 20 |
|---|
| Documentation | 13 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 |
|---|
| Best for | - Teams already operating Dokploy and needing API automation
- Developers who want centralized Dokploy resource management in an MCP client
| - Engineering teams scaling AI coding agents while controlling spend
- Platform teams that need auditable, rollback-aware agent execution records
- Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
|
|---|
| Not for | - Users without a Dokploy server or API token
- Use cases requiring management of platforms other than Dokploy without a corresponding API
| - Developers who just want a simple code-completion helper without run governance
- Teams unwilling to accept local JSONL run records with HMAC signing
- Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
|
|---|
| Required permissions | - Access to the Dokploy server URL is required
- A Dokploy API authentication token is required
- Depending on the API operation, the server may have permission to create, modify, deploy, stop, delete, and manage security-sensitive resources
| - Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
- Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
- Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
- Execution of user-configured verifier commands (e.g. npm test)
|
|---|
| Risks and side effects | - The server exposes a broad range of Dokploy API operations, including potentially destructive deployment, stop, deletion, password, and security actions
- API responses may contain environment variables, tokens, passwords, or other sensitive fields; set DOKPLOY_REDACT_ENV=true to redact them
- Protect DOKPLOY_API_KEY and any service tokens supplied through DOKPLOY_CUSTOM_HEADERS
| - Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
- Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
- Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
- Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
|
|---|
| Supported clients | Cursor, Windsurf, VS Code, Claude Code, Zed, Claude Desktop, BoltAI | Claude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue |
|---|
| Tools | 0 | 0 |
|---|