Learn about the tools available in the Trigger.dev MCP Server
The Trigger.dev MCP Server provides a comprehensive set of tools that enable AI assistants to interact with your Trigger.dev projects. These tools cover everything from project management to task execution and monitoring.
The organization to create the project in, can either be the organization slug or the ID. Use the
list_orgs tool to get a list of organizations and ask the user to select one.
The organization to create the project in, can either be the organization slug or the ID. Use the
list_orgs tool to get a list of organizations and ask the user to select one.
The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the
project ref if running inside a directory that includes a trigger.config.ts file.
The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the
project ref if running inside a directory that includes a trigger.config.ts file.
The path to the trigger.config.ts file. Only used when the trigger.config.ts file is not at the
root dir (like in a monorepo setup). If not provided, we will try to find the config file in the
current working directory.
The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the
project ref if running inside a directory that includes a trigger.config.ts file.
The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the
project ref if running inside a directory that includes a trigger.config.ts file.
Enable debug mode to get more detailed information about the run, including the entire trace (all logs and spans for the run and any child run). Set this to true if prompted to debug a run.
The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the
project ref if running inside a directory that includes a trigger.config.ts file.
The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the
project ref if running inside a directory that includes a trigger.config.ts file.
The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the
project ref if running inside a directory that includes a trigger.config.ts file.
The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the
project ref if running inside a directory that includes a trigger.config.ts file.
The trigger.dev project ref, starts with proj_. We will attempt to automatically detect the
project ref if running inside a directory that includes a trigger.config.ts file.
The path to the trigger.config.ts file. Only used when the trigger.config.ts file is not at the
root dir (like in a monorepo setup). If not provided, we will try to find the config file in the
current working directory.