| name | cli-recipes |
| description | Trigger.dev CLI commands for development, deployment, MCP setup, and project management. Use when the user asks about "trigger.dev CLI", "npx trigger.dev", "trigger.dev dev server", "trigger.dev deploy command", "trigger.dev mcp install", "trigger.dev profiles", or needs ready-to-use CLI commands. |
Trigger.dev CLI Recipes
The CLI is bundled with the SDK — no separate install:
npx trigger.dev@latest <command>
Authentication
npx trigger.dev@latest login
npx trigger.dev@latest login -a https://trigger.example.com
npx trigger.dev@latest login -a https://trigger.example.com --profile self-hosted
npx trigger.dev@latest whoami
Profile Management
npx trigger.dev@latest list-profiles
npx trigger.dev@latest switch
npx trigger.dev@latest switch self-hosted
npx trigger.dev@latest logout --profile self-hosted
Project Initialization
npx trigger.dev@latest init
npx trigger.dev@latest init -p proj_xxx -a https://trigger.example.com
npx trigger.dev@latest init --runtime bun
npx trigger.dev@latest init --javascript
Development Server
npx trigger.dev@latest dev
npx trigger.dev@latest dev --config ./packages/jobs/trigger.config.ts
npx trigger.dev@latest dev --log-level debug
npx trigger.dev@latest dev --profile self-hosted
The dev server watches for file changes, registers tasks, and executes them locally.
Deployment
npx trigger.dev@latest deploy
npx trigger.dev@latest deploy --env staging
npx trigger.dev@latest deploy --env preview --branch feature/new-task
npx trigger.dev@latest deploy --skip-promotion
MCP Server
npx trigger.dev@latest install-mcp
npx trigger.dev@latest install-mcp --client claude-code
npx trigger.dev@latest install-mcp --client cursor --scope user
npx trigger.dev@latest install-mcp --yolo
npx trigger.dev@latest install-mcp --readonly
npx trigger.dev@latest install-mcp --dev-only --project-ref proj_abc123
install-mcp Flags
| Flag | Purpose |
|---|
--client <name...> | claude-code, cursor, windsurf, vscode, zed, cline, gemini-cli, amp, openai-codex, crush, opencode, ruler |
--scope <scope> | user / project / local |
--dev-only | Hide deploy / list_preview_branches — only dev env tools exposed |
--readonly | Hide deploy, trigger_task, cancel_run (AI can read but not mutate) |
--project-ref <ref> | Lock MCP to one project |
--tag <tag> | Pin CLI version |
-a, --api-url <url> | Self-hosted API URL |
--log-file <path> | Write MCP server logs to file |
--log-level <level> | debug / info / log / warn / error / none |
--yolo | Install into every supported client |
Manual Config
{
"mcpServers": {
"trigger": {
"command": "npx",
"args": ["trigger.dev@latest", "mcp"]
}
}
}
Dev-only + project-scoped example:
{
"mcpServers": {
"trigger": {
"command": "npx",
"args": ["trigger.dev@latest", "mcp", "--dev-only", "--project-ref", "proj_abc123", "--readonly"]
}
}
}
Platform Notifications
Since v4.4.4, trigger dev and trigger login fetch server-side notifications (info/warn/error/success) with color markup. Disable with --skip-platform-notifications:
npx trigger.dev@latest dev --skip-platform-notifications
Agent Rules
npx trigger.dev@latest install-rules
| Rule Set | Tokens | Description |
|---|
| Basic tasks | 1,200 | Core task writing patterns |
| Advanced tasks | 3,000 | Complex workflows, error handling |
| Scheduled tasks | 780 | Cron/scheduled tasks |
| Configuration | 1,900 | trigger.config.ts setup |
| Realtime | 1,700 | Realtime API and React hooks |
Rules auto-update when you run npx trigger.dev@latest dev.
Self-Hosted Docker
git clone --depth=1 https://github.com/triggerdotdev/trigger.dev
cd trigger.dev/hosting/docker
cd webapp && docker compose up -d
cd ../worker && docker compose up -d
docker compose logs -f webapp
docker compose logs -f supervisor
docker compose ps
TRIGGER_IMAGE_TAG=v4.0.0
Package.json Scripts
{
"scripts": {
"trigger:dev": "trigger.dev dev",
"trigger:deploy:staging": "trigger.dev deploy --env staging",
"trigger:deploy:prod": "trigger.dev deploy --env production"
}
}
Common Issues
| Issue | Solution |
|---|
| Cannot find trigger.config.ts | Run from project root or pass --config |
| Authentication failed | Check TRIGGER_SECRET_KEY or re-login |
| Connection refused | Verify TRIGGER_API_URL and instance health |
| No tasks found | Ensure task files are in configured dirs |
| Redirected to cloud | Use login -a <url> or set TRIGGER_API_URL |
| Registry push fails | docker login -u user registry:5000 |