trigger-dev

Tools

22 tools: 14 read-only, 0 change data, 8 high risk (delete, pay, send or run code).

No tool name points to sending messages.

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 3,103 tokens of tool definitions and a 598 ms handshake.

• high risktrigger_get_runFetch a single run's outcome - its status, output, error and attempts. Trigger.dev: GET /api/v1/runs/{runId}/result.
• high risktrigger_cancel_runCancel an in-flight run. Note this is the one endpoint on API v2, not v1. Trigger.dev: POST /api/v2/runs/{runId}/cancel.
• high risktrigger_replay_runRe-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.
• high risktrigger_reschedule_runChange when a delayed run will execute. Only applies to runs that have not started. Trigger.dev: POST /api/v1/runs/{runId}/reschedule.
• high risktrigger_add_run_tagsAttach tags to a run so you can filter for it later. Additive and safe. Trigger.dev: POST /api/v1/runs/{runId}/tags.
• high risktrigger_activate_scheduleResume a paused schedule so it fires again. Trigger.dev: POST /api/v1/schedules/{scheduleId}/activate.
• high risktrigger_deactivate_schedulePause a schedule so it stops firing. The usual first move when a scheduled task is misbehaving. Trigger.dev: POST /api/v1/schedules/{scheduleId}/deactivate.
• high risktrigger_pause_queuePause 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.
• read-onlytrigger_list_runsList 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.
• read-onlytrigger_get_run_traceFetch 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.
• read-onlytrigger_get_run_spanFetch a single span from a run's trace, with its own logs and attributes. Trigger.dev: GET /api/v1/runs/{runId}/spans/{spanId}.
• read-onlytrigger_list_run_eventsList the lifecycle events of one run - queued, dequeued, started, retried, completed. Trigger.dev: GET /api/v1/runs/{runId}/events.
• read-onlytrigger_get_run_metadataFetch the mutable metadata a run has written about itself - progress, checkpoints and custom state. Trigger.dev: GET /api/v1/runs/{runId}/metadata.
• read-onlytrigger_get_batch_resultsFetch the outcome of every run in a batch. Trigger.dev: GET /api/v1/batches/{batchId}/results.
• read-onlytrigger_list_schedulesList the cron schedules configured for tasks, with their next run times. Trigger.dev: GET /api/v1/schedules.
• read-onlytrigger_get_scheduleFetch a single schedule with its cron expression, timezone and active state. Trigger.dev: GET /api/v1/schedules/{scheduleId}.
• read-onlytrigger_list_queuesList task queues with their concurrency limits and current depth - where you look when work is backing up. Trigger.dev: GET /api/v1/queues.
• read-onlytrigger_get_queueFetch a single queue's concurrency limit, running count and queued count. Trigger.dev: GET /api/v1/queues/{queue}.
• read-onlytrigger_get_current_deploymentFetch the deployment currently serving the key's environment - its version, git ref and status. Trigger.dev: GET /api/v1/deployments/current.
• read-onlytrigger_list_env_varsList 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}.
• read-onlytrigger_list_waitpoint_tokensList outstanding waitpoint tokens - runs paused waiting for an external signal. Trigger.dev: GET /api/v1/waitpoints/tokens.
• read-onlytrigger_list_bulk_actionsList bulk replay and cancel operations and their progress. Trigger.dev: GET /api/v1/bulk-actions.

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Status

Newest check: answered with tools, from the daily check, 2026-10-04, 598 ms.

From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-052026-10-04

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in Bookings and appointments, ranked by days answering.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/trigger-dev.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/trigger-dev.usefulapi.io/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=trigger-dev.usefulapi.io%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/trigger-dev.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/trigger-dev.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=trigger-dev.usefulapi.io%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.