Trigger.dev (Background Tasks & Jobs) Connector for AI agents.

19 live capabilities

Manage background jobs and cron schedules for your production workflows.

Live agent request Trigger.dev (Background Tasks & Jobs) / Connector

Waiting for input…

AI Agent

Why people use Trigger.dev (Background Tasks & Jobs)

Trigger.dev for Debugging Production Jobs

This Connector puts the Trigger.dev control plane directly into your AI client. You can just ask your agent to list the last five failed runs or update a production secret. You get the same level of control without the tab-switching, making it much faster to debug and manage your infrastructure.

What Vinkius changes

You get a direct command line for your background jobs inside your AI chat.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 5,900+ Connectors

Real-world use case 01

Fixing a stuck migration

A developer asks the agent to cancel_run on a hung database update and then replay_run once the lock is cleared.
Real-world use case 02

Batching user invites

A PM asks the agent to batch_trigger_tasks to send 500 welcome emails to new signups in one request.
Real-world use case 03

Emergency queue pause

An engineer sees a spike in traffic and tells the agent to pause_resume_queue to protect the backend.

Complete set · 19capabilities

The complete Trigger.dev (Background Tasks & Jobs) capability set.

These are the exact actions your AI can choose when you ask it to work with Trigger.dev (Background Tasks & Jobs).

Capability set01 / 05

01—04

4 capabilities in this set.

Part of 19 available through Trigger.dev (Background Tasks & Jobs).

01 Capability
Create env var
Create_env_var adds a new environment variable to your Trigger.dev project. This lets you manage secrets and configs without a web UI.
02 Capability
Replay run
Replay_run re-runs a job that failed previously. Use this to fix errors without having to manually trigger the task again.
03 Capability
Batch trigger tasks
Batch_trigger_tasks lets you fire off a large group of tasks in one go. This helps when you need to update many records at once without hitting rate limits.
04 Capability
Cancel run
Cancel_run stops a job that's currently running. Use this if a process is stuck or no longer needed.

Capability set02 / 05

05—08

4 capabilities in this set.

Part of 19 available through Trigger.dev (Background Tasks & Jobs).

05 Capability
Complete waitpoint
Complete_waitpoint manually finishes a task that's waiting for an external signal. This is great for multi-step workflows that need human input.
06 Capability
Create batch
Create_batch starts a new group of tasks to be processed together. It helps organize large-scale data operations into manageable phases.
07 Capability
Create schedule
Create_schedule sets up a recurring cron job for your tasks. Use this to automate daily or hourly maintenance jobs.
08 Capability
Create waitpoint token
Create_waitpoint_token generates a unique token for a task that needs to pause. It allows you to resume a job whenever you're ready.

Capability set03 / 05

09—12

4 capabilities in this set.

Part of 19 available through Trigger.dev (Background Tasks & Jobs).

09 Capability
Delete env var
Delete_env_var removes an environment variable from your project. Use this to clean up old configuration keys.
10 Capability
Get batch results
Get_batch_results shows the final output of a completed batch of tasks. This is perfect for verifying large data migrations.
11 Capability
Get run
Get_run looks up the details of a specific job execution. Use it to see exactly what went wrong during a failure.
12 Capability
List env vars
List_env_vars shows all the environment variables currently set in your project. This helps you quickly check your configuration.

Capability set04 / 05

13—16

4 capabilities in this set.

Part of 19 available through Trigger.dev (Background Tasks & Jobs).

13 Capability
List runs
List_runs shows a history of all your recent task executions. Use it to monitor the health of your background workers.
14 Capability
List schedules
List_schedules shows all the recurring jobs you've created. This helps you keep track of your automated workflows.
15 Capability
Override queue concurrency
Override_queue_concurrency changes how many jobs run at once in a specific queue. Use this to prevent overloading your database.
16 Capability
Pause resume queue
Pause_resume_queue temporarily stops or starts a queue of jobs. This is useful for maintenance windows or handling traffic spikes.

