Skip to main content
Glama
clezcoding

awesome-coolify-mcp

by clezcoding

database

Manage database lifecycle, environment variables, and backup schedules with CRUD operations, start/stop/restart actions, and backup automation.

Instructions

Database CRUD, lifecycle, environment-variable, and backup-schedule actions (get, start, stop, restart, create, update, delete, delete_preview, envs:list, envs:get, envs:create, envs:update, envs:delete, envs:bulk-update, backup:create, backup:list, backup:update, backup:delete, backup:now, backup:history) — list via resource tool. Local .env sync is application-only (not on database). Database envs:* omit is_preview (OpenAPI Pitfall 1). envs:delete and envs:bulk-update require confirm:true. Env values masked as *** by default; pass reveal:true only after asking the human — do not persist revealed secrets. backup:delete requires confirm:true; delete_s3 defaults false and delete_s3:true still requires confirm. backup:create frequency accepts OpenAPI presets or cron; backup:update frequency accepts presets only — cron on update returns COOLIFY_VALIDATION_ERROR. backup:now triggers immediate backup via PATCH with backup_now:true and requires scheduled_backup_uuid. Backup config S3 credentials masked as *** by default; pass reveal:true only after asking the human — do not persist revealed secrets. create: 8 engines via engine discriminator; instant_deploy defaults true. update: curated engine-specific fields; is_public: true requires confirm: true. delete requires confirm: true with safe defaults (delete_volumes/delete_configurations/docker_cleanup/delete_connected_networks default false). Full-projection get/create/update masks credentials and connection strings as *** by default; pass reveal: true for plaintext only when needed — do not persist revealed secrets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

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

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

The description goes far beyond the openWorldHint annotation by detailing confirmation requirements, secret masking defaults, the need to ask humans before revealing secrets, OpenAPI pitfalls, and backup frequency constraints. This level of detail fully discloses behavioral traits and potential side effects.

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?

The description is long but well-structured, grouping sub-actions and using consistent formatting for notes. Every sentence carries essential information, and the length is justified by the tool's complexity. It could be slightly more concise, but it remains efficient for the scope.

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

Completeness5/5

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

The description covers all sub-actions, parameter semantics, confirmation needs, default behaviors, and known errors. With the output schema available and full schema coverage, the tool definition is thoroughly complete. No gaps are evident.

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

Parameters5/5

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

With 100% schema coverage, the description still adds substantial value by explaining the semantic context of parameters such as 'reveal' (must ask human), 'confirm' (required for destructive actions), 'delete_s3' defaults, and 'frequency' constraints for backup creation vs update. This enriches the agent's understanding beyond the schema itself.

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 'Database CRUD, lifecycle, environment-variable, and backup-schedule actions', enumerating all supported sub-actions. It distinguishes itself from sibling tools like 'resource' by noting that listing is done via the resource tool. The purpose is fully defined and unambiguous.

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 extensive guidance on when to use specific sub-actions, including requirements for confirm flags, reveal flags, and known pitfalls for env operations and backup updates. It mentions that listing databases should be done via the resource tool. However, it could more explicitly distinguish when to use this tool versus other sibling tools for broader context.

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