Trigger.dev MCP Server

Lets an assistant trigger, monitor and deploy Trigger.dev background tasks and query run data.

Official · Trigger.dev JavaScript Local · stdio DevOps and monitoringDeveloper tools

115 popularity score ★ 17k ↓ 1.2M/wk

Connect your client

Local (npm)

Add in one click

Opens the app, which asks before it adds the server.

Or add it by command or config

Claude CodeTerminal
claude mcp add trigger-dev -- npx -y trigger.dev mcp
Claude Desktopclaude_desktop_config.json
{
  "mcpServers": {
    "trigger-dev": {
      "command": "npx",
      "args": [
        "-y",
        "trigger.dev",
        "mcp"
      ]
    }
  }
}
Cursor~/.cursor/mcp.json
{
  "mcpServers": {
    "trigger-dev": {
      "command": "npx",
      "args": [
        "-y",
        "trigger.dev",
        "mcp"
      ]
    }
  }
}
VS Code.vscode/mcp.json
{
  "servers": {
    "trigger-dev": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "trigger.dev",
        "mcp"
      ]
    }
  }
}
Codex~/.codex/config.toml
[mcp_servers.trigger-dev]
command = "npx"
args = ["-y", "trigger.dev", "mcp"]
Gemini CLITerminal
gemini mcp add --scope user trigger-dev npx -- -y trigger.dev mcp

What it does

Trigger.dev is an open-source platform for building and running background jobs, workflows and AI agents in TypeScript, hosted or self-hosted. Its MCP server, run through the Trigger.dev CLI, lets a coding assistant work with your projects: search the Trigger.dev docs, set up Trigger.dev in a project, list organisations and projects, see the current worker and its tasks, trigger tasks with a payload, follow runs and their logs, wait for a run to finish, cancel runs, and deploy to staging or production.

It can also query run data with TRQL and the built-in dashboards and health reports, start and stop the local dev server, and talk to chat agents registered in your worker. Flags restrict it to the dev environment (--dev-only), hide the write tools deploy, trigger_task and cancel_run (--readonly), or scope it to one project (--project-ref).

The quickest setup is npx trigger.dev@latest install-mcp, which detects installed MCP clients and configures them; the configured command is npx trigger.dev@latest mcp. search_docs works without an account; the other tools need you to be logged in through the Trigger.dev CLI, and the client prompts for login on first use.

What it needs

RuntimeNode.js

Tools 31

search_docs
Search the Trigger.dev documentation for guides, examples, and API references.
list_orgs
List all organizations you have access to.
list_projects
List all projects in your Trigger.dev account.
create_project_in_org
Create a new project in an organization.
initialize_project
Initialize Trigger.dev in your project with automatic setup and configuration.
get_current_worker
Get the current worker for a project, including worker version, SDK version, and registered tasks.
trigger_task
Trigger a task to run with a specific payload, including delay, tags, retries, and other options.
get_run_details
Get detailed information about a specific task run, including logs and status.
list_runs
List runs for a project with filtering by status, task, tags, version, and time period.
wait_for_run_to_complete
Wait for a specific run to finish and return the result.
cancel_run
Cancel a running or queued run.
deploy
Deploy your project to staging or production.
list_deploys
List deployments for a project with filtering by status or time period.
list_preview_branches
List all preview branches in the project.
whoami
Show the current authenticated user, active CLI profile, email, and API URL.
list_profiles
List all configured CLI profiles and which one is currently active.
switch_profile
Switch the active CLI profile for this MCP session.
get_query_schema
Get the schema for TRQL queries with available tables, columns, and data types.
query
Execute a TRQL query against your Trigger.dev data for analyzing runs and metrics.
list_dashboards
List available built-in dashboards with their widgets.
run_dashboard_query
Execute a single widget query from a built-in dashboard.
get_report
Render an interpreted health report as text with sparklines.
start_dev_server
Start the Trigger.dev dev server in the background.
stop_dev_server
Stop the running Trigger.dev dev server.
dev_server_status
Check the status of the dev server and view recent output.
list_agents
List all chat agents registered in the current worker.
start_agent_chat
Start a conversation with a chat agent.
send_agent_message
Send a message to an active agent chat and get the response.
close_agent_chat
Close an agent chat conversation.
read_session_channel
Read records from a session's realtime stream.
write_session_channel
Append one record to a named side channel's input stream.

Similar servers