Trigger.dev

Trigger.dev MCP Connector for Claude

A+

Equip your AI agent with direct access to Trigger.dev — manage background jobs, monitor task runs, and inspect workflow executions without opening the dashboard.

8 tools Official Updated Jun 28, 2026 Official Vinkius Partner

Connect Trigger.dev to your AI agent and manage your background job infrastructure conversationally.

What you can do

  • Job Monitoring — List active, completed, and failed task runs with execution times, statuses, and error details.
  • Project Overview — Query projects, environments, and their associated job definitions.
  • Run Inspection — Drill into individual runs to view payloads, outputs, logs, and retry history.
  • Environment Management — Switch between dev, staging, and production environments to inspect runs across your deployment pipeline.

How it works

  1. Subscribe to the Trigger.dev integration on the marketplace.
  2. Generate a Secret API Key from your Trigger.dev dashboard (Project → API Keys section — keys start with tr_dev_ or tr_prod_).
  3. Ask your AI agent to list job runs, check failures, or inspect task outputs.

Who is this for?

  • Backend Developers — Monitor background job health, debug failed runs, and verify task outputs without leaving your code editor.
  • DevOps Engineers — Track job execution across environments and identify bottlenecks in your processing pipeline.
  • Technical Leads — Get instant visibility into production job queues during incident response without switching to the Trigger.dev dashboard.
background-jobsworkflow-automationevent-driventask-schedulingobservabilitytypescript

8 tools expose this connector's capabilities to your AI agent.

replay_run

Replay a completed task

list_schedules

List cron schedules

list_environments

List deployment environments

list_projects

List all projects

list_runs

List task runs

get_run

Get run details

trigger_task

Trigger a background task

cancel_run

Cancel a running task

See how to talk to your AI agent using Trigger.dev.

Are there any failed background jobs in production?

I found 2 failed runs in the last 24 hours: 'process-webhook' failed with a timeout error (3 retries exhausted) and 'sync-inventory' failed due to a database connection error. Both occurred between 3:00-3:15 AM UTC.

Show me the details of the last 'process-webhook' run.

Run ID: run_abc123. Status: FAILED. Duration: 30.2s (timeout at 30s). Error: 'Request timeout after 30000ms at postWebhook step'. Input payload: {event: 'order.created', id: 'ord_xyz'}. Retries: 3/3 exhausted.

How many jobs ran successfully today?

Today's stats: 1,247 total runs — 1,238 successful (99.3%), 7 failed (0.6%), and 2 currently running. Average execution time: 2.4 seconds. Most active task: 'process-order' with 892 runs.

Log in to your Trigger.dev dashboard at **cloud.trigger.dev**. Open your project, then find the **API Keys** section in the project settings. Copy your **Secret API Key** (it starts with `tr_dev_` for development or `tr_prod_` for production). Paste it into the configuration field below. For Personal Access Tokens (used for admin operations), go to **Profile → Personal Access Tokens** tab instead.

Related Connectors