Activity

Description:

The coolify_application MCP tool has a schema validation bug that prevents any write operations, including updating application settings like build pack, environment variables, etc.

Reproduction Steps:

1. Create an application via Coolify web UI with incorrect build pack (dockerfile instead of dockercompose)
2. Attempt to update via MCP:

{
  "action": "update",
  "uuid": "",
  "build_pack": "dockercompose"
}

Expected: Build pack updated to dockercompose Actual:

Validation failed. - action: This field is not allowed.; uuid: This field is not allowed.

Affected Actions (all fail with same error):

• create_github - Cannot create GitHub-connected apps
• create_dockerimage - Cannot create Docker image apps
• create_key - Cannot create SSH key apps
• update - Cannot update any application settings
• delete - Cannot delete applications

Working MCP Operations (read-only):

• coolify_list_applications - Lists applications ✓
• coolify_get_application - Gets application details ✓
• coolify_application_logs - Gets logs ✓
• coolify_deploy - Triggers deployment ✓

Root Cause:

The MCP tool schema appears to have conflicting validation rules:

1. action parameter is required but all valid values are rejected
2. uuid parameter is required for update but rejected as "not allowed"

Impact:

The MCP tool is effectively read-only. Users cannot:

• Create new applications via MCP
• Update any application settings (build pack, env vars, etc.) via MCP
• Delete applications via MCP
• Create services via MCP

Workaround:

Use Coolify web UI or REST API directly:

# Update build pack via API
curl -X PATCH "https://coolify.example.com/api/v1/applications/<uuid>" \
  -H "Authorization: Bearer <TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"build_pack": "dockercompose"}'