An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Triggerdev Background Tasks Jobs to your AI

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Run, monitor, and schedule complex workflows through your AI agent.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 19 capabilities

We ship only the actions that matter.

Capability set01 / 05

01-04

4 capabilities in this set.

Part of 19 available through Trigger.dev.

  1. 01

    Replay run

    Replays a specific failed or completed run to re-execute the logic.

  2. 02

    Batch trigger tasks

    Triggers a large group of tasks in a single request for high-volume operations.

  3. 03

    Create batch

    Starts the first phase of creating a batch operation.

  4. 04

    List env vars

    Retrieves a list of all environment variables in your current environment.

Capability set02 / 05

05-08

4 capabilities in this set.

Part of 19 available through Trigger.dev.

  1. 05

    Pause resume queue

    Pauses or resumes a specific queue to control task processing.

  2. 06

    Update env var

    Modifies the value of an existing environment variable.

  3. 07

    Update run metadata

    Updates the metadata associated with a specific run for better tracking.

  4. 08

    Cancel run

    Stops an in-progress run immediately.

Capability set03 / 05

09-12

4 capabilities in this set.

Part of 19 available through Trigger.dev.

  1. 09

    Complete waitpoint

    Signals that a waitpoint has been satisfied.

  2. 10

    Create env var

    Adds a new environment variable to your configuration.

  3. 11

    Create schedule

    Sets up a new imperative cron schedule for recurring tasks.

  4. 12

    Create waitpoint token

    Generates a token required to satisfy a waitpoint.

Capability set04 / 05

13-16

4 capabilities in this set.

Part of 19 available through Trigger.dev.

  1. 13

    Delete env var

    Removes an environment variable from your setup.

  2. 14

    Get batch results

    Fetches the outcomes and data from a completed batch.

  3. 15

    Get run

    Retrieves the full details, status, and payloads for a specific run.

  4. 16

    List runs

    Lists the runs within an environment, supporting advanced filtering.

Capability set05 / 05

17-19

3 capabilities in this set.

Part of 19 available through Trigger.dev.

  1. 17

    List schedules

    Shows all currently active cron schedules.

  2. 18

    Override queue concurrency

    Changes the concurrency limits for a specific queue.

  3. 19

    Trigger task

    Starts a single task using its unique identifier.

Real work

What teams actually run

01

Production Debugging

An engineer identifies a failed job and asks the agent to replay it after a fix is deployed.

02

Bulk Data Processing

A developer triggers a batch of 1,000 tasks to process user uploads simultaneously.

03

Automated Maintenance

A DevOps engineer sets up a midnight cron schedule to clean up database logs.

04

System Load Management

A team pauses a queue or overrides concurrency to handle unexpected traffic spikes.

Automate a task

Put Trigger.dev to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Trigger.dev works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Trigger.dev to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

1086ms average. Fast in production.

Trigger.dev is checked daily against the live service.

Daily averagePeak 1285ms
Oct 3Today
Fastest day
846ms
Slowest day
1285ms
14-day trend
Improving-9%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 19 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Trigger.dev, so you can see the experience inside your AI.

It does not authenticate your account with Trigger.dev. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Trigger.dev Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_DiUWSJJpaOcItA1IYDF4PWPoPmppnbeSDfcRQ8O3/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Trigger.dev capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "triggerdev-background-tasks-jobs-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_DiUWSJJpaOcItA1IYDF4PWPoPmppnbeSDfcRQ8O3/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Trigger.dev in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Trigger.dev owners hand off.

This MCP is built for technical teams who need to manage background workloads without switching contexts between their code and their monitoring capabilities.

  • 01

    Backend Engineers

    They use the agent to debug and monitor production jobs directly from their IDE.

  • 02

    DevOps Teams

    They automate task triggers and manage environment configurations via chat.

  • 03

    Product Managers

    They check the status of critical data processing runs or batch operations.

FAQ

Questions Trigger.dev owners ask.

  • 01

    How do I connect my Trigger.dev account?

    You subscribe to the MCP on Vinkius and enter your Trigger.dev Secret Key. Once connected, your AI client can immediately start interacting with your jobs.

  • 02

    Can I trigger multiple tasks at once?

    Yes, you can use the batch_trigger_tasks capability to trigger up to 1,000 tasks in a single request.

  • 03

    What happens if a background job fails?

    You can ask your AI agent to list recent runs, check the error details, and then use the replay_run capability to try the execution again.

  • 04

    Is it possible to automate tasks on a schedule?

    Yes, you can use the create_schedule capability to set up imperative cron schedules for any task.

  • 05

    Which AI clients are compatible with this MCP?

    This MCP works with any compatible client, including Claude, Cursor, Windsurf, and VS Code.

  • 06

    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.

  • 07

    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.

  • 08

    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.

Explore

More in Developer Tools

Suggestions

Connect Trigger.dev to Claude, Cursor, ChatGPT & more