Capability set05 / 05

17—19

3 capabilities in this set.

Part of 19 available through Trigger.dev (Background Tasks & Jobs).

17 Capability
Trigger task
Trigger_task starts a single background job by its name. This is the most common way to kick off a new workflow.
18 Capability
Update env var
Update_env_var changes the value of an existing environment variable. Use this to flip feature flags or update API keys.
19 Capability
Update run metadata
Update_run_metadata adds extra info to a running job for better tracking. This helps you see custom progress markers in your dashboard.

Set up in minutes

One URL. Then ask Trigger.dev (Background Tasks & Jobs) to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Trigger.dev (Background Tasks & Jobs) from the conversation.

Choose your client

Live preview

Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP

https://edge.vinkius.com/vk_preview_DiUWSJJpaOcItA1IYDF4PWPoPmppnbeSDfcRQ8O3/mcp

Step 01

Open Connectors

In Claude Web or Claude Desktop, open Settings and choose Connectors.
Step 02

Add the URL

Choose Add custom connector, name it Trigger.dev (Background Tasks & Jobs), and paste the URL above.
Step 03

Turn it on in chat

Select +, open Connectors, and enable Trigger.dev (Background Tasks & Jobs) for the conversation.

ChatGPT · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP

https://edge.vinkius.com/vk_preview_DiUWSJJpaOcItA1IYDF4PWPoPmppnbeSDfcRQ8O3/mcp

Step 01

Open MCP settings

On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
Step 02

Add the URL

Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the Trigger.dev (Background Tasks & Jobs) URL.
Step 03

Save and start

Save the connection and enable Trigger.dev (Background Tasks & Jobs) in your conversation. Desktop may ask you to restart once.

Cursor · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "triggerdev-background-tasks-jobs": {
      "url": "https://edge.vinkius.com/vk_preview_DiUWSJJpaOcItA1IYDF4PWPoPmppnbeSDfcRQ8O3/mcp"
    }
  }
}

Step 01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
Step 02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens
Step 03

Save the file

Cursor will automatically detect the new Connector
Step 04

Start using Trigger.dev (Background Tasks & Jobs)

Open Agent mode in chat and ask: "Using Trigger.dev (Background Tasks & Jobs), help me...". 19 tools available

VS Code Copilot · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "triggerdev-background-tasks-jobs": {
      "url": "https://edge.vinkius.com/vk_preview_DiUWSJJpaOcItA1IYDF4PWPoPmppnbeSDfcRQ8O3/mcp"
    }
  }
}

Step 01

Create MCP config

Create a .vscode/mcp.json file in your project root
Step 02

Add the server config

Paste the JSON configuration above
Step 03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown
Step 04

Start using Trigger.dev (Background Tasks & Jobs)

Ask Copilot: "Using Trigger.dev (Background Tasks & Jobs), help me...". 19 tools available

Windsurf · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "triggerdev-background-tasks-jobs": {
      "url": "https://edge.vinkius.com/vk_preview_DiUWSJJpaOcItA1IYDF4PWPoPmppnbeSDfcRQ8O3/mcp"
    }
  }
}

Step 01

Open MCP Settings

Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
Step 02

Add the server

Paste the JSON configuration above into mcp_config.json
Step 03

Save and reload

Windsurf will detect the new server automatically
Step 04

Start using Trigger.dev (Background Tasks & Jobs)

Open Cascade and ask: "Using Trigger.dev (Background Tasks & Jobs), help me...". 19 tools available

Cline · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "triggerdev-background-tasks-jobs": {
      "url": "https://edge.vinkius.com/vk_preview_DiUWSJJpaOcItA1IYDF4PWPoPmppnbeSDfcRQ8O3/mcp"
    }
  }
}

Step 01

Open Cline MCP Settings

Click the Connectors icon in the Cline sidebar panel
Step 02

Add remote server

