Download PDFMarkdown Version
ClaudeChatGPTPerplexityGeminiMicrosoft CopilotRaycastMeta AIGrokZ.aiQwenKimi
DeepSeekMistralCursorVS CodeWindsurfJetBrainsClineLovableVercel AI SDKLangChain

Use Trigger.dev with your AI.

Connect your account once and let the AI you already use work with it, without building another integration. Equip your AI agent with direct access to Trigger.dev. manage background jobs, monitor task runs, and inspect workflow executions without opening the dashboard

Included with plan

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

Complete set · 8 capabilities

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

    List projects

    List all projects

  2. 02

    List runs

    List task runs

  3. 03

    Get run

    Get run details

  4. 04

    Trigger task

    Trigger a background task

Capability set02 / 02

05-08

4 capabilities in this set.

Part of 8 available through Trigger.dev.

  1. 05

    Cancel run

    Cancel a running task

  2. 06

    List environments

    List deployment environments

  3. 07

    List schedules

    List cron schedules

  4. 08

    Replay run

    Replay a completed task

Observed, not estimated

855ms average. Fast in production.

Trigger.dev is checked daily against the live service.

Daily averagePeak 1086ms
Aug 20Today
Fastest day
689ms
Slowest day
1086ms
14-day trend
Slowing+13%

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

FAQ

Questions Trigger.dev owners ask.

  • 01

    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.

  • 02

    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.

  • 03

    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.

  • 04

    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