How to Use the Trigger.dev MCP in Claude Code

Q: How do I use Claude Code to manage background tasks in Trigger.dev?

You pipe the results of listprojects into a script that then calls triggertask. This allows you to automate the initiation and monitoring of jobs entirely from the terminal.

Q: Can Claude Code check scheduling status for Trigger.dev in CI/CD?

Yes, using listschedules provides a clean, scriptable output of all cron schedules configured in Trigger.dev, perfect for pre-deployment checks.

Q: What is the best way to debug job failures in Trigger.dev using Claude Code?

First, run listruns to get a list of failed runs. Then, use that ID with getrun. The output streams directly into your terminal session for immediate debugging.

Q: When automating a new deployment using Claude Code and Trigger.dev, what scope checks should I perform?

Always check listprojects for the target project, then use listenvironments to verify all possible deployment scopes before running any code.

Script complex Trigger.dev workflow management in Claude Code's terminal environment.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Trigger.dev MCP to Claude Code

Create your Vinkius account to connect Trigger.dev to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Trigger.dev with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Programmatic Task Control

The agent can control background jobs directly from the command line. Use `trigger_task` to start a job for testing or processing, and use `cancel_run` if that task needs to be killed immediately. This is perfect for shell scripts needing immediate operational feedback. Need visibility? You'll check current status using `get_run` on any given run ID.

CI/CD Workflow Auditing

Running in a pipeline, you need to verify job history. The MCP Server lets you use `list_runs` and then pull detailed logs using `get_run`. This is faster than any UI dashboard for CI/CD checks. Furthermore, if the build fails due to an old issue, `replay_run` gives you a clean way to re-test that job's definition without manual cleanup.

Map Project and Schedule Scope

Before scripting anything, map out your entire system using the listing tools. Run `list_projects` to get every project name available for deployment scope. Then use `list_environments` to pinpoint which environments are valid targets. For scheduling checks, simply execute `list_schedules`. This confirms all cron jobs that need to be managed by your script in Trigger.dev.

Setup guide

Set up Trigger.dev MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see triggerdev-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Trigger.dev transactions." It will automatically discover and invoke the available Trigger.dev tools.

Terminal

claude mcp add --transport http triggerdev-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Trigger.dev MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "triggerdev-mcp": {
      "type": "url",
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Trigger.dev. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Trigger.dev now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Trigger.dev MCP in Claude Code

You pipe the results of `list_projects` into a script that then calls `trigger_task`. This allows you to automate the initiation and monitoring of jobs entirely from the terminal.

Yes, using `list_schedules` provides a clean, scriptable output of all cron schedules configured in Trigger.dev, perfect for pre-deployment checks.

First, run `list_runs` to get a list of failed runs. Then, use that ID with `get_run`. The output streams directly into your terminal session for immediate debugging.

The server manages project definitions, task run status (including replay context), and scheduled cron job metadata from your Trigger.dev setup.

Always check `list_projects` for the target project, then use `list_environments` to verify all possible deployment scopes before running any code.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python