Add the Trigger.dev MCP server to Windsurf

Config last verified Jun 1, 2026

The exact config to run Trigger.dev in Windsurf — paste it in, restart, and the tools load.

Prerequisites

Windsurf installed.
TRIGGER_ACCESS_TOKEN — Trigger.dev personal access token (tr_pat_...). Authenticates the MCP server. Obtained via trigger.dev login or the dashboard.

Setup

1. Open `~/.codeium/windsurf/mcp_config.json`

On Windows the file lives at %USERPROFILE%\.codeium\windsurf\mcp_config.json.

2. Add this configuration

Add to ~/.codeium/windsurf/mcp_config.json

~/.codeium/windsurf/mcp_config.json

json

{
  "mcpServers": {
    "trigger-dev": {
      "command": "npx",
      "args": [
        "-y",
        "trigger.dev@latest",
        "mcp"
      ],
      "env": {
        "TRIGGER_ACCESS_TOKEN": "<TRIGGER_ACCESS_TOKEN>"
      }
    }
  }
}

3. Restart Windsurf and confirm the Trigger.dev tools load.

Gotchas

Windsurf's Cascade reads MCP servers from an "mcpServers" object in ~/.codeium/windsurf/mcp_config.json. Unlike most clients, remote servers are configured with the "serverUrl" field rather than "url", so a config that uses "url" silently fails to connect. Native remote transport is supported without an OAuth flow.

← Back to the Trigger.dev MCP server