Trigger.dev
Trigger.dev's official MCP server lets an AI assistant trigger tasks, inspect runs, and debug background jobs directly from your editor.
Install the MCP server
npx trigger.dev@latest install-mcp
About
The Trigger.dev MCP server connects an AI assistant straight to your Trigger.dev project so it can trigger a task with a payload, list the last N runs filtered by status, and inspect a run's full trace without leaving the chat window. It sits on top of the same durable background-job platform Trigger.dev ships, including retries, queues, and observability, just reachable through natural language instead of the dashboard.
Beyond runtime debugging it can search Trigger.dev's own documentation, scaffold a new project, and report which tasks are currently defined in your codebase, so an agent can go from 'set this task up' to 'why did this run fail' in one conversation. Authentication rides on the Trigger.dev CLI login, and every tool except doc search requires it.
Key features
- Trigger a defined task with a JSON payload straight from chat
- Filter and list recent runs by status to spot failures fast
- Pull full trace details for a single run without opening the dashboard
- Search official Trigger.dev docs without authentication
- Scaffold new projects and inspect currently defined tasks
- One-command installer that auto-detects your MCP client
Use cases
- Asking an agent to trigger a task and report back once the run finishes
- Debugging a failing background job by having the assistant pull the run's full trace
- Bootstrapping a new Trigger.dev project without leaving your AI coding tool
- Building an on-call workflow where the assistant lists recent failed runs on request
Available tools
trigger_task
Triggers a task run with a given payload, e.g. "trigger the tts-generate-audio task with this input".
list_runs
Lists recent runs filtered by status, task, or other criteria to surface failures.
get_run_details
Returns full trace information for a specific run for step-by-step debugging.
get_current_worker
Reports which tasks are currently defined and deployed in a project.
Documentation search
Searches Trigger.dev's official docs and works without authentication.
Frequently asked questions
Do I need to log in before I can use it?
Doc search works without auth, but triggering tasks or reading runs requires logging in via the Trigger.dev CLI the first time you call an authenticated tool.
Which AI clients does the installer support?
install-mcp detects common clients automatically and writes the config for you; you can also add it manually to .claude.json, .cursor/mcp.json, or .vscode/mcp.json.