Skip to main content
Glama
sapientsai

dokploy-mcp-server

by sapientsai

dokploy_application

Manage Dokploy applications: create, deploy, update, and control lifecycle with environment variables, build options, and monitoring.

Instructions

Manage applications. create: name+environmentId. get: applicationId (returns metadata + masked env summary — never values). update: applicationId+fields (supports sourceType, repository, owner, branch, customGitUrl, customGitBranch, githubId, dockerImage, etc.). move: applicationId+targetEnvironmentId. deploy: applicationId, redeploy? (note: first deploy on new services may fail — retry immediately). start/stop/delete/markRunning/refreshToken/cleanQueues/killBuild/cancelDeployment: applicationId. reload: applicationId+appName. saveEnvironment: applicationId+env (KEY=VALUE pairs, full replace). setEnvVars: applicationId + set? (KEY=VALUE pairs to upsert) + unset? (KEY names to remove) — read-modify-write inside the server; result is a masked confirmation with changed key names only. getEnvKeys: applicationId — returns just the KEY names (no values). getEnvValuesUnsafe: applicationId — UNSAFE escape hatch that returns full KEY=VALUE pairs (use only when you need actual values; output goes to the tool transcript and any retained logs). saveBuildType: applicationId+buildType. traefikConfig: applicationId, traefikConfig? (omit to read). readMonitoring: appName. readLogs: applicationId, tail? (default 100), since? ('all' or duration like '1h'), search? (substring filter).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
envNoEnvironment variables as KEY=VALUE pairs, one per line. Example: 'DB_HOST=localhost\nDB_PORT=5432'. Used by saveEnvironment (full replace).
setNosetEnvVars: KEY=VALUE pairs to upsert, one per line. Existing keys retain order; new keys append.
nameNo
tailNoNumber of recent log lines to return (default 100)
ownerNoGitHub org/user
sinceNoTime range: 'all' or a duration like '30m', '1h', '7d'
titleNo
unsetNosetEnvVars: list of KEY names to remove. Unknown keys are silently skipped.
actionYes
branchNoBranch name
searchNoFilter log lines by substring (alphanumeric + ' ._-' only)
appNameNo
commandNo
cpuLimitNo
githubIdNoGitHub App provider ID for private repo access
redeployNo
replicasNo
serverIdNo
buildArgsNo
buildTypeNodockerfile | heroku_buildpacks | paketo_buildpacks | nixpacks | static | railpack
autoDeployNo
dockerfileNo
repositoryNoGitHub repository name
sourceTypeNoSource type. github → set repository+owner+branch (+githubId for private). git → set customGitUrl+customGitBranch. docker → set dockerImage. The API also supports gitlab/bitbucket/gitea/drop sources, but those need provider-specific fields not yet exposed by this tool.
descriptionNo
dockerImageNo
memoryLimitNo
buildSecretsNo
customGitUrlNoCustom git repository URL (for sourceType: git)
applicationIdNo
createEnvFileNo
environmentIdNo
traefikConfigNoNew config content (omit to read current)
customGitBranchNoBranch for custom git source
dockerBuildStageNo
publishDirectoryNo
deployDescriptionNoDeploy description (maps to API description field)
dockerContextPathNo
targetEnvironmentIdNo
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It discloses important behaviors: masked env summaries, full-replace vs upsert for environment variables, UNSAFE escape hatch with consequences, and potential deploy failures. Auth needs and rate limits are missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense and uses a consistent 'action: parameter(s)' format, making it scannable. It is longer than ideal but well-structured with action-by-action breakdown. Could be more concise without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 39 parameters, no output schema, and moderate schema coverage, the description provides good contextual notes for key actions (e.g., deployment retry, environment variable operations). However, return values are only described for a few actions, and many parameters remain unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 41%, leaving many parameters undocumented. The description compensates by tying parameters to specific actions (e.g., for 'sourceType' it explains mapping to other fields). However, 59% of parameters lack both schema and description context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Manage applications' and enumerates 22 specific actions with parameter mappings. It distinguishes the tool from siblings by focusing on application lifecycle operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Each action has explicit parameter requirements (e.g., 'create: name+environmentId') and special notes like 'first deploy on new services may fail — retry immediately'. It does not explicitly exclude alternatives but provides enough context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sapientsai/dokploy-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server