Skip to main content
Glama
sapientsai

dokploy-mcp-server

by sapientsai

dokploy_compose

Manage Docker Compose services across environments: create, update, deploy, and monitor with built-in environment variable management and log access.

Instructions

Manage Docker Compose services. create: name+environmentId. get: composeId (metadata + masked env summary — never values). update: composeId+fields (supports sourceType, composeFile for raw/inline, git source fields, autoDeploy). delete/start/stop/getDefaultCommand: composeId. deploy: composeId, redeploy? (note: first deploy on new services may fail — retry immediately). move: composeId+targetEnvironmentId. loadServices: composeId (must deploy first). loadMounts: composeId+serviceName. saveEnvironment: composeId+env (full replace). setEnvVars: composeId + set?/unset? (merge inside the server, masked confirmation only). getEnvKeys: composeId — KEY names only. getEnvValuesUnsafe: composeId — UNSAFE escape hatch that returns full KEY=VALUE pairs (output goes to the tool transcript). cancelDeployment/cleanQueues/killBuild/refreshToken: composeId. readLogs: composeId+containerId, tail?, since?, search?.

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.
nameNo
tailNoNumber of recent log lines (default 100)
typeNo
ownerNoGitHub owner/organization
sinceNoTime range: 'all' or a duration like '30m', '1h', '7d'
titleNo
unsetNosetEnvVars: list of KEY names to remove.
actionYes
branchNoGitHub branch
searchNoFilter log lines by substring
appNameNoInternal app name
commandNo
redeployNo
serverIdNo
composeIdNo
autoDeployNoEnable auto-deploy on git push
repositoryNoGitHub repository (owner/repo format)
sourceTypeNoSource type. github → set repository+owner+branch (+composePath). git → set customGitUrl+customGitBranch (+customGitSSHKeyId for private). raw → set composeFile (inline YAML). The API also supports gitlab/bitbucket/gitea sources, but those need provider-specific fields not yet exposed by this tool.
composeFileNoDocker Compose YAML content (for sourceType: raw, set this to the inline compose file)
composePathNoPath to compose file in repo
composeTypeNodocker-compose or stack
containerIdNoContainer ID for readLogs (use dokploy_docker findContainers to discover)
descriptionNo
serviceNameNo
customGitUrlNoCustom git repository URL
deleteVolumesNo
environmentIdNo
customGitBranchNoCustom git branch
customGitSSHKeyIdNoSSH key ID for private git repos
deployDescriptionNo
targetEnvironmentIdNo
Behavior2/5

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

With no annotations, the description must carry the full burden. It discloses some behaviors like 'get returns masked env summary — never values' and deploy retry note, but it omits important aspects such as side effects, rate limits, authentication needs, and error handling for most actions.

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

Conciseness2/5

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

The description is a long, unstructured block of text that redundantly lists 'composeId' for many actions. It could be organized as a table or bullet list with clear separations. It front-loads the purpose but the subsequent enumeration is inefficient and hard to parse.

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

Completeness2/5

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

Given the tool's complexity (33 parameters, 20 actions, no output schema), the description is incomplete. It fails to describe return values for any action, which the agent would need to understand what the tool provides. The behavioral notes are sparse and not comprehensive.

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?

The input schema has 58% description coverage. The description adds some value by grouping parameters per action (e.g., 'saveEnvironment: composeId+env (full replace)'), but it does not provide detailed semantics beyond what the schema already contains. Many parameters are only named in the description without additional explanation.

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

Purpose3/5

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

The description states 'Manage Docker Compose services' which clearly identifies the resource and action, but the enumeration of actions is cluttered and lacks a concise summary. It distinguishes from siblings by being specific to Compose, but the structure hinders clarity.

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

Usage Guidelines2/5

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

Some implicit guidance is given, such as 'first deploy on new services may fail — retry immediately', but there are no explicit when-to-use or when-not-to-use instructions relative to sibling tools like dokploy_application. The description does not help the agent decide between this and other tools.

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