Trigger.dev MCP by usefulapi MCP Prompts

Trigger.dev MCP by usefulapi offers 7 prompts. A prompt is one you invoke yourself, rather than a tool the model calls on your behalf — each has its own page with the configuration for every client that can run it.

getting_started

getting started
find_failed_runs_and_read_their_errors

find failed runs and read their errors
find_where_a_run_spent_its_time_or_broke

find where a run spent its time or broke
check_queues_that_are_backing_up

check queues that are backing up
review_cron_schedules_and_their_next_runs

review cron schedules and their next runs
pause_or_resume_a_schedule_or_a_queue

pause or resume a schedule or a queue
cancel_replay_reschedule_or_tag_a_run

cancel replay reschedule or tag a run

Read from the server itself, by connecting to it and calling prompts/list on 5 November 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.

Trigger.dev MCP by usefulapi MCP server