Trigger.dev MCP by usefulapi
io.usefulapi/trigger-dev · v1.11.1
Debug background jobs — runs, traces, spans, schedules, queues and deployments.
MCPremoteno credentialsTasks & projects
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 22 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 88/100
What it does: 22 tools · 15 read, 7 write (incl. delete/pay) · Tasks & projects
No tool could be tested safely. Only read-only tools that need no input are called.
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: +5
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://trigger-dev.usefulapi.io/mcpTools
22 tools listed at last check
trigger_list_runsList task runs, filtered by status, task, tag, queue, schedule or a time window. This is the main read for 'what ran, and what failed?'. Trigger.dev: GET /api/v1/runs.trigger_get_runFetch a single run's outcome — its status, output, error and attempts. Trigger.dev: GET /api/v1/runs/{runId}/result.trigger_get_run_traceFetch the full execution trace of a run — every span, with timings and nesting. The tool for 'where did this run spend its time, and where did it break?'. Trigger.dev: GET /api/v1/runs/{runId}/trace.trigger_get_run_spanFetch a single span from a run's trace, with its own logs and attributes. Trigger.dev: GET /api/v1/runs/{runId}/spans/{spanId}.trigger_list_run_eventsList the lifecycle events of one run — queued, dequeued, started, retried, completed. Trigger.dev: GET /api/v1/runs/{runId}/events.trigger_get_run_metadataFetch the mutable metadata a run has written about itself — progress, checkpoints and custom state. Trigger.dev: GET /api/v1/runs/{runId}/metadata.trigger_get_batch_resultsFetch the outcome of every run in a batch. Trigger.dev: GET /api/v1/batches/{batchId}/results.trigger_list_schedulesList the cron schedules configured for tasks, with their next run times. Trigger.dev: GET /api/v1/schedules.trigger_get_scheduleFetch a single schedule with its cron expression, timezone and active state. Trigger.dev: GET /api/v1/schedules/{scheduleId}.trigger_list_queuesList task queues with their concurrency limits and current depth — where you look when work is backing up. Trigger.dev: GET /api/v1/queues.trigger_get_queueFetch a single queue's concurrency limit, running count and queued count. Trigger.dev: GET /api/v1/queues/{queue}.trigger_get_current_deploymentFetch the deployment currently serving the key's environment — its version, git ref and status. Trigger.dev: GET /api/v1/deployments/current.trigger_list_env_varsList the environment variables configured for a project environment. Values may be redacted depending on the key's permissions. READ ONLY — this server exposes no env-var writes. Trigger.dev: GET /api/v1/projects/{projectRef}/envvars/{env}.trigger_list_waitpoint_tokensList outstanding waitpoint tokens — runs paused waiting for an external signal. Trigger.dev: GET /api/v1/waitpoints/tokens.trigger_list_bulk_actionsList bulk replay and cancel operations and their progress. Trigger.dev: GET /api/v1/bulk-actions.trigger_cancel_runCancel an in-flight run. Note this is the one endpoint on API v2, not v1. Trigger.dev: POST /api/v2/runs/{runId}/cancel.trigger_replay_runRe-run one specific past run with the same payload. This EXECUTES your production task again — the same side effects it had the first time. Trigger.dev: POST /api/v1/runs/{runId}/replay.trigger_reschedule_runChange when a delayed run will execute. Only applies to runs that have not started. Trigger.dev: POST /api/v1/runs/{runId}/reschedule.trigger_add_run_tagsAttach tags to a run so you can filter for it later. Additive and safe. Trigger.dev: POST /api/v1/runs/{runId}/tags.trigger_activate_scheduleResume a paused schedule so it fires again. Trigger.dev: POST /api/v1/schedules/{scheduleId}/activate.trigger_deactivate_schedulePause a schedule so it stops firing. The usual first move when a scheduled task is misbehaving. Trigger.dev: POST /api/v1/schedules/{scheduleId}/deactivate.trigger_pause_queuePause a queue so its runs stop being dequeued, or resume it. The containment move when a task is failing in a loop. Trigger.dev: POST /api/v1/queues/{queue}/pause.
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.usefulapi/trigger-dev)