Skip to main content
Glama
clezcoding

awesome-coolify-mcp

by clezcoding

database

Manage DB instances: start, stop, restart, create, update, delete, set environment variables, and schedule backups with history and on-demand triggers.

Instructions

Database CRUD, lifecycle, env vars, and backup-schedule actions — list via resource tool. Actions: get(uuid?, name?) · start(uuid?) · stop(uuid?) · restart(uuid?) · create(engine, server_uuid) · update(uuid?) · delete(uuid?, confirm) · delete_preview(uuid?, name?) · envs:list(uuid?) · envs:get(uuid?, env_uuid?, key?) · envs:create(uuid?, key, value) · envs:update(uuid?, env_uuid?, key?, value) · envs:delete(uuid?, env_uuid, confirm) · envs:bulk-update(uuid?, entries, confirm) · backup:create(uuid?, frequency) · backup:list(uuid?) · backup:history(uuid?, scheduled_backup_uuid) · backup:update(uuid?, scheduled_backup_uuid) · backup:delete(uuid?, scheduled_backup_uuid, confirm) · backup:now(uuid?, scheduled_backup_uuid) Safety: confirm for destructive ops · optional instance · reveal opt-in only

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoEnvironment variable key
nameNoDatabase name substring
pageNoPage number for pagination
uuidNoDatabase UUID
imageNoCustom database image
valueNoEnvironment variable value
actionYesThe action to run
engineNoDatabase engine (required for create)
formatNoOutput format (default pretty)
revealNoReveal sensitive/masked values in full projection (default false — secrets masked as ***)
confirmNoConfirm destructive or public exposure ops
enabledNoEnable schedule
entriesNo
save_s3NoUpload backups to S3
timeoutNoBackup timeout in seconds
dump_allNo
env_uuidNoEnvironment variable UUID
instanceNoCoolify instance name from registry (optional — uses env credentials or registry default)
per_pageNoItems per page
delete_s3NoAlso delete S3 backup artifacts
frequencyNoBackup frequency preset or cron expression
is_publicNoExpose database port publicly
max_charsNoMax formatted output characters (default 16000)
backup_nowNo
is_literalNo
mysql_userNo
projectionNoDetail projection depth
descriptionNoDatabase description
limits_cpusNo
postgres_dbNo
public_portNoPublic port when is_public
server_uuidNoTarget server UUID
include_fullNoAlias for projection: full
is_multilineNo
mariadb_userNo
project_nameNoProject name
project_uuidNoProject UUID
is_shown_onceNo
limits_cpusetNo
limits_memoryNo
postgres_confNo
postgres_userNo
delete_volumesNo
docker_cleanupNo
instant_deployNoStart database after create
keydb_passwordNo
mysql_databaseNo
mysql_passwordNo
redis_passwordNo
s3_storage_uuidNoS3 storage destination UUID
destination_uuidNo
environment_nameNoEnvironment name
environment_uuidNoEnvironment UUID
mariadb_databaseNo
mariadb_passwordNo
limits_cpu_sharesNo
postgres_passwordNo
dragonfly_passwordNo
limits_memory_swapNo
databases_to_backupNo
mysql_root_passwordNo
public_port_timeoutNoPublic port mapping timeout
postgres_initdb_argsNo
clickhouse_admin_userNo
delete_configurationsNo
mariadb_root_passwordNo
mongo_initdb_databaseNo
scheduled_backup_uuidNoBackup schedule UUID
limits_memory_swappinessNo
clickhouse_admin_passwordNo
delete_connected_networksNo
limits_memory_reservationNo
postgres_host_auth_methodNo
mongo_initdb_root_passwordNo
database_backup_retention_days_s3No
database_backup_retention_amount_s3No
database_backup_retention_days_locallyNo
database_backup_retention_amount_locallyNo
database_backup_retention_max_storage_s3No
database_backup_retention_max_storage_locallyNo

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 discloses behavioral traits such as safety confirmations for destructive ops, optional instance parameter, and reveal opt-in. While annotations only include openWorldHint, the description adds useful context beyond that. It does not contradict annotations.

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 structured with a compact list of actions and safety notes. However, it is lengthy due to the many actions listed. It could be more concise by grouping or summarizing less common actions.

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 (80 parameters, numerous actions) and the presence of an output schema, the description is incomplete. It does not explain return values, common parameter combinations, or prerequisites beyond basic safety.

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

Parameters2/5

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

Schema description coverage is only 43%, and the description adds little meaning beyond listing actions with parenthesized parameters (e.g., 'get(uuid?, name?)'). Many of the 80 parameters are not explained in the description, leaving gaps for the agent.

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 the tool's purpose: 'Database CRUD, lifecycle, env vars, and backup-schedule actions'. It lists specific actions and distinguishes from sibling tools by noting 'list via resource tool'. The scope is well-defined.

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 guidance on when to use this tool versus others (e.g., 'list via resource tool'). It also includes safety notes for destructive ops. However, it does not explicitly differentiate from other sibling tools like 'application' or 'service'.

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