Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Debug background jobs — runs, traces, spans, schedules, queues and deployments.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
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:
https://trigger-dev.usefulapi.io/mcpRun this in your terminal
claude mcp add --transport http trigger-dev https://trigger-dev.usefulapi.io/mcpPaste 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.
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:
https://trigger-dev.usefulapi.io/mcpMenu 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.
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_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.
trigger_get_runFetch a single run's outcome — its status, output, error and attempts. Trigger.dev: GET /api/v1/runs/{runId}/result.
trigger_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.
trigger_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}.
trigger_list_run_eventsList the lifecycle events of one run — queued, dequeued, started, retried, completed. Trigger.dev: GET /api/v1/runs/{runId}/events.
trigger_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.
trigger_get_batch_resultsFetch the outcome of every run in a batch. Trigger.dev: GET /api/v1/batches/{batchId}/results.
trigger_list_schedulesList the cron schedules configured for tasks, with their next run times. Trigger.dev: GET /api/v1/schedules.
trigger_get_scheduleFetch a single schedule with its cron expression, timezone and active state. Trigger.dev: GET /api/v1/schedules/{scheduleId}.
trigger_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.
trigger_get_queueFetch a single queue's concurrency limit, running count and queued count. Trigger.dev: GET /api/v1/queues/{queue}.
trigger_get_current_deploymentFetch the deployment currently serving the key's environment — its version, git ref and status. Trigger.dev: GET /api/v1/deployments/current.
trigger_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}.
trigger_list_waitpoint_tokensList outstanding waitpoint tokens — runs paused waiting for an external signal. Trigger.dev: GET /api/v1/waitpoints/tokens.
trigger_list_bulk_actionsList bulk replay and cancel operations and their progress. Trigger.dev: GET /api/v1/bulk-actions.
trigger_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.
trigger_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.
trigger_reschedule_runChange 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_tagsAttach tags to a run so you can filter for it later. Additive and safe. Trigger.dev: POST /api/v1/runs/{runId}/tags.
trigger_activate_scheduleResume a paused schedule so it fires again. Trigger.dev: POST /api/v1/schedules/{scheduleId}/activate.
trigger_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.
trigger_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.
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 7, 2026
The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 12 ms (HTTP 200)
No sign-in needed
Read 22 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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.
The GitHub repo last changed –, and the latest version (1.36.2) reached the registry today.
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.
In the same category: Spec Driven Development, Remote Desktop Commander, Detailing Manager
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
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Connect your auto detailing studio's tasks, cars, clients and revenue to Claude or ChatGPT.
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.
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
https://trigger-dev.usefulapi.io/mcp.claude mcp add --transport http trigger-dev https://trigger-dev.usefulapi.io/mcp, then run /mcp to log in.{
"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.
| Tool | Type | What it does |
|---|---|---|
trigger_list_runs | read | List runs |
trigger_get_run | read | Get one run |
trigger_get_run_trace | read | Get a run's trace |
trigger_get_run_span | read | Get one span of a run |
trigger_list_run_events | read | List a run's events |
trigger_get_run_metadata | read | Get a run's metadata |
trigger_get_batch_results | read | Get a batch's results |
trigger_list_schedules | read | List schedules |
trigger_get_schedule | read | Get one schedule |
trigger_list_queues | read | List queues |
trigger_get_queue | read | Get one queue |
trigger_get_current_deployment | read | Get the current deployment |
trigger_list_env_vars | read | List environment variables |
trigger_list_waitpoint_tokens | read | List waitpoint tokens |
trigger_list_bulk_actions | read | List bulk actions |
trigger_cancel_run | write | Cancel a run |
trigger_replay_run | write | Replay a run |
trigger_reschedule_run | write | Reschedule a delayed run |
trigger_add_run_tags | write | Add tags to a run |
trigger_activate_schedule | write | Activate a schedule |
trigger_deactivate_schedule | write | Deactivate a schedule |
trigger_pause_queue | write | Pause or resume a queue |
trigger_dev_usage_status | meta | Usage status (free-tier meter) |
trigger_dev_request_feature | meta | Request a missing feature |
trigger_dev_upgrade | meta | Upgrade to Pro or Pro+ |
trigger_dev_cancel_subscription | meta | Cancel 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.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 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.
MIT