Activity

Summary

The deploy tool has a parameter named tag_or_uuid but it only seems to accept Coolify tags, not application UUIDs.

What I was trying to do

Trigger a deployment of an application after pushing code changes. I had the application UUID from list_applications.

Steps to reproduce

1. List applications to get the UUID:

mcp__coolify__list_applications

Returns (truncated):

{
  "uuid": "o8wg40wgs8ckc0c4wscs4cw4",
  "name": "devtrends",
  "status": "running:healthy",
  "fqdn": "https://trends.stumason.dev"
}

1. Verify the UUID works with other tools:

mcp__coolify__get_application
  uuid: "o8wg40wgs8ckc0c4wscs4cw4"

✅ Works - returns full application details

1. Try to deploy using the same UUID:

mcp__coolify__deploy
  tag_or_uuid: "o8wg40wgs8ckc0c4wscs4cw4"

Expected: Deployment triggered

Actual:

Error: No resources found with this tag.

The confusion

The parameter is named tag_or_uuid which implies both should work. But the error message says "No resources found with this tag" - suggesting it's only looking for Coolify tags (resource labels), not UUIDs.

This is inconsistent with other tools like get_application which accept UUIDs directly.

Desired behavior

Either:

1. The deploy tool should accept application UUIDs (matching the parameter name), or
2. There should be a separate tool like deploy_application that accepts a UUID