Add the Trigger.dev MCP server to VS Code

Config last verified Jun 1, 2026

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

Prerequisites

VS Code 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 `.vscode/mcp.json`

2. Add this configuration

Add to .vscode/mcp.json

.vscode/mcp.json

json

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

Heads up

VS Code uses the `servers` key (not `mcpServers`) and requires `type`.

3. Restart VS Code and confirm the Trigger.dev tools load.

Gotchas

VS Code uses the `servers` key (not `mcpServers`) and requires `type`.

VS Code is the exception to every other client: its top-level key is "servers", not "mcpServers", and each entry needs an explicit "type" (for example "http" or "stdio"). Secrets are not inlined; instead you declare an "inputs" array and reference each value as ${input:id}, so VS Code prompts for it once and never writes it to disk. Remote servers connect natively with OAuth.

← Back to the Trigger.dev MCP server