Model Context Protocol server for Rollbar
Trigger Dev is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Debug background jobs — runs, traces, spans, schedules, queues and deployments.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http usefulapi-trigger-dev-mcp https://trigger-dev.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# trigger_list_runs, trigger_get_run, trigger_get_run_trace and 19 more
Trigger Dev costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http usefulapi-trigger-dev-mcp https://trigger-dev.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
22 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | array | no | Only runs in these states, e.g. ["FAILED","CRASHED"]. Others include PENDING, EXECUTING, COMPLETED, CANCELED, TIMED_OUT. |
| taskIdentifier | array | no | Only runs of these task ids. |
| tag | array | no | Only runs carrying these tags. |
| queue | array | no | Only runs on these queues. |
| machine | array | no | Only runs on these machine presets. |
| version | string | no | Only runs of this deployment version. |
| schedule | string | no | Only runs created by this schedule. |
| batch | string | no | Only runs in this batch. |
| isTest | boolean | no | Only test runs, or only real ones. |
| period | string | no | Relative window, e.g. "1h", "24h", "7d". |
| from | string | no | Epoch milliseconds lower bound on creation time. |
| to | string | no | Epoch milliseconds upper bound on creation time. |
| pageSize | integer | no | Page size, 1-100. |
| after | string | no | Cursor from the previous page's pagination. Omit for the first page. |
Fetch a single run's outcome — its status, output, error and attempts. Trigger.dev: GET /api/v1/runs/{runId}/result.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| run_id | string | yes | The run's id (run_...). |
Fetch 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| run_id | string | yes | The run's id. |
Fetch a single span from a run's trace, with its own logs and attributes. Trigger.dev: GET /api/v1/runs/{runId}/spans/{spanId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| run_id | string | yes | The run's id. |
| span_id | string | yes | The span's id, from the trace. |
List the lifecycle events of one run — queued, dequeued, started, retried, completed. Trigger.dev: GET /api/v1/runs/{runId}/events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| run_id | string | yes | The run's id. |
Fetch the mutable metadata a run has written about itself — progress, checkpoints and custom state. Trigger.dev: GET /api/v1/runs/{runId}/metadata.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| run_id | string | yes | The run's id. |
Fetch the outcome of every run in a batch. Trigger.dev: GET /api/v1/batches/{batchId}/results.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| batch_id | string | yes | The batch's id (batch_...). |
List the cron schedules configured for tasks, with their next run times. Trigger.dev: GET /api/v1/schedules.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pageSize | integer | no | Page size, 1-100. |
| page | integer | no | 1-based page number. |
Fetch a single schedule with its cron expression, timezone and active state. Trigger.dev: GET /api/v1/schedules/{scheduleId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schedule_id | string | yes | The schedule's id (sched_...). |
List task queues with their concurrency limits and current depth — where you look when work is backing up. Trigger.dev: GET /api/v1/queues.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pageSize | integer | no | Page size, 1-100. |
Fetch a single queue's concurrency limit, running count and queued count. Trigger.dev: GET /api/v1/queues/{queue}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| queue | string | yes | The queue's name or id. |
Fetch the deployment currently serving the key's environment — its version, git ref and status. Trigger.dev: GET /api/v1/deployments/current.
No parameter schema on file.
List 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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_ref | string | yes | The project reference (proj_...). |
| environment | string | yes | Which environment's variables to list. |
List outstanding waitpoint tokens — runs paused waiting for an external signal. Trigger.dev: GET /api/v1/waitpoints/tokens.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pageSize | integer | no | Page size, 1-100. |
| after | string | no | Cursor from the previous page's pagination. Omit for the first page. |
List bulk replay and cancel operations and their progress. Trigger.dev: GET /api/v1/bulk-actions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pageSize | integer | no | Page size, 1-100. |
Cancel an in-flight run. Note this is the one endpoint on API v2, not v1. Trigger.dev: POST /api/v2/runs/{runId}/cancel.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| run_id | string | yes | The run to cancel. |
Re-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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| run_id | string | yes | The run to replay. |
Change when a delayed run will execute. Only applies to runs that have not started. Trigger.dev: POST /api/v1/runs/{runId}/reschedule.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| run_id | string | yes | The delayed run to move. |
| delay | string | yes | New delay or timestamp, e.g. "1h" or an ISO-8601 datetime. |
Attach tags to a run so you can filter for it later. Additive and safe. Trigger.dev: POST /api/v1/runs/{runId}/tags.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| run_id | string | yes | The run to tag. |
| tags | array | yes | Tags to add. |
Resume a paused schedule so it fires again. Trigger.dev: POST /api/v1/schedules/{scheduleId}/activate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schedule_id | string | yes | The schedule to activate. |
Pause a schedule so it stops firing. The usual first move when a scheduled task is misbehaving. Trigger.dev: POST /api/v1/schedules/{scheduleId}/deactivate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schedule_id | string | yes | The schedule to pause. |
Pause 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| queue | string | yes | The queue's name or id. |
| paused | boolean | yes | true to pause, false to resume. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Trigger Dev or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Trigger Dev can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.