Skip to main content

​
What is the Trigger.dev MCP Server?

The Trigger.dev MCP (Model Context Protocol) Server enables AI assistants to interact directly with your Trigger.dev projects. It provides a comprehensive set of tools to:
  • Search Trigger.dev documentation
  • Initialize new Trigger.dev projects
  • List and manage your projects and organizations
  • Get task information and trigger task runs
  • Deploy projects to different environments
  • Monitor run details and list runs with filtering options

​
Installation

The quickest way to get set up is the interactive installer: 
npx trigger.dev@latest install-mcp
It will detect your installed clients and configure them automatically. You can also copy-paste the config for your client below.

​
Client Configuration

Each client has a slightly different config format. Copy the snippet for your client into the appropriate file.
Install using the command line:
npx trigger.dev@latest install-mcp --client claude-code
Or add this configuration to ~/.claude.json (user) or .mcp.json (project):
{
  "mcpServers": {
    "trigger": {
      "command": "npx",
      "args": ["trigger.dev@latest", "mcp"]
    }
  }
}
View Claude Code MCP docs ↗
After adding the config, restart your client. You should see a server named trigger connect automatically.

​
Authentication

The search_docs tool works without authentication. All other tools require you to be logged in via the Trigger.dev CLI. The first time you use an authenticated tool, your MCP client will prompt you to log in.
The install-mcp command supports these options:Core Options
  • -p, --project-ref <project ref> — Scope the MCP server to a specific project
  • -t, --tag <package tag> — CLI package version to use (default: latest)
  • --dev-only — Restrict to the dev environment only
  • --yolo — Install into all supported clients automatically
  • --scope <scope> — user, project, or local
  • --client <clients...> — Install into specific client(s)
Configuration Options
  • --log-file <log file> — Write logs to a file
  • -a, --api-url <value> — Custom Trigger.dev API URL
  • -l, --log-level <level> — Log level (debug, info, log, warn, error, none)
ExamplesInstall for all supported clients:
npx trigger.dev@latest install-mcp --yolo
Install for specific clients:
npx trigger.dev@latest install-mcp --client claude-code cursor --scope user
Restrict to dev environment for a specific project:
npx trigger.dev@latest install-mcp --dev-only --project-ref proj_abc123
To add these options to a manual config, append them to the args array:
{
  "args": ["trigger.dev@latest", "mcp", "--dev-only", "--project-ref", "proj_abc123"]
}

​
Getting Started

Once installed, you can start using the MCP server by asking your AI assistant questions like:
  • "Search the trigger docs for a ffmpeg example"
  • "Initialize trigger.dev in my project"
  • "Get all tasks in my project"
  • "Trigger my foobar task with a sample payload"
  • "Get the details of the latest run for my foobar task"
  • "List all runs for my foobar task"
  • "Deploy my project to staging"
  • "Deploy my project to production"

​
Next Steps