Skip to main content
Glama
clezcoding

awesome-coolify-mcp

by clezcoding

setup

Initialize a workspace by verifying GitHub connectivity, linking Coolify, and provisioning greenfield apps.

Instructions

Workspace setup: gh preflight, Coolify linkage, optional greenfield provisioning. Actions: preflight() · wire(mode, set_env?, env_file?, env_content?, ...) · resume(mode?, set_env?, env_file?, env_content?, ...) Safety: optional instance · no auto-push · gh soft-pause

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoSetup mode for wire/resume
pageNoPage number for pagination
pushNoPush to GitHub after repo create (default false)
typeNoOne-click service type
actionYesThe action to run
formatNoOutput format style
revealNoReveal sensitive/masked values in full projection (default false — secrets masked as ***)
db_nameNoDatabase name for create-app-db
domainsNoComma-separated domains when include_domains
env_keyNoEnv key for create-app-db
set_envNoSync env vars after wire (default false)
skip_ghNoSkip gh preflight (link-existing without repo step)
app_nameNoApplication name for create-app-db
env_fileNoLocal filesystem path to a .env file
instanceNoCoolify instance name from registry (optional — uses env credentials or registry default)
per_pageNoItems per page
db_engineNoDatabase engine for create-app-db
max_charsNoMaximum characters in text response before truncation
repo_nameNoGitHub repo name for greenfield create
repo_pathNoLocal repo path for create-git-app
build_packNoBuild pack for create-git-app
git_branchNoGit branch for create-git-app
projectionNoDetail projection depth
env_contentNoInline .env file content
recipe_typeNoRecipe action for greenfield wire
server_uuidNoTarget server UUID
include_fullNoAlias for projection: full
project_nameNoProject name for lookup
project_uuidNoProject UUID
git_repositoryNoGit repository URL for create-git-app
instant_deployNoInstant deploy for recipe create
include_domainsNoAttach domains after wire (default false)
application_uuidNoExisting application UUID for link-existing manifest
deploy_and_watchNoDeploy and watch after wire (default false)
environment_nameNoEnvironment name
environment_uuidNoEnvironment UUID
initial_environmentNoInitial environment name for greenfield project create

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?

The description adds safety-related behavior beyond the annotations, such as 'no auto-push' and 'optional instance', which is useful. However, it doesn't disclose other important traits like auth requirements, rate limits, or side effects, and the 'gh soft-pause' note is cryptic and unclear.

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 exceptionally concise, using three short lines to convey purpose, actions, and safety. Each sentence has a distinct role, and there is no wasted wording.

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 high complexity (37 parameters, 3 actions), the description is too brief. It doesn't explain the differences between actions, which parameters belong to which action, or how the output schema relates to the tool's behavior. The description leaves many questions unanswered.

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?

The schema provides 100% parameter descriptions, so the baseline is 3. The description's action signatures (e.g., wire(mode, set_env?, ...)) do not add meaningful semantics beyond what the schema already offers.

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

Purpose4/5

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

The description clearly states the tool is for workspace setup, involving gh preflight, Coolify linkage, and optional greenfield provisioning. It lists specific actions (preflight, wire, resume), giving a general sense of the tool's scope, but it doesn't fully explain what each action does, so it's not as clear as it could be.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternative tools like deployment or resource. There's no mention of when to use preflight vs wire vs resume, or any exclusions or 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/clezcoding/awesome-coolify'

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