io.usefulapiPublished by usefulapi.ioOfficial publisherv1.39.2Updated Nov 14, 2026
Debug background jobs — runs, traces, spans, schedules, queues and deployments.
The publisher's own server: Ably MCP by usefulapi
Hosted MCP server that lets an assistant inspect and control Trigger.dev background jobs: runs, traces, spans, schedules, queues and deployments.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.usefulapi%2Ftrigger-dev/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"trigger-dev-by-usefulapi": {
"type": "http",
"url": "https://trigger-dev.usefulapi.io/mcp"
}
}
}Debug background jobs — runs, traces, spans, schedules, queues and deployments. Hosted, no local install.
Live endpoint: https://trigger-dev.usefulapi.io/mcp · Homepage: https://usefulapi.io
https://trigger-dev.usefulapi.io/mcp.claude mcp add --transport http trigger-dev https://trigger-dev.usefulapi.io/mcp, then run /mcp to log in.Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Trigger.dev credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/trigger-dev/
On first connect you'll paste your Trigger.dev credentials. They are validated, stored per-user, and scoped to you — no keys in config files.
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
Each paid plan covers this server only. Ask your AI to run trigger_dev_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with trigger_dev_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with trigger_dev_upgrade before then undoes the cancel. Or write to [email protected].
MIT
Source: servers/trigger-dev/README.md at commit f22f848
List runs
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.
totagfromafterbatchqueueisTestperiodstatusmachineversionpageSize+2 moreGet one run
Fetch a single run's outcome — its status, output, error and attempts. Trigger.dev: GET /api/v1/runs/{runId}/result.
run_idrequiredGet a run's trace
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.
run_idrequiredGet one span of a run
Fetch a single span from a run's trace, with its own logs and attributes. Trigger.dev: GET /api/v1/runs/{runId}/spans/{spanId}.
run_idrequiredspan_idrequiredList a run's events
List the lifecycle events of one run — queued, dequeued, started, retried, completed. Trigger.dev: GET /api/v1/runs/{runId}/events.
run_idrequiredGet a run's metadata
Fetch the mutable metadata a run has written about itself — progress, checkpoints and custom state. Trigger.dev: GET /api/v1/runs/{runId}/metadata.
run_idrequiredGet a batch's results
Fetch the outcome of every run in a batch. Trigger.dev: GET /api/v1/batches/{batchId}/results.
batch_idrequiredList schedules
List the cron schedules configured for tasks, with their next run times. Trigger.dev: GET /api/v1/schedules.
pagepageSizeGet one schedule
Fetch a single schedule with its cron expression, timezone and active state. Trigger.dev: GET /api/v1/schedules/{scheduleId}.
schedule_idrequiredList queues
List task queues with their concurrency limits and current depth — where you look when work is backing up. Trigger.dev: GET /api/v1/queues.
pageSizeGet one queue
Fetch a single queue's concurrency limit, running count and queued count. Trigger.dev: GET /api/v1/queues/{queue}.
queuerequiredGet the current deployment
Fetch the deployment currently serving the key's environment — its version, git ref and status. Trigger.dev: GET /api/v1/deployments/current.
Takes no parameters.
List environment variables
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}.
environmentrequiredproject_refrequiredList waitpoint tokens
List outstanding waitpoint tokens — runs paused waiting for an external signal. Trigger.dev: GET /api/v1/waitpoints/tokens.
afterpageSizeList bulk actions
List bulk replay and cancel operations and their progress. Trigger.dev: GET /api/v1/bulk-actions.
pageSizeCancel a run
Cancel an in-flight run. Note this is the one endpoint on API v2, not v1. Trigger.dev: POST /api/v2/runs/{runId}/cancel.
run_idrequiredReplay a run
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.
run_idrequiredReschedule a delayed run
Change when a delayed run will execute. Only applies to runs that have not started. Trigger.dev: POST /api/v1/runs/{runId}/reschedule.
delayrequiredrun_idrequiredAdd tags to a run
Attach tags to a run so you can filter for it later. Additive and safe. Trigger.dev: POST /api/v1/runs/{runId}/tags.
tagsrequiredrun_idrequiredActivate a schedule
Resume a paused schedule so it fires again. Trigger.dev: POST /api/v1/schedules/{scheduleId}/activate.
schedule_idrequiredDeactivate a schedule
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.
schedule_idrequiredPause or resume a queue
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.
queuerequiredpausedrequired100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
io.usefulapiOfficial publisher
Hosted MCP server for Ably that lets an assistant inspect realtime channels, presence and usage stats, publish messages, and review app configuration.
io.usefulapiOfficial publisher
Read-only access to ROLLER venue data: search bookings, check product availability, and look up guests, waivers, gift cards and daily reports.
io.usefulapiOfficial publisher
Hosted Planerio connector that lets an assistant read shifts, staffing requirements, staff, employees, absences and vacation days.
io.usefulapiOfficial publisher
Read-only access to Marmin UAE e-invoicing data: invoices, credit notes, UBL XML, Peppol status and business profiles.
io.usefulapiOfficial publisher
Remote MCP server for Oyster that lets an assistant read team, time off, expense, contract and invoice data and approve or decline requests.
{ "mcpServers": { "trigger-dev": { "url": "https://trigger-dev.usefulapi.io/mcp" } }}