Integrate Trigger.dev with Claude, Cursor, Chatbots & AI Agents MCP Server

Q: 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 trdev for development or trprod 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.

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

GDPR Free for Subscribers

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

cancel

Cancel run on Trigger.dev

Cancel a running task

get

Get run on Trigger.dev

Get run details

list

List environments on Trigger.dev

List deployment environments

list

List projects on Trigger.dev

List all projects

list

List runs on Trigger.dev

List task runs

list

List schedules on Trigger.dev

List cron schedules

replay

Replay run on Trigger.dev

Replay a completed task

trigger

Trigger task on Trigger.dev

Trigger a background task

Security & Code Integrity Audit

Every tool in the Trigger.dev MCP Server is continuously audited by the Vinkius Security Engine. We guarantee zero-trust payload isolation, strict data boundaries, and deterministic execution for enterprise-grade AI agents.

A+Score: 100

How Vinkius protects your data

What happens if the underlying API rate limits my agent?

Our edge infrastructure automatically handles backoffs, queueing, and throttling. If an AI agent sends too many erratic requests, Vinkius manages the rate limits gracefully, ensuring your backend doesn't crash.

How does the AI access my passwords and credentials?

It simply doesn't. On Vinkius, your passwords, API keys, and login details are kept in a secure vault. The AI (like ChatGPT or Claude) merely "asks" Vinkius to perform the task. Vinkius opens the door, does the work, and hands the result back to the AI. Your credentials are never seen, read, or learned by the artificial intelligence.

What if the AI ends up reading customer data or confidential information?

We have a built-in digital "bodyguard" called DLP (Data Loss Prevention). If a tool fetches data and the response contains social security numbers, credit cards, or personal customer info, Vinkius magically blocks and erases that information before it is delivered to the AI. The AI works only with what is strictly necessary, and your sensitive data never leaks.

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.

Trigger.dev Capabilities for AI Assistants

Add the Trigger.dev tool to your AI Agents. The toolkit allows Claude and ChatGPT to securely fetch and update targeted data.

background jobs & AI Execution

Use the Trigger.dev MCP to manage background jobs requests. Models like Claude Code utilize this connection to perform reliable ship it updates.

AI-Driven workflow automation Workflows

The Trigger.dev server supports direct MCP connections for workflow automation. This provides Claude with the required permissions to execute ship it functions.