Skip to main content
Glama
clezcoding

awesome-coolify-mcp

by clezcoding

service

Create, update, delete, start, stop, restart, deploy services, and manage environment variables on Coolify instances.

Instructions

Service CRUD, lifecycle, and environment-variable actions — list via resource tool. Actions: get(uuid, format?, projection?, reveal?) · list-types(format?, projection?) · create(server_uuid, type?, compose?) · update(uuid) · delete(uuid, confirm) · delete_preview(uuid) · start(uuid) · stop(uuid) · restart(uuid) · deploy(uuid) · envs:list(uuid) · envs:get(uuid, key) · envs:create(uuid, key, value) · envs:update(uuid, key, value) · envs:delete(uuid, env_uuid, confirm) · envs:bulk-update(uuid, entries, confirm) Safety: confirm for destructive ops · optional instance · reveal opt-in only

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoEnvironment variable key
fqdnNoApplication FQDN substring
nameNoService name substring
pageNoPage number for pagination
typeNoOne-click service type, e.g. actualbudget, calibre-web, gitea-with-mysql
urlsNoOptional domain URLs
uuidNoService UUID
valueNoEnvironment variable value
actionYesThe action to run
formatNoOutput format (default pretty)
revealNoReveal sensitive/masked values in full projection (default false — secrets masked as ***)
composeNoInline Docker Compose YAML
confirmNoExplicit confirmation for destructive ops
entriesNoBulk env entries (min 1, max 100 per call)
env_uuidNoEnvironment variable UUID
instanceNoCoolify instance name from registry (optional — uses env credentials or registry default)
per_pageNoItems per page
max_charsNoMax formatted output characters (default 16000)
is_literalNoLiteral flag
is_previewNoPreview variable
projectionNoDetail projection depth
descriptionNoService description
pull_latestNoPull latest Docker images before restart
server_uuidNoTarget server UUID
compose_fileNoLocal path to a docker-compose.yml file (max 1 MiB)
include_fullNoAlias for projection: full
is_multilineNoMultiline flag
project_nameNoProject name
project_uuidNoProject UUID
is_shown_onceNoShow-once flag
delete_volumesNoAlso delete attached volumes
docker_cleanupNoRun Docker cleanup on stop
instant_deployNoStart/deploy immediately after create
destination_uuidNoDestination UUID
environment_nameNoEnvironment name
environment_uuidNoEnvironment UUID
delete_configurationsNoAlso delete configurations
force_domain_overrideNoOverride domain conflict
connect_to_docker_networkNoConnect to Docker network
delete_connected_networksNoDelete connected networks
is_container_label_escape_enabledNoContainer label escape enabled

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
dataNo
_metaNo
errorNo
_size_warningNo
_formattedTextNo
Behavior3/5

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

Annotations include openWorldHint, indicating potential side effects. Description adds safety requirement for destructive operations and reveals opt-in behavior, but does not detail other side effects, error behavior, or state changes beyond these notes.

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

Conciseness4/5

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

Description is compact, front-loaded with purpose, and uses a clear list of actions. Every sentence adds value without repetition, though formatting could be improved for readability.

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?

For a tool with 41 parameters and 16 actions, the description is too brief. It does not explain per-action parameters, dependencies, or return values. An output schema exists but is not shown; the description should provide more guidance for such complexity.

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 100%, so the schema already documents all parameters. The description adds no additional meaning beyond listing action signatures, which are already in the enum. Baseline 3 is appropriate.

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?

Clearly states 'Service CRUD, lifecycle, and environment-variable actions' and distinguishes from sibling 'resource' tool by noting 'list via resource tool'. Enumerates all actions, establishing a specific verb+resource mapping.

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?

Provides safety notes on 'confirm for destructive ops' and mentions optional instance and reveal opt-in. However, lacks explicit guidance on when to use this tool versus siblings like 'application' or 'deployment', and no when-not-to instructions.

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/clezcoding/awesome-coolify'

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