Add the Trigger.dev MCP server to Claude Desktop

Config last verified Jun 1, 2026

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

Prerequisites

Claude Desktop 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 `~/Library/Application Support/Claude/claude_desktop_config.json`

On Windows the file lives at %APPDATA%\Claude\claude_desktop_config.json.

2. Add this configuration

Add to ~/Library/Application Support/Claude/claude_desktop_config.json

~/Library/Application Support/Claude/claude_desktop_config.json

json

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

3. Restart Claude Desktop and confirm the Trigger.dev tools load.

Gotchas

Claude Desktop reads MCP servers from an "mcpServers" object, but the config file is stdio-only: it cannot dial a remote URL directly. To reach a remote server you bridge it locally by running "npx mcp-remote <url>" as the command. Native remote Connectors exist on paid plans, but not through this config file, so the bridge is the portable path.

← Back to the Trigger.dev MCP server