StuMason/coolify-mcp
TypeScript
Issue Opened
Issue #208 opened: Add trigger action to scheduled_tasks tool for one-shot execution
Summary
The scheduled_tasks MCP tool supports list, create, update, delete, and list_executions but has no way to trigger a one-shot run of an existing scheduled task without mutating its cron frequency.
Use case
social-risk-intelligence runs Coolify scheduled tasks (dbt silver, bronze ingest, etc.) as one-shot docker exec invocations documented in https://github.com/Shirudo-Solutions/social-risk-intelligence/blob/main/docs/deployment.md#manual-one-shot-scheduled-task-runs-docker-exec. Operators and agents need a safe API/MCP path to fire a task once after deploy verification without editing cron.
Proposed API
Add action: "trigger" (or "run") accepting resource, uuid (app), and task_uuid, mapping to the upstream Coolify HTTP API if/when it exists.
Related
- Upstream Coolify feature request (if endpoint missing): coollabsio/coolify
- Consumer docs: Shirudo-Solutions/social-risk-intelligence PR #57