mcpt

Docs Add server

Trigger.dev

by Trigger.dev

Create and debug background jobs with a developer-first framework.

Updated 5 days ago

Official

Go to documentation

npx @mintlify/mcp add trigger --client claude

Setup

Run the command above and follow the instructions in the CLI.

If you run into any issues, please don't hesitate to contact support.

Available tools

activate-schedule

Activate a schedule by its ID. This will only work on `IMPERATIVE` schedules that were created in the dashboard or using the imperative SDK functions like `schedules.create()`.

batch-trigger-tasks

Batch trigger tasks with up to 500 payloads.

cancel-a-run

Cancels an in-progress run. If the run is already completed, this will have no effect.

create-a-schedule

Create a new `IMPERATIVE` schedule based on the specified options.

create-an-event

Send an event to Trigger.dev to trigger job runs through eventTrigger()

create-environment-variable

Create a new environment variable for a specific project and environment.

deactivate-schedule

Deactivate a schedule by its ID. This will only work on `IMPERATIVE` schedules that were created in the dashboard or using the imperative SDK functions like `schedules.create()`.

delete-environment-variable

Delete a specific environment variable for a specific project and environment.

delete-schedule

Delete a schedule by its ID. This will only work on `IMPERATIVE` schedules that were created in the dashboard or using the imperative SDK functions like `schedules.create()`.

get-all-supported-timezones

Get all supported timezones that schedule tasks support.

list-all-schedules

List all schedules. You can also paginate the results.

list-environment-variables

List all environment variables for a specific project and environment.

list-project-runs

List runs in a project, across multiple environments, using Personal Access Token auth. You can filter the runs by status, created at, task identifier, version, and more.

list-runs

List runs in a specific environment. You can filter the runs by status, created at, task identifier, version, and more.

replay-a-run

Creates a new run with the same payload and options as the original run.

rescheduled-a-delayed-run

Updates a delayed run with a new delay. Only valid when the run is in the DELAYED state.

retrieve-a-run

Retrieve information about a run, including its status, payload, output, and attempts. If you authenticate with a Public API key, we will omit the payload and output fields for security reasons.

retrieve-environment-variable

Retrieve a specific environment variable for a specific project and environment.

retrieve-schedule

Get a schedule by its ID.

search

Search across the Trigger.dev documentation to fetch relevant context for a given query

trigger-a-task

Trigger a task by its identifier.

update-environment-variable

Update a specific environment variable for a specific project and environment.

update-run-metadata

Update the metadata of a run.

update-schedule

Update a schedule by its ID. This will only work on `IMPERATIVE` schedules that were created in the dashboard or using the imperative SDK functions like `schedules.create()`.

upload-environment-variables

Upload mulitple environment variables for a specific project and environment.