Dokploy MCP integration for AI agents.
Connect AI agents to Dokploy through 524 structured actions, including admin setupmonitoring, ai analyzelogs, and ai create. Review authentication, inputs, w…
- ACTION CONTRACTS
- 524
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Dokploy integration exposes
The Dokploy Agent App exposes 524 provider-backed actions for developer tools and infrastructure work. Its current contract lets an authorized agent modify dokploy state via post /admin.setupmonitoring, modify dokploy state via post /ai.analyzelogs, and modify dokploy state via post /ai.create. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Dokploy account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Dokploy capabilities.
Showing 12 of 524 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
admin-setupMonitoringREVIEWModify Dokploy state via POST /admin.setupMonitoring.
INPUTS: metricsConfig
ai-analyzeLogsREVIEWModify Dokploy state via POST /ai.analyzeLogs.
INPUTS: aiId / logs / context
ai-createREVIEWModify Dokploy state via POST /ai.create.
INPUTS: name / apiUrl / apiKey / model / isEnabled
ai-deleteREVIEWModify Dokploy state via POST /ai.delete. Warning: this operation can remove, stop, or otherwise disrupt resources.
INPUTS: aiId
ai-deployREVIEWModify Dokploy state via POST /ai.deploy.
INPUTS: environmentId / id / dockerCompose / envVariables / serverId
ai-getREVIEWRead Dokploy data via GET /ai.get.
INPUTS: aiId
ai-getAllREVIEWRead Dokploy data via GET /ai.getAll.
ai-getEnabledProvidersREVIEWRead Dokploy data via GET /ai.getEnabledProviders.
ai-getModelsREVIEWRead Dokploy data via GET /ai.getModels.
INPUTS: apiUrl / apiKey
ai-oneREVIEWRead Dokploy data via GET /ai.one.
INPUTS: aiId
ai-suggestREVIEWModify Dokploy state via POST /ai.suggest.
INPUTS: aiId / input / serverId
ai-testConnectionREVIEWModify Dokploy state via POST /ai.testConnection.
INPUTS: apiUrl / apiKey / model
INPUT CONTRACTS
Know what the action needs before it runs.
admin-setupMonitoring
metricsConfigREQUIRED
ai-analyzeLogs
aiIdREQUIREDlogsREQUIREDcontextREQUIRED
ai-create
nameREQUIREDapiUrlREQUIREDapiKeyREQUIREDmodelREQUIREDisEnabledREQUIRED
ai-delete
aiIdREQUIRED
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Admin SetupMonitoring
Modify Dokploy state via POST /admin.setupMonitoring. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
admin-setupMonitoringVerify with Ai AnalyzeLogs
Modify Dokploy state via POST /ai.analyzeLogs. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
ai-analyzeLogsSAFETY BOUNDARY
Operate Dokploy with explicit limits
- Authorize Dokploy with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Dokploy data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Dokploy rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Dokploy task completed successfully.
CONNECTION MODEL
API key
An API key created from the Dokploy dashboard under Settings > API Keys. The key is sent in the x-api-key header.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 0
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 524
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Dokploy.