Debug background jobs — runs, traces, spans, schedules, queues and deployments. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"trigger-dev": {
"url": "https://trigger-dev.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"trigger-dev": {
"type": "http",
"url": "https://trigger-dev.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Trigger.dev secret key.
Copy it from your Trigger.dev project's API keys page. Your token is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
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: the login page asks for your Trigger.dev secret key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Trigger.dev connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
trigger_list_runs | read | 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 | read | Get one 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 | read | Get 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. |
trigger_get_run_span | read | Get 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}. |
trigger_list_run_events | read | List a run's 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 | read | Get 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. |
trigger_get_batch_results | read | Get a batch's results Fetch the outcome of every run in a batch. Trigger.dev: GET /api/v1/batches/{batchId}/results. |
trigger_list_schedules | read | List schedules List the cron schedules configured for tasks, with their next run times. Trigger.dev: GET /api/v1/schedules. |
trigger_get_schedule | read | Get one schedule Fetch a single schedule with its cron expression, timezone and active state. Trigger.dev: GET /api/v1/schedules/{scheduleId}. |
trigger_list_queues | read | 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 | read | Get one queue Fetch a single queue's concurrency limit, running count and queued count. Trigger.dev: GET /api/v1/queues/{queue}. |
trigger_get_current_deployment | read | Get 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. |
trigger_list_env_vars | read | 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}. |
trigger_list_waitpoint_tokens | read | 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 | read | List bulk actions List bulk replay and cancel operations and their progress. Trigger.dev: GET /api/v1/bulk-actions. |
trigger_cancel_run | write | Cancel 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. |
trigger_replay_run | write | Replay 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. |
trigger_reschedule_run | write | Reschedule 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. |
trigger_add_run_tags | write | Add 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. |
trigger_activate_schedule | write | Activate a schedule Resume a paused schedule so it fires again. Trigger.dev: POST /api/v1/schedules/{scheduleId}/activate. |
trigger_deactivate_schedule | write | Deactivate 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. |
trigger_pause_queue | write | Pause 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. |
trigger_dev_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
trigger_dev_request_feature | Request a missing feature Tell usefulapi that the user needs something the Trigger.dev tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
trigger_dev_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Trigger.dev tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
trigger_dev_cancel_subscription | Cancel the Pro subscription Cancel the caller's Trigger.dev Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run trigger_dev_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Trigger.dev server only. Subscribe with trigger_dev_upgrade (it returns a Stripe Checkout link). Cancel any time with trigger_dev_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running trigger_dev_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Trigger.dev. The server calls the Trigger.dev API with your own Trigger.dev access, so it sees only the data that your account can see.
The login page asks for your Trigger.dev secret key. See Before you connect for where to find it.
No. 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: the login page asks for your Trigger.dev secret key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Trigger.dev API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Trigger.dev.
Yes, if you approve it. 7 of the 22 Trigger.dev tools can create or change data. The other 15 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Trigger.dev server only. Run trigger_dev_usage_status to see how many calls you used.
Ask the AI to run trigger_dev_upgrade: it returns a Stripe Checkout link. To cancel, run trigger_dev_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with trigger_dev_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.