Trigger.dev MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Trigger.dev MCP by usefulapi is answering right now. Last checked moments ago. It exposes 22 tools. Last commit 10 Oct 2026.

Debug background jobs — runs, traces, spans, schedules, queues and deployments.

Uptime history 13 days of history

13 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

110 ms

Response time

average over 24h

Stars

last commit 10 Oct 2026

What changed 7

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 September 2026. No other catalogue keeps this.

9 Oct a tool changed version4 times that day

7 Oct a tool changed version

30 Sep a tool changed version2 times that day

and 4 more, back to 30 September 2026

Nothing serious here today

Today is the operative word: we check Trigger.dev MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add trigger-dev --transport http https://trigger-dev.usefulapi.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "trigger-dev": {
      "url": "https://trigger-dev.usefulapi.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.trigger-dev]
url = "https://trigger-dev.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "trigger-dev": {
      "url": "https://trigger-dev.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "trigger-dev": {
      "url": "https://trigger-dev.usefulapi.io/mcp"
    }
  }
}

Available tools 22

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

trigger

trigger_activate_schedule

Resume a paused schedule so it fires again. Trigger.dev: POST /api/v1/schedules/{scheduleId}/activate.

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_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_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_get_batch_results

Fetch the outcome of every run in a batch. Trigger.dev: GET /api/v1/batches/{batchId}/results.

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.

trigger_get_queue

Fetch a single queue's concurrency limit, running count and queued count. Trigger.dev: GET /api/v1/queues/{queue}.

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_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_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_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_schedule

Fetch a single schedule with its cron expression, timezone and active state. Trigger.dev: GET /api/v1/schedules/{scheduleId}.

trigger_list_bulk_actions

List bulk replay and cancel operations and their progress. Trigger.dev: GET /api/v1/bulk-actions.

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_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_list_run_events

List the lifecycle events of one run — queued, dequeued, started, retried, completed. Trigger.dev: GET /api/v1/runs/{runId}/events.

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_list_schedules

List the cron schedules configured for tasks, with their next run times. Trigger.dev: GET /api/v1/schedules.

trigger_list_waitpoint_tokens

List outstanding waitpoint tokens — runs paused waiting for an external signal. Trigger.dev: GET /api/v1/waitpoints/tokens.

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.

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.

Endpoints

URL	Transport	State	Latency	Checked
https://trigger-dev.usefulapi.io/mcp	streamable-http	answering	81 ms	0 min ago

Alternatives to Trigger.dev MCP by usefulapi

same job, measured the same way

Fireworks AI MCP by usefulapi

by usefulapi

Inspect Fireworks AI models, deployments, datasets and fine-tuning jobs.

14 tools answering

Laravel Forge MCP by usefulapi

by usefulapi

Manage Laravel Forge servers, sites, and deployments from your AI assistant.

17 tools answering

Airbrake MCP by usefulapi

by usefulapi

Read Airbrake projects, error groups, notices, deploys and stats; mute or unmute error groups.

13 tools answering

Scalingo MCP by usefulapi

by usefulapi

Manage Scalingo PaaS apps, deployments, containers, logs and env vars from your AI assistant.

21 tools answering

Railway MCP

by railway

Develop, manage, and debug Railway projects, services, and deployments from within agents.

answering

CloudPepper

by cloudpepper

Manage CloudPepper servers, Odoo instances, backups, and deployments over MCP.

answering

Prefect MCP Server

by prefecthq

MCP server for Prefect. Monitor and debug workflows, deployments, and automations.

1 284 installs/wk local only

Civo MCP by usefulapi

by usefulapi

List Civo instances, Kubernetes clusters, networks and DNS; reboot instances, add rules.

22 tools answering

Trigger.dev MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Trigger.dev MCP by usefulapi do?

It exposes 22 tools, read directly from the server on our last check. Among them: trigger_activate_schedule, trigger_add_run_tags, trigger_cancel_run, trigger_deactivate_schedule, trigger_get_batch_results, trigger_get_current_deployment and 16 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Trigger.dev MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 110 ms. The bar chart above shows every period we have measured.

How do I connect Trigger.dev MCP by usefulapi?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Trigger.dev MCP by usefulapi need an API key?

No. Trigger.dev MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 22 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Trigger.dev MCP by usefulapi?

It answers our handshake in 110 ms on average, which is faster than 81% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Trigger.dev MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.