Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Trigger.dev MCP by usefulapi

by m190version 1.35.3i★ –iRuns in the cloud
Registry nameio.usefulapi/trigger-dev

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Install

Pick the AI app you use, then copy the settings.

Before you install

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://trigger-dev.usefulapi.io/mcp

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://trigger-dev.usefulapi.io/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

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

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • ✓ Pass

    Endpoint responds

    Responded in 12 ms (HTTP 200)

  • – Not applicable

    Sign-in with OAuth

    No sign-in needed

  • ✓ Pass

    No hidden instructions in tool descriptions

    Read 22 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

  • More stars than 0% of the other 32380 servers in this category
  • Published to the registry more recently than 97% of the other 32380 servers in this category
  • Basic checks equal to or better than 100% of the other 32380 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Trigger.dev MCP by usefulapi safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.35.3) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Dechonet MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

Dechonet MCP

by node-man

30 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.

Computer or cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Trigger.dev MCP by usefulapi

Debug background jobs — runs, traces, spans, schedules, queues and deployments. Hosted, no local install.

Live endpoint: https://trigger-dev.usefulapi.io/mcp · Homepage: https://usefulapi.io

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://trigger-dev.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http trigger-dev https://trigger-dev.usefulapi.io/mcp, then run /mcp to log in.
  • VS Code: Add to VS Code.
  • Cursor and other clients: add the URL as a remote MCP server:
{

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

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, and the login page asks for your Trigger.dev credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/trigger-dev/

On first connect you'll paste your Trigger.dev credentials. They are validated, stored per-user, and scoped to you — no keys in config files.

Tools

ToolTypeWhat it does
trigger_list_runsreadList runs
trigger_get_runreadGet one run
trigger_get_run_tracereadGet a run's trace
trigger_get_run_spanreadGet one span of a run
trigger_list_run_eventsreadList a run's events
trigger_get_run_metadatareadGet a run's metadata
trigger_get_batch_resultsreadGet a batch's results
trigger_list_schedulesreadList schedules
trigger_get_schedulereadGet one schedule
trigger_list_queuesreadList queues
trigger_get_queuereadGet one queue
trigger_get_current_deploymentreadGet the current deployment
trigger_list_env_varsreadList environment variables
trigger_list_waitpoint_tokensreadList waitpoint tokens
trigger_list_bulk_actionsreadList bulk actions
trigger_cancel_runwriteCancel a run
trigger_replay_runwriteReplay a run
trigger_reschedule_runwriteReschedule a delayed run
trigger_add_run_tagswriteAdd tags to a run
trigger_activate_schedulewriteActivate a schedule
trigger_deactivate_schedulewriteDeactivate a schedule
trigger_pause_queuewritePause or resume a queue
trigger_dev_usage_statusmetaUsage status (free-tier meter)
trigger_dev_request_featuremetaRequest a missing feature
trigger_dev_upgrademetaUpgrade to Pro or Pro+
trigger_dev_cancel_subscriptionmetaCancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Pro$9/mo or $90/yr (2 months free)Unlimited*

\*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to support@usefulapi.io.

Pro covers this 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 support@usefulapi.io.

License

MIT

Ask PopNx