An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Trigger.dev to ChatGPT, Claude and Gemini

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. Manage your entire job infrastructure through your AI client.

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 · 8 capabilities

We ship only the actions that matter.

Capability set01 / 02

01-04

4 capabilities in this set.

Part of 8 available through Trigger.dev.

  1. 01

    List projects

    This capability lists all your Trigger.dev projects.

  2. 02

    List runs

    Use this to get a list of all task runs.

  3. 03

    Get run

    This capability retrieves the specific details for a single run.

  4. 04

    Trigger task

    Use this to start a new background task immediately.

Capability set02 / 02

05-08

4 capabilities in this set.

Part of 8 available through Trigger.dev.

  1. 05

    Cancel run

    This capability stops a task that is currently running.

  2. 06

    List environments

    This capability shows all your deployment environments like dev or production.

  3. 07

    List schedules

    Use this to view your configured cron schedules.

  4. 08

    Replay run

    This capability re-runs a task that has already completed.

Real work

What teams actually run

01

Rapid Debugging

Ask your agent to find the exact error message and input payload for a failed task.

02

Production Monitoring

Check the success rate and volume of background jobs in your production environment.

03

Task Retries

Instruct your agent to replay a specific completed task to test fixes.

04

Environment Auditing

Compare job performance and schedules across dev, staging, and production.

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

938ms average. Fast in production.

Trigger.dev is checked daily against the live service.

Daily averagePeak 1312ms
Oct 3Today
Fastest day
736ms
Slowest day
1312ms
14-day trend
Slowing+11%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 8 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_E3D1PSFbED6190OhQ3gSMc4dXdMknoYFUrVm1Mgk/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-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_E3D1PSFbED6190OhQ3gSMc4dXdMknoYFUrVm1Mgk/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 engineers who manage event-driven architectures and need fast visibility into background processes.

  • 01

    Backend Developers

    They use the agent to debug failed runs and verify task outputs without leaving their editor.

  • 02

    DevOps Engineers

    They track job execution across environments to find bottlenecks in processing pipelines.

  • 03

    Technical Leads

    They get instant visibility into production job queues during incident response.

FAQ

Questions Trigger.dev owners ask.

  • 01

    How do I connect this MCP to my Trigger.dev account?

    You need to generate a Secret API Key in your Trigger.dev dashboard under the Project API Keys section. Once you have that, you can connect the MCP through Vinkius.

  • 02

    Can I trigger tasks using my AI agent?

    Yes, the trigger_task capability allows your agent to start background tasks directly through your conversation.

  • 03

    Which AI clients can use this MCP?

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

  • 04

    Can I see error logs for failed jobs?

    Yes, you can use the agent to inspect specific runs to view error details, logs, and retry history.

  • 05

    Is it possible to manage different environments?

    Yes, the MCP includes capabilities to list and switch between your dev, staging, and production environments.

  • 06

    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.

  • 07

    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.

  • 08

    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.

  • 09

    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.

Explore

More in Ship It

Suggestions

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