Trigger.dev MCP by usefulapi
Debug background jobs — runs, traces, spans, schedules, queues and deployments
What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: monitor production incidents.Similar tools
Listed for the same task: monitor production incidentsReviews
No review yet. Used Trigger.dev MCP by usefulapi? Be the first to help others choose.What it does
Trigger.dev MCP by usefulapi is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to 2 capabilities: debugging and devops automation. That makes it a candidate for tasks such as monitor production incidents or automate CI/CD pipelines.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)Hosted endpoint
https://trigger-dev.usefulapi.io/mcpstreamable-http
In Claude Code: claude mcp add --transport http trigger-dev https://trigger-dev.usefulapi.io/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"trigger-dev": {
"url": "https://trigger-dev.usefulapi.io/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 1d agoONLINE Trigger.dev MCP by usefulapi answered an MCP connection on 15 Nov 2026 and introduced itself as trigger-dev-mcp 1.39.2 (MCP protocol 2025-06-18).
22 tools offered to AI assistants
trigger_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.trigger_get_run· Fetch a single run's outcome — its status, output, error and attempts. Trigger.dev: GET /api/v1/runs/{runId}/result.trigger_get_run_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.trigger_get_run_span· Fetch 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_events· List the lifecycle events of one run — queued, dequeued, started, retried, completed. Trigger.dev: GET /api/v1/runs/{runId}/events.trigger_get_run_metadata· Fetch 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_results· Fetch the outcome of every run in a batch. Trigger.dev: GET /api/v1/batches/{batchId}/results.trigger_list_schedules· List the cron schedules configured for tasks, with their next run times. Trigger.dev: GET /api/v1/schedules.trigger_get_schedule· Fetch a single schedule with its cron expression, timezone and active state. Trigger.dev: GET /api/v1/schedules/{scheduleId}.trigger_list_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.trigger_get_queue· Fetch a single queue's concurrency limit, running count and queued count. Trigger.dev: GET /api/v1/queues/{queue}.trigger_get_current_deployment· Fetch the deployment currently serving the key's environment — its version, git ref and status. Trigger.dev: GET /api/v1/deployments/current.
Show 10 more
trigger_list_env_vars· 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}.trigger_list_waitpoint_tokens· List outstanding waitpoint tokens — runs paused waiting for an external signal. Trigger.dev: GET /api/v1/waitpoints/tokens.trigger_list_bulk_actions· List bulk replay and cancel operations and their progress. Trigger.dev: GET /api/v1/bulk-actions.trigger_cancel_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.trigger_replay_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.trigger_reschedule_run· Change 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_tags· Attach tags to a run so you can filter for it later. Additive and safe. Trigger.dev: POST /api/v1/runs/{runId}/tags.trigger_activate_schedule· Resume a paused schedule so it fires again. Trigger.dev: POST /api/v1/schedules/{scheduleId}/activate.trigger_deactivate_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.trigger_pause_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.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Version | 1.40.0 | DECLARED | SRC-001 Official MCP Registry | 22h ago |
| Hosted endpoint | https://trigger-dev.usefulapi.io/mcp | DECLARED | SRC-001 Official MCP Registry | 22h ago |
| Website | https://usefulapi.io/trigger-dev/ | DECLARED | SRC-001 Official MCP Registry | 22h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 22h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 22h ago |
| Repository | https://github.com/m190/usefulapi-mcp | DECLARED | SRC-001 Official MCP Registry | 22h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 22h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 22h ago |
Change history
- VERSION16 Nov 20261.39.3 → 1.40.0
- VERSION16 Nov 20261.39.2 → 1.39.3
- VERSION14 Nov 20261.39.1 → 1.39.2
- VERSION13 Nov 20261.39.0 → 1.39.1
- VERSION13 Nov 20261.38.0 → 1.39.0
- VERSION11 Nov 20261.37.3 → 1.38.0
- VERSION11 Nov 20261.37.2 → 1.37.3
- VERSION10 Nov 20261.37.1 → 1.37.2
- VERSION10 Nov 20261.37.0 → 1.37.1
- VERSION10 Nov 20261.36.5 → 1.37.0
- VERSION07 Nov 20261.36.4 → 1.36.5
- VERSION07 Nov 20261.36.3 → 1.36.4
- VERSION07 Nov 20261.36.2 → 1.36.3
- VERSION06 Nov 20261.36.1 → 1.36.2
- VERSION06 Nov 20261.35.4 → 1.36.1
- VERSION06 Nov 20261.35.3 → 1.35.4
- VERSION05 Nov 20261.35.2 → 1.35.3
- VERSION05 Nov 20261.35.1 → 1.35.2
- VERSION03 Nov 20261.35.0 → 1.35.1
- VERSION03 Nov 20261.34.1 → 1.35.0
- VERSION03 Nov 20261.34.0 → 1.34.1
- VERSION02 Nov 20261.33.0 → 1.34.0
- VERSION31 Oct 20261.32.0 → 1.33.0
- VERSION31 Oct 20261.31.0 → 1.32.0
- VERSION31 Oct 20261.30.0 → 1.31.0
- VERSION31 Oct 20261.29.2 → 1.30.0
- VERSION30 Oct 20261.29.1 → 1.29.2
- VERSION30 Oct 20261.29.0 → 1.29.1
- VERSION29 Oct 20261.28.0 → 1.29.0
- VERSION29 Oct 20261.27.0 → 1.28.0
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Trigger.dev MCP by usefulapi still online?
Free alerts · no account▲ 0Do you run Trigger.dev MCP by usefulapi? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Trigger.dev MCP by usefulapi
How do I connect Trigger.dev MCP by usefulapi?
Use the hosted endpoint https://trigger-dev.usefulapi.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Trigger.dev MCP by usefulapi offer?
When Electra Index connected on 15 Nov 2026, it listed 22 tools: trigger_list_runs, trigger_get_run, trigger_get_run_trace, trigger_get_run_span, trigger_list_run_events, trigger_get_run_metadata, trigger_get_batch_results, trigger_list_schedules and more. The full list is in "Live check" above.
Is Trigger.dev MCP by usefulapi online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.
What can I use Trigger.dev MCP by usefulapi for?
Based on its description, it is most relevant to: monitor production incidents, automate CI/CD pipelines, fix bugs in a codebase.