Add the Trigger.dev MCP server to Claude Code
Config last verified Jun 1, 2026
The exact config to run Trigger.dev in Claude Code — paste it in, restart, and the tools load.
Prerequisites
- Claude 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 ~/.claude.json
2. Add this configuration
Add to ~/.claude.json
~/.claude.json
json
{
"mcpServers": {
"trigger-dev": {
"command": "npx",
"args": [
"-y",
"trigger.dev@latest",
"mcp"
],
"env": {
"TRIGGER_ACCESS_TOKEN": "<TRIGGER_ACCESS_TOKEN>"
}
}
}
}Or via CLI
bash
claude mcp add trigger-dev -- npx -y trigger.dev@latest mcp3. Restart Claude Code and confirm the Trigger.dev tools load.
Gotchas
Claude Code stores MCP servers under an "mcpServers" object in ~/.claude.json. It also reads a project-scoped .mcp.json and supports adding servers from the command line with "claude mcp add". Each entry must declare either a "type" or a "command"; Claude Code refuses an entry that has neither. Remote servers connect natively over Streamable HTTP with OAuth.