nicktrn
7c791dd519
* shard unit tests * temp enable for all pushes * fix test workflow * update to latest vitest and only add to root package.json * additionally use default reporter * gather reports before uploading * split up slow replication tests * split up unit tests workflow * move workflows to parent dir * use new paths in parent workflow * prevent artifact clashes * we always need to create the reports dir * speed up merge reports * gather reports even when tests fail * fix artifact patterns * increase shards * disable push trigger again * improve dequeue snapshot test reliability
Trigger.dev CLI
A CLI that allows you to create, run locally and deploy Trigger.dev background tasks.
Note: this only works with Trigger.dev v3 projects and later. For older projects use the @trigger.dev/cli package.
Trigger.dev is an open source platform that makes it easy to create event-driven background tasks directly in your existing project.
Commands
| Command | Description |
|---|---|
| login | Login with Trigger.dev so you can perform authenticated actions. |
| init | Initialize your existing project for development with Trigger.dev. |
| dev | Run your Trigger.dev tasks locally. |
| deploy | Deploy your Trigger.dev v3 project to the cloud. |
| whoami | Display the current logged in user and project details. |
| logout | Logout of Trigger.dev. |
| list-profiles | List all of your CLI profiles. |
| update | Updates all @trigger.dev/* packages to match the CLI version. |
MCP Server
The Model Context Protocol (MCP) is an open protocol that allows you to provide custom tools to agentic LLM clients, like Claude for Desktop, Cursor, Windsurf, etc...
The Trigger.dev CLI can expose an MCP server and enable you interact with Trigger.dev in agentic LLM workflows. For example, you can use it to trigger tasks via natural language, view task runs, view logs, debug issues with task runs, etc...
Starting the Trigger.dev MCP Server
To start the Trigger.dev MCP server, simply pass the --mcp flag to the dev command:
trigger dev --mcp
By default it runs on port 3333. You can change this by passing the --mcp-port flag:
trigger dev --mcp --mcp-port 3334
Configuring your MCP client
This depends on what tool you are using. For Cursor, the configuration is in the .cursor/mcp.json file and should be good to go as long as you use the default MCP server port.
Check out Cursor's docs for further details.
Tip: try out Cursor's YOLO mode for a seamless experience :D
Support
If you have any questions, please reach out to us on Discord and we'll be happy to help.