Skip to content
Vinkius

Trigger.dev Connector for AI agents.

8 live capabilities

Manage background job infrastructure and debug failed tasks in your production pipeline.

Live agent request Trigger.dev / Connector

Waiting for input…

AI Agent

Why people use Trigger.dev

Trigger.dev for Debugging Failed Background Jobs

This Connector lets you stay in your flow. You can just ask your agent to pull the logs for a specific failed run, see the error message, and check the retry history. It turns a five-minute dashboard hunt into a five-second chat response.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • Visual Studio Code
  • Windsurf

What Vinkius changes

You get a conversational way to manage and debug your background infrastructure without ever opening a dashboard.

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

One account · 5,900+ Connectors

  1. Real-world use case 01

    Debugging a failed production webhook

    A production webhook failed.

  2. Real-world use case 02

    Testing a fix for a data sync

    I need to test a fix for a data sync.

  3. Real-world use case 03

    Checking environment status

    Checking environment status.

Complete set · 8capabilities

The complete Trigger.dev capability set.

These are the exact actions your AI can choose when you ask it to work with Trigger.dev.

Capability set01 / 02

01—04

4 capabilities in this set.

Part of 8 available through Trigger.dev.

  1. 01 Capability

    List projects

    Get a list of all projects associated with your account.

  2. 02 Capability

    List runs

    See a list of all task runs including their current status and execution time.

  3. 03 Capability

    Get run

    Pull the full details of a specific run, including logs and retry history.

  4. 04 Capability

    Trigger task

    Start a new background task manually to test a specific workflow.

Capability set02 / 02

05—08

4 capabilities in this set.

Part of 8 available through Trigger.dev.

  1. 05 Capability

    Cancel run

    Stop a running task immediately if it's stuck or needs to be interrupted.

  2. 06 Capability

    Replay run

    Replay a completed task to test your fixes with the original data.

  3. 07 Capability

    List schedules

    View all cron schedules to see how your tasks are currently timed.

  4. 08 Capability

    List environments

    See all deployment environments like dev, staging, and production.

Set up in minutes

One URL. Then ask Trigger.dev to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Trigger.dev 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_E3D1PSFbED6190OhQ3gSMc4dXdMknoYFUrVm1Mgk/mcp
  1. Step 01

    Open Connectors

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

  2. Step 02

    Add the URL

    Choose Add custom connector, name it Trigger.dev, and paste the URL above.

  3. Step 03

    Turn it on in chat

    Select +, open Connectors, and enable Trigger.dev for the conversation.

Where the request belongs

Work Trigger.dev can move forward.

Built around the request

This is for the backend engineer who's tired of manual log hunting or the DevOps lead who needs to know exactly why a production queue is backing up at 3 AM.

01

Backend Developer

Debugging failed background tasks and verifying output payloads during a sprint.

02

DevOps Engineer

Monitoring job health across multiple environments and identifying bottlenecks in the pipeline.

03

Technical Lead

Getting a high-level overview of production job success rates during an incident.

Build the capability set

Add more capabilities.

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

Browse Connectors
Trigger.dev (Background Tasks & Jobs) logo
01 19 capabilities

Trigger.dev (Background Tasks & Jobs)

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

View Connector
Tray.io logo
02 6 capabilities

Tray.io

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

View Connector
Orkes Conductor logo
03 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.

View Connector
Lindy (Autonomous AI Employees) logo
04 10 capabilities

Lindy (Autonomous AI Employees)

Manage autonomous AI employees via Lindy. trigger task runs, monitor reasoning logs, and audit app integrations.

View Connector
Semaphore logo
05 36 capabilities

Semaphore

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

View Connector
Temporal logo
06 7 capabilities

Temporal

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

View Connector

Bring your own AI

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

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • VS Code
  • Windsurf
  • ZCode
  • Cline
  • Zed
  • Continue
  • Kiro
  • Roo Code
  • Zencoder
  • Goose
  • Void
  • Augment Code
  • Amp
  • Qodo
  • Tabnine
  • Pieces
  • Sourcegraph Cody
  • JetBrains
  • Warp
  • Amazon Q
  • Antigravity
  • BoltAI
  • Raycast
  • Jan
  • LM Studio
  • AnythingLLM
  • Open WebUI
  • Msty
  • Cherry Studio
  • LibreChat
  • TypingMind
  • Chorus
  • 5ire
  • n8n
  • LangChain
  • LlamaIndex
  • CrewAI
  • Vercel AI SDK

Before you connect

Questions about Trigger.dev.

The practical details behind the request, access and result.

Can I use Trigger.dev MCP to see why my background tasks are failing?

Yes. The Connector lets your agent pull specific error logs and retry histories for any failed run, making it easy to spot bugs in your background logic.

Does the Trigger.dev MCP work for production environments?

It does. You can use it to monitor production job health, check success rates, and inspect live runs across your entire deployment pipeline.

How does the Trigger.dev MCP help with debugging?

It allows your agent to retrieve the exact input payload and output logs for specific runs. You can see exactly what data caused a crash without manual searching.

Can I use Trigger.dev MCP to restart a job?

You can use it to replay a completed task. This is great for testing a code fix against the exact same data that caused the original failure.

Does Trigger.dev MCP let me see my different projects?

Yes, your agent can list all projects and environments associated with your Trigger.dev account, giving you a bird's-eye view of your infrastructure.

Can I stop a running job using the Trigger.dev MCP?

Yes, your agent can cancel a running task immediately if you notice it's stuck or behaving unexpectedly in your production queue.

How do I get my Trigger.dev API key?

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.

Can my AI agent tell me why a background job failed in production?

Yes. Ask your agent to list failed runs and it returns the task name, error message, stack trace, execution duration, and retry count for each failure. You can then drill into a specific run to see the exact input payload and which step failed. cutting your debugging time from minutes to seconds.

What if I'm on-call and need to check job health at 2 AM?

Just ask your AI agent 'Are there any failed jobs in production?' and get an instant triage report. number of failures, which tasks are affected, when they started failing, and whether retries resolved them. No need to open a browser, log in, or navigate dashboards in the middle of the night.

Does it support multiple environments like dev, staging, and production?

Yes. Each API key is scoped to a specific environment (dev or prod), just like in Trigger.dev itself. You can configure separate integrations for each environment, or switch between them by updating the API key. giving you full control over which environment your AI agent queries.

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