Trigger.dev MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://trigger-dev.usefulapi.io/mcp

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

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

{
  "servers": {
    "trigger-dev": {
      "type": "http",
      "url": "https://trigger-dev.usefulapi.io/mcp"
    }
  }
}

https://trigger-dev.usefulapi.io/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• 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.

• 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.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 12 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 22 个工具描述，未发现针对 AI 的隐藏指令

与“其他”中的其他服务器比较i

• 星标数多于此分类中其他 32380 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 32380 个服务器的 97% 更新
• 基础检查结果等于或优于此分类中其他 32380 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{