Trigger.dev (Background Tasks & Jobs)

Trigger.dev (Background Tasks & Jobs) MCP Connector for Claude

A+

Manage background tasks and jobs via Trigger.dev — trigger tasks, monitor runs, manage schedules, and configure environment variables directly from your AI agent.

19 tools Official Updated Jun 28, 2026 Official Vinkius Partner

Connect your Trigger.dev account to any AI agent to orchestrate complex background workflows and monitor job execution through natural language.

What you can do

  • Task Orchestration — Trigger individual tasks or batch up to 1,000 tasks in a single request using trigger_task and batch_trigger_tasks.
  • Run Monitoring — Retrieve detailed status, payloads, and outputs for specific runs with get_run, or list runs with advanced filtering using list_runs.
  • Lifecycle Management — Cancel in-progress runs, replay failed executions, and update run metadata for real-time progress tracking.
  • Scheduling — Create and manage imperative cron schedules to automate recurring tasks with create_schedule.
  • Environment Control — Manage environment variables and control queue concurrency or pause/resume operations directly via the API.

How it works

  1. Subscribe to this server
  2. Enter your Trigger.dev Secret Key
  3. Start managing your background jobs from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Backend Engineers — monitor and debug production jobs without leaving the terminal or IDE.
  • DevOps Teams — automate task triggers and manage environment configurations via chat.
  • Product Managers — check the status of critical data processing runs or batch operations.
background-jobstask-schedulingworkflow-automationserverlessmonitoring

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

batch_trigger_tasks

Trigger multiple tasks in a single request

cancel_run

Cancel an in-progress run

complete_waitpoint

Complete a waitpoint

create_batch

Create a batch (Phase 1)

create_env_var

Create an environment variable

create_schedule

Create an IMPERATIVE schedule (cron)

create_waitpoint_token

Create a waitpoint token

delete_env_var

Delete an environment variable

get_batch_results

Retrieve batch results

get_run

Retrieve a specific run

list_env_vars

List environment variables

list_runs

List runs in an environment

list_schedules

List schedules

override_queue_concurrency

Override queue concurrency

pause_resume_queue

Pause or resume a queue

replay_run

Replay a run

trigger_task

dev. Trigger a task by its identifier

update_env_var

Update an environment variable

update_run_metadata

Update run metadata

See how to talk to your AI agent using Trigger.dev (Background Tasks & Jobs).

Trigger the 'image-processing' task with payload { 'url': 'https://example.com/img.jpg' }.

Task triggered successfully. Run ID: run_abc123. Status: QUEUED. You can check its progress using get_run.

List the last 5 failed runs for the 'sync-data' task.

I've found 5 failed runs for 'sync-data'. The most recent failure (ID: run_xyz789) occurred at 10:30 AM with error: 'Connection Timeout'. Would you like to replay it?

Create a daily schedule for the 'cleanup-logs' task at midnight.

Schedule created for 'cleanup-logs' with cron '0 0 * * *'. Deduplication key: 'daily-cleanup-logs'. The task will now run automatically every day at midnight UTC.

Yes! You can use the `batch_trigger_tasks` tool to trigger up to 1,000 tasks in a single batch request, which is highly efficient for high-volume workflows.

Related Connectors