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.

Trigger.dev MCP Server for Windsurf 8 tools — connect in under 2 minutes

Name: Trigger.dev
Availability: InStock
Author: Vinkius

docs.windsurf.com/windsurf/mcp

Built by Vinkius GDPR 8 Tools IDE

Windsurf brings agentic AI coding to a purpose-built IDE. Connect Trigger.dev through Vinkius and Cascade will auto-discover every tool. ask questions, generate code, and act on live data without leaving your editor.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Trigger.dev and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "triggerdev": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Trigger.dev MCP Server

Connect Trigger.dev to your AI agent and manage your background job infrastructure conversationally.

Windsurf's Cascade agent chains multiple Trigger.dev tool calls autonomously. query data, analyze results, and generate code in a single agentic session. Paste Vinkius Edge URL, reload, and all 8 tools are immediately available. Real-time tool feedback appears inline, so you see API responses directly in your editor.

What you can do

Job Monitoring — List active, completed, and failed task runs with execution times, statuses, and error details.
Project Overview — Query projects, environments, and their associated job definitions.
Run Inspection — Drill into individual runs to view payloads, outputs, logs, and retry history.
Environment Management — Switch between dev, staging, and production environments to inspect runs across your deployment pipeline.

The Trigger.dev MCP Server exposes 8 tools through the Vinkius. Connect it to Windsurf in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Trigger.dev to Windsurf via MCP

Follow these steps to integrate the Trigger.dev MCP Server with Windsurf.

Open MCP Settings

Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"

Add the server

Paste the JSON configuration above into mcp_config.json

Save and reload

Windsurf will detect the new server automatically

Start using Trigger.dev

Open Cascade and ask: "Using Trigger.dev, help me...". 8 tools available

Why Use Windsurf with the Trigger.dev MCP Server

Windsurf provides unique advantages when paired with Trigger.dev through the Model Context Protocol.

Windsurf's Cascade agent autonomously chains multiple tool calls in sequence, solving complex multi-step tasks without manual intervention

Purpose-built for agentic workflows. Cascade understands context across your entire codebase and integrates MCP tools natively

JSON-based configuration means zero code changes: paste a URL, reload, and all 8 tools are immediately available

Real-time tool feedback is displayed inline, so you see API responses directly in your editor without switching contexts

Trigger.dev + Windsurf Use Cases

Practical scenarios where Windsurf combined with the Trigger.dev MCP Server delivers measurable value.

Automated code generation: ask Cascade to fetch data from Trigger.dev and generate models, types, or handlers based on real API responses

Live debugging: query Trigger.dev tools mid-session to inspect production data while debugging without leaving the editor

Documentation generation: pull schema information from Trigger.dev and have Cascade generate comprehensive API docs automatically

Rapid prototyping: combine Trigger.dev data with Cascade's code generation to scaffold entire features in minutes

Trigger.dev MCP Tools for Windsurf (8)

These 8 tools become available when you connect Trigger.dev to Windsurf via MCP:

cancel_run

Cancel a running task

get_run

Get run details

list_environments

List deployment environments

list_projects

List all projects

list_runs

List task runs

list_schedules

List cron schedules

replay_run

Replay a completed task

trigger_task

Trigger a background task

Example Prompts for Trigger.dev in Windsurf

Ready-to-use prompts you can give your Windsurf agent to start working with Trigger.dev immediately.

"Are there any failed background jobs in production?"

"Show me the details of the last 'process-webhook' run."

"How many jobs ran successfully today?"

Troubleshooting Trigger.dev MCP Server with Windsurf

Common issues when connecting Trigger.dev to Windsurf through the Vinkius, and how to resolve them.

Server not connecting

Check Settings → MCP for the server status. Try toggling it off and on.

Trigger.dev + Windsurf FAQ

Common questions about integrating Trigger.dev MCP Server with Windsurf.

How does Windsurf discover MCP tools?

Windsurf reads the mcp_config.json file on startup and connects to each configured server via Streamable HTTP. Tools are listed in the MCP panel and available to Cascade automatically.

Can Cascade chain multiple MCP tool calls?

Yes. Cascade is an agentic system. it can plan and execute multi-step workflows, calling several tools in sequence to accomplish complex tasks without manual prompting between steps.

Does Windsurf support multiple MCP servers?

Yes. Add as many servers as needed in mcp_config.json. Each server's tools appear in the MCP panel and Cascade can use tools from different servers in a single flow.