Skip to main content
Glama
clezcoding

awesome-coolify-mcp

by clezcoding

application

Deploy, control, and configure Coolify apps: start, stop, restart, fetch logs, and sync environment variables.

Instructions

Application lifecycle, deploy, log, and environment-variable actions — list via resource tool. Actions: get(uuid, format?, projection?, reveal?) · start(uuid) · stop(uuid) · restart(uuid) · deploy(uuid, force?) · logs(uuid, lines?, follow?, timeout?, idle_timeout?, min_interval?, max_interval?) — follow runtime only; check system.version capabilities.application_logs_follow · create(source_type, server_uuid) · update(uuid) · delete(uuid, confirm) · delete_preview(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) · envs:sync(uuid, env_file?, env_content?, dry_run?, confirm?, conflict_policy?) · envs:promote(source_uuid, target_uuid, dry_run?, confirm?, conflict_policy?, reveal?) Safety: confirm for destructive ops · optional instance · reveal opt-in only

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoEnvironment variable key
tagNoSingle tag batch expand
fqdnNoApplication FQDN substring
nameNoApplication name substring
pageNoPage number for pagination
tagsNoBatch deploy tags
typeNoFilter build-logs entries by type (default all — no filter). Applies only to the deployment_uuid (build-logs) path; ignored on runtime logs path.
uuidNoApplication UUID
waitNoPoll until terminal or timeout
forceNoForce rebuild without cache
linesNoNumber of log lines to retrieve
pruneNoDelete remote env keys absent from local
uuidsNoBatch deploy UUIDs
valueNoEnvironment variable value
actionYesThe action to run
followNoPoll runtime logs until idle or timeout (runtime identity only)
formatNoOutput format (default pretty)
is_spaNo
offsetNoSkip first K log lines
revealNoReveal sensitive/masked values in full projection (default false — secrets masked as ***)
confirmNoExplicit confirmation for destructive ops
domainsNoComma-separated domain list
dry_runNoPreview diff only
entriesNo
timeoutNoWait-mode timeout in seconds (deploy wait min 10; follow logs min 1)
env_fileNoLocal filesystem path to a .env file
env_uuidNoEnvironment variable UUID
instanceNoCoolify instance name from registry (optional — uses env credentials or registry default)
per_pageNoItems per page
redirectNo
is_staticNo
max_charsNoMax formatted output characters (default 16000)
build_packNoBuild pack
dockerfileNoDockerfile content
git_branchNoGit branch
is_literalNo
is_previewNo
projectionNoDetail projection depth
descriptionNoApplication description
env_contentNoInline .env file content
server_uuidNoServer UUID (required for create)
source_typeNoApplication source type for create
source_uuidNoSource application UUID for envs:promote
target_uuidNoTarget application UUID for envs:promote
watch_pathsNo
idle_timeoutNoFollow idle stop in seconds (default 60 when follow:true)
include_fullNoAlias for projection: full
is_multilineNo
max_intervalNoFollow max poll interval in seconds (default 30 when follow:true)
min_intervalNoFollow min poll interval in seconds (default 3 when follow:true)
project_nameNoProject name for lookup
project_uuidNoProject UUID
build_commandNo
custom_labelsNo
is_shown_onceNo
ports_exposesNoPorts to expose
start_commandNo
base_directoryNo
delete_volumesNo
docker_cleanupNo
git_commit_shaNoGit commit SHA
git_repositoryNoGit repository URL
include_hiddenNoInclude entries with hidden:true in build-logs output (default false — hidden entries are filtered out)
instant_deployNoQueue deploy immediately after create
ports_mappingsNoPort mappings
conflict_policyNoHow to resolve value conflicts on apply
deployment_uuidNoDeployment UUID for build logs
github_app_uuidNoGitHub app UUID
install_commandNo
environment_nameNoEnvironment name
environment_uuidNoEnvironment UUID
private_key_uuidNoPrivate deploy key UUID
use_build_serverNo
health_check_hostNo
health_check_pathNo
health_check_portNo
publish_directoryNo
health_check_methodNo
health_check_schemeNo
health_check_enabledNo
health_check_retriesNo
health_check_timeoutNo
delete_configurationsNo
force_domain_overrideNoOverride domain conflict
health_check_intervalNo
is_auto_deploy_enabledNo
is_force_https_enabledNo
health_check_return_codeNo
http_basic_auth_passwordNo
http_basic_auth_usernameNo
connect_to_docker_networkNo
custom_docker_run_optionsNo
delete_connected_networksNo
docker_registry_image_tagNoDocker registry image tag
health_check_start_periodNo
docker_registry_image_nameNoDocker registry image name
health_check_response_textNo
is_http_basic_auth_enabledNo
is_preserve_repository_enabledNo
is_container_label_escape_enabledNo

Output Schema

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

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

The description adds meaningful behavioral details beyond the sparse openWorldHint annotation: destructive operations require explicit confirmation, instance is optional, and reveal is opt-in only for sensitive values. It also flags the runtime-only follow capability check, giving the agent useful safety context.

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

Conciseness5/5

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

The description is dense but efficiently structured: a one-line scope statement, a compact action list with signatures, and a safety note. Every sentence adds actionable information, and the format is easy to scan for action selection.

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

Completeness4/5

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

For a complex 100-parameter tool with many actions, the description provides a strong overview, action signatures, safety rules, and a capability check. It falls short of full completeness by not mentioning the build-logs path via deployment_uuid or elaborating on open-world side effects, but the output schema and sibling context fill some gaps.

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

Parameters4/5

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

With 100 parameters and only 59% schema coverage, the description compensates by listing per-action signatures (e.g., get(uuid, format?, projection?, reveal?)) and required fields like server_uuid for create and confirm for destructive ops. However, the logs signature omits build-logs parameters such as deployment_uuid, type, and include_hidden, leaving a minor gap.

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 explicitly names the resource domain ('Application lifecycle, deploy, log, and environment-variable actions') and enumerates every supported action with its signature. It also distinguishes itself from the sibling resource tool by saying 'list via resource tool,' making the scope clear.

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?

The description provides concrete guidance for when to use certain actions, such as 'list via resource tool' and 'follow runtime only; check system.version capabilities.application_logs_follow.' It does not comprehensively contrast with all sibling tools like deployment or environment, but the key alternatives and conditional requirements are present.

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