Debug background jobs — runs, traces, spans, schedules, queues and deployments. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
Turn on the Trigger.dev connector, then ask in plain words. The AI picks the tools.
For developers who run background tasks on Trigger.dev.
The AI lists runs filtered by status, task, tag, queue or time window, then opens a run to read its output, error and attempts.
The AI reads the full trace of a run with every span and its timing, one span with its logs, and the lifecycle events (queued, started, retried, completed).
The AI lists queues with their concurrency limit, running count and queued count, so you see where work piles up.
The AI lists schedules with cron expression, timezone, active state and next run times.
The AI deactivates a schedule that misbehaves, activates it again later, or pauses a queue so its runs stop being dequeued.
Changes dataThe AI cancels a run in flight, replays a past run with the same payload, changes the time of a delayed run, or adds tags to a run.
Changes dataThe login page asks for your Trigger.dev secret key.
Copy it from your Trigger.dev project's API keys page. Your token is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Team and Enterprise: an Owner adds the connector for the organization first.
No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"trigger-dev": {
"url": "https://trigger-dev.usefulapi.io/mcp"
}
}
} Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"trigger-dev": {
"type": "http",
"url": "https://trigger-dev.usefulapi.io/mcp"
}
}
} Run these commands. The second one opens the login page:
Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.
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: the login page asks for your Trigger.dev secret key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Pro | $9/mo · $90/yr | 10,000 tool calls / month |
| Pro+ | $39/mo · $390/yr | 100,000 tool calls / month |
Each paid plan covers this Trigger.dev server only. Ask your AI to run trigger_dev_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with trigger_dev_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with trigger_dev_upgrade before then undoes the cancel. Or write to [email protected].
trigger_list_runstrigger_get_runtrigger_get_run_tracetrigger_get_run_spantrigger_list_run_eventstrigger_get_run_metadatatrigger_get_batch_resultstrigger_list_schedulestrigger_get_scheduletrigger_list_queuestrigger_get_queuetrigger_get_current_deploymenttrigger_list_env_varstrigger_list_waitpoint_tokenstrigger_list_bulk_actionstrigger_cancel_runtrigger_replay_runtrigger_reschedule_runtrigger_add_run_tagstrigger_activate_scheduletrigger_deactivate_scheduletrigger_pause_queuetrigger_dev_usage_statustrigger_dev_request_featuretrigger_dev_upgradetrigger_dev_cancel_subscriptionFind failed runs and read their errors. Find where a run spent its time or broke. Check queues that are backing up. Review cron schedules and their next runs. Pause or resume a schedule or a queue. Cancel, replay, reschedule or tag a run. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Trigger.dev. The server calls the Trigger.dev API with your own Trigger.dev access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Trigger.dev secret key. See Before you connect for where to find it.
No. 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: the login page asks for your Trigger.dev secret key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Trigger.dev API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Trigger.dev.
Yes, if you approve it. 7 of the 22 Trigger.dev tools can create or change data. The other 15 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Trigger.dev server only. Cancel any time: your paid plan then runs to the end of the paid period. Run trigger_dev_usage_status to see how many calls you used.
Ask the AI to run trigger_dev_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run trigger_dev_cancel_subscription. Your paid plan continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with trigger_dev_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.