Skip to main content
Glama
sapientsai

dokploy-mcp-server

by sapientsai

dokploy_compose

Manage Docker Compose services: create, deploy, update, and control them with environment variable and git source integration.

Instructions

Manage Docker Compose services. create: name+environmentId. get: composeId (returns env vars). 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 (KEY=VALUE pairs, one per line). cancelDeployment/cleanQueues/killBuild/refreshToken: composeId. readLogs: composeId+containerId, tail?, since?, search?.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
composeIdNo
nameNo
environmentIdNo
descriptionNo
composeTypeNodocker-compose or stack
composeFileNoDocker Compose YAML content (for sourceType: raw, set this to the inline compose file)
serverIdNo
envNoEnvironment variables as KEY=VALUE pairs, one per line. Example: 'DB_HOST=localhost\nDB_PORT=5432'
commandNo
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.
customGitUrlNoCustom git repository URL
customGitBranchNoCustom git branch
customGitSSHKeyIdNoSSH key ID for private git repos
repositoryNoGitHub repository (owner/repo format)
branchNoGitHub branch
ownerNoGitHub owner/organization
composePathNoPath to compose file in repo
autoDeployNoEnable auto-deploy on git push
appNameNoInternal app name
deleteVolumesNo
redeployNo
titleNo
deployDescriptionNo
targetEnvironmentIdNo
typeNo
serviceNameNo
containerIdNoContainer ID for readLogs (use dokploy_docker findContainers to discover)
tailNoNumber of recent log lines (default 100)
sinceNoTime range: 'all' or a duration like '30m', '1h', '7d'
searchNoFilter log lines by substring
Behavior3/5

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

With no annotations, the description carries the burden. It mentions potential failure on first deploy and supported fields for update, but does not disclose side effects, idempotency, permissions, or rate limits 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.

Conciseness3/5

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

The description is a dense run-on paragraph. It is front-loaded with the purpose, but the list of actions would benefit from bullet points or clearer separation. Every sentence provides some use, but the structure hinders quick scanning.

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 the tool's complexity (31 parameters, 16 actions), the description covers all actions and key parameters. However, it lacks output details (except for 'get returns env vars') and could be more comprehensive about return values or error states.

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 description coverage is 55%, so the schema already documents many parameters. The description adds value by grouping parameters per action (e.g., 'create: name+environmentId'), but omits some parameters like 'description' and 'title', and does not elaborate on data formats beyond what the schema provides.

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

Purpose5/5

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

The description clearly states 'Manage Docker Compose services' and enumerates specific actions (create, get, update, etc.), making the tool's purpose distinct from sibling tools like dokploy_application or dokploy_database.

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

Usage Guidelines3/5

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

The description provides per-action usage hints (e.g., 'loadServices: composeId (must deploy first)' and 'first deploy may fail — retry immediately'), but lacks an overall statement on when to use this tool versus alternatives or general prerequisites.

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