A Claude Code skill for interacting with Coolify's REST API to manage servers, projects, applications, databases, and deployments.
- Server Management: Monitor and manage Coolify servers
- Project Operations: Create, update, and delete projects
- Application Lifecycle: Deploy, start, stop, and restart applications
- Database Management: Control database instances
- Service Control: Manage containerized services
- Deployment Tracking: View deployment history and logs
- Environment Variables: Manage application configuration
- Webhook Integration: Set up event notifications
# Copy the skill to your Claude Code skills directory
cp -r skill-coolify ~/.claude/skills/coolify-api# Linux/macOS
ln -s $(pwd)/skill-coolify ~/.claude/skills/coolify-api
# Windows (PowerShell as Administrator)
New-Item -ItemType Junction -Path "$env:USERPROFILE\.claude\skills\coolify-api" -Target "$(Get-Location)\skill-coolify"The skill automatically loads when you use phrases like:
- "Check Coolify status"
- "List my Coolify projects"
- "Deploy to Coolify"
- "Use the Coolify API"
- "Manage my Coolify server"
Once loaded, Claude will have access to the Coolify API documentation and can help you:
# Check server health (no authentication required)
"Check the health of my Coolify instance at http://192.168.1.100:8000"
# List projects (authentication required)
"Using my API token, list all Coolify projects"
# Deploy an application
"Deploy the application with UUID abc-123"
Before using the Coolify API, you must enable it in your instance:
- Go to Settings > Advanced in your Coolify dashboard.
- Enable the API Access setting.
If enabled, authenticated requests to Coolify's REST API will be allowed. Configure API tokens in Security > API Tokens. (
/security/api-tokens)
To use this skill, you need:
- Server URL: Your Coolify instance address (e.g.,
http://192.168.1.100:8000) - API Token: Your generated Bearer token
| Setting | Value |
|---|---|
| Base URL | http://<ip>:8000/api |
| API Prefix | /v1 (except /health and /feedback) |
| Auth Header | Authorization: Bearer <token> |
- Navigate to your Coolify dashboard
- Go to Security > API tokens (or Keys & Tokens > API tokens depending on your version)
- Enter a name and click Create New Token
- Copy the token immediately (shown only once)
| Permission | Read | Write | View Sensitive |
|---|---|---|---|
read-only |
Yes | No | No |
read:sensitive |
Yes | No | Yes |
view:sensitive |
Yes | No | Yes |
* (full access) |
Yes | Yes | Yes |
GET /health
No authentication required. Returns server status.
GET /v1/projects
Authorization: Bearer 1|your-api-token-hereGET /v1/applications/{uuid}/deploy
Authorization: Bearer 1|your-api-token-herePOST /v1/applications/{uuid}/envs
Authorization: Bearer 1|your-api-token-here
Content-Type: application/json
{
"key": "DATABASE_URL",
"value": "postgres://localhost:5432/mydb"
}When exposing a service (Docker Compose) as a subdomain, you must use the urls field:
PATCH /v1/services/{uuid}
Content-Type: application/json
{
"urls": [
{
"name": "service-name",
"url": "https://subdomain.domain.tld"
}
]
}Important:
- Use
urlsfield (NOTfqdnordomains) namemust match the service name in docker-compose.yml- URL must include protocol (
https://orhttp://)
See references/service-domains.md for full documentation.
skill-coolify/
├── SKILL.md # Main skill definition (YAML + instructions)
├── README.md # This documentation file
├── LICENSE.md # MIT License
├── CHANGELOG.md # Version history
├── references/
│ ├── authorization.md # Authentication & permissions guide
│ ├── openapi.json # OpenAPI 3.1.0 specification
│ └── service-domains.md # Service domain/URL configuration
└── workflows/
└── deploy-filebrowser.md # Workflow for deploying Filebrowser
The API returns rate limit information in response headers:
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 59This skill is provided as-is for use with Claude Code and the Coolify platform.
- Skill Version: 1.3.2
- Compatible with: Coolify v4.x API