Click "Add Connector" and paste the configuration above
Step 03

Enable the server

Toggle the server switch to ON
Step 04

Start using Trigger.dev (Background Tasks & Jobs)

Ask Cline: "Using Trigger.dev (Background Tasks & Jobs), help me...". 19 tools available

Claude Code · Terminal command

Official guide ↗

Advanced setup

claude mcp add triggerdev-background-tasks-jobs --transport http "https://edge.vinkius.com/vk_preview_DiUWSJJpaOcItA1IYDF4PWPoPmppnbeSDfcRQ8O3/mcp"

Step 01

Install Claude Code

Run npm install -g @anthropic-ai/claude-code if not already installed
Step 02

Add the Connector

Run the command above in your terminal
Step 03

Verify the connection

Run claude mcp to list connected servers, or type /mcp inside a session
Step 04

Start using Trigger.dev (Background Tasks & Jobs)

Ask Claude: "Using Trigger.dev (Background Tasks & Jobs), show me...". 19 tools are ready

Where the request belongs

Work Trigger.dev can move forward.

Built around the request

The backend engineer who's tired of clicking through dashboards at 2am to find out why a production job failed. It's for developers who need to manage infrastructure without the overhead of multiple browser tabs.

01

Backend Engineer

Debugging production jobs without leaving the IDE.

02

DevOps Engineer

Managing concurrency and environment variables via chat.

03

Product Manager

Checking the status of critical data processing runs without asking developers for updates.

Build the capability set

Each Connector adds new actions and data without changing how you work.

Browse Connectors

01 8 capabilities

Trigger.dev

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

02 17 capabilities

Zeplo (Queue & Background Job API)

Schedule, queue, and manage background jobs and webhooks via Zeplo directly from your AI agent.

03 36 capabilities

Semaphore

Automate CI/CD workflows, manage pipelines, and monitor build jobs directly from your AI agent.

04 7 capabilities

Temporal

Monitor and manage distributed workflows in Temporal Cloud natively via your AI agent.

05 6 capabilities

Tray.io

Equip your AI agent to orchestrate automations, track active workflows, and monitor data execution flows across Tray.io natively.

06 6 capabilities

Orkes Conductor

Orchestrate microservice workflows via Orkes Conductor. list definitions, track running executions, search workflow history, and inspect task states from any AI agent.

Bring your own AI

Change the model, client or framework. Keep Trigger.dev connected.

Before you connect

Questions about Trigger.dev.

The practical details behind the request, access and result.

Can the Trigger.dev MCP help me see why a job failed?

Yes, it lets you list all recent runs and get the specific error details for any failed job without leaving your chat.

How do I use this to manage my cron jobs?

You can describe the schedule you want in plain English, and the Connector will create the recurring task for you using the create_schedule capability.

Can I use this to update my production secrets?

Yes, you can ask your agent to update or list environment variables directly, which is much safer than manually editing config files.

Is it possible to restart a job that stopped halfway?

You can use the replay_run capability to re-execute a failed job, which saves you from having to manually trigger the whole workflow again.

Can I use this to stop a queue from overloading my database?

Definitely. You can tell your agent to pause a queue or override the concurrency limits to keep your database stable during high traffic.

Does this Connector work for batching multiple tasks?

Yes, it supports triggering up to 1,000 tasks in a single request, which is perfect for large data migrations or bulk updates.

Can I trigger multiple background tasks at once?

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

How do I check the output or error of a specific job run?

Use the get_run capability with the specific Run ID. It will return the full status, payload, output, and any attempt details or error logs associated with that run.

Can I schedule a task to run automatically using a cron expression?

Absolutely. Use the create_schedule capability to define a task identifier, a cron expression (e.g., '0 0 * * *'), and a deduplication key to automate recurring background jobs.

One connection away

Give your agent a direct line to Trigger.dev.

Connect Trigger.dev once. Keep it beside 5,900+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available