Can AI agents automate Trigger.dev?

Trigger.dev is automatable today through its management API, used from the official TypeScript package @trigger.dev/sdk. An environment secret key, passed as secretKey or TRIGGER_SECRET_KEY, starts with tr_dev_sk_, tr_prod_sk_, or tr_preview_sk_ and is limited to that environment. A personal access token starts with tr_pat_ and can list runs and manage environment variables, but the authentication table does not show it triggering tasks. The same CLI, npx trigger.dev, initializes projects, runs tasks locally, deploys, and lists, inspects, replays, and cancels runs. Trigger.dev documents an official MCP server as npx trigger.dev@latest mcp. search_docs works without login. Other tools use the CLI login. --dev-only and --readonly are documented, and read-only mode hides deploy, trigger_task, and cancel_run. The homepage says Trigger.dev is Apache 2.0 licensed and can be self-hosted. Cloud pricing publishes a Free plan at $0 per month. https://trigger.dev/docs/llms.txt is a first-party documentation index. Zapier, Make, Power Automate, and n8n were not assessed. Computer-use viability is unassessed. API, CLI, and MCP each score 7. API is the best path because an environment secret key calls management operations from the SDK without an MCP client.

Best path today: api · Overall automatability: 7/10