About Trigger.dev MCP by usefulapi
Trigger.dev MCP by usefulapi is a hosted MCP server for developers working with Trigger.dev background jobs. It exposes run details and operational controls for investigating traces, schedules, queues and deployments without local installation.
Key features
- 01List runs and inspect run details
- 02View traces, spans, events and metadata
- 03Check batch results and schedules
- 04Inspect queues and current deployment
- 05Cancel, replay or reschedule runs
- 06Manage schedule and queue state
Use cases
- 01Trace a background run to investigate an issue
- 02Review run events and batch results
- 03Check schedules, queues or deployment state
- 04Cancel or replay a run during debugging
MCP support
It exposes Trigger.dev run, trace, schedule, queue and deployment data as MCP tools, along with write tools for run and operational controls. The hosted endpoint accepts Trigger.dev credentials through sign-in and stores them per user.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://trigger-dev.usefulapi.io/mcpclaude mcp add --transport http io-usefulapi-trigger-dev https://trigger-dev.usefulapi.io/mcp{"mcpServers":{"io-usefulapi-trigger-dev":{"type":"http","url":"https://trigger-dev.usefulapi.io/mcp"}}}Open in Cursor{"servers":{"io-usefulapi-trigger-dev":{"type":"http","url":"https://trigger-dev.usefulapi.io/mcp"}}}Open in VS Code{"mcpServers":{"io-usefulapi-trigger-dev":{"type":"http","url":"https://trigger-dev.usefulapi.io/mcp"}}}{"mcpServers":{"io-usefulapi-trigger-dev":{"serverUrl":"https://trigger-dev.usefulapi.io/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
22| Parameter | Type | Required | Description |
|---|---|---|---|
| to | string | No | Epoch milliseconds upper bound on creation time. |
| tag | array | No | Only runs carrying these tags. |
| from | string | No | Epoch milliseconds lower bound on creation time. |
| after | string | No | Cursor from the previous page's pagination. Omit for the first page. |
| batch | string | No | Only runs in this batch. |
| queue | array | No | Only runs on these queues. |
| isTest | boolean | No | Only test runs, or only real ones. |
| period | string | No | Relative window, e.g. "1h", "24h", "7d". |
| status | array | No | Only runs in these states, e.g. ["FAILED","CRASHED"]. Others include PENDING, EXECUTING, COMPLETED, CANCELED, TIMED_OUT. |
| machine | array | No | Only runs on these machine presets. |
| version | string | No | Only runs of this deployment version. |
| pageSize | integer | No | Page size, 1-100. |
| schedule | string | No | Only runs created by this schedule. |
| taskIdentifier | array | No | Only runs of these task ids. |
Details
From the project READMETrigger.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/mcpto 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
| 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 (unlimited*) |
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.
Pricing
| 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 [email protected].
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 [email protected].
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.