How to Use the Trigger.dev MCP in Cline

Q: If I need to test a scheduled task in Trigger.dev with Cline, what tools do I use?

First, you check existing schedules using listschedules. Then, if needed, you can manually trigger and monitor it by calling triggertask and tracking the results via getrun.

Q: Can Cline handle debugging specific run failures in Trigger.dev?

Absolutely. You use listruns to find the failed job ID, then pass it to getrun. This pulls the exact details needed for you to diagnose why that particular workflow instance broke.

Q: When working on a new feature in Trigger.dev with Cline, how do I verify the scope?

You should always start by running listprojects to confirm the intended project exists, and then run listenvironments to know which deployment target your code needs to respect.

Execute end-to-end workflow testing and development against Trigger.dev using Cline.

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 Cline

Create your Vinkius account to connect Trigger.dev to Cline 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 Cline

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Automate Job Lifecycle Testing

You can write code that manages the entire job lifecycle, from triggering to cancellation. Use `trigger_task` when you want a new background process started for testing. If things go sideways, the agent can call `cancel_run` immediately. This makes your end-to-end tests reliable. Need context? Start by calling `list_projects` to ensure your test script is targeting the right scope in Trigger.dev.

Audit and Inspect Workflow Runs

Testing requires knowing what happened before. The agent can use `list_runs` to pull a manifest of all past job executions. Then, it grabs specific data using `get_run`, pulling the full details into your local environment for inspection. If you fix a bug and want to test that fix against old parameters, `replay_run` allows you to re-execute historical runs without touching the live system.

Map Out Deployment Contexts

To write correct deployment code, you first need the list of available environments. Running `list_environments` shows all possible scopes for your application in Trigger.dev. Similarly, running `list_schedules` gives you a full map of every cron job that needs to be accounted for. Overall context starts with `list_projects`, ensuring your code knows which specific project it's building tests for.

Setup guide

Set up Trigger.dev MCP in Cline

Prerequisites

VS Code with Cline extension installed
Active Vinkius subscription with a valid endpoint token

1

Open Cline MCP settings

Click the Cline icon in the VS Code sidebar to open the Cline panel. Then click the MCP Servers icon (server stack) at the top-right corner of the panel.
2

Add a remote server

Click "Remote Servers" at the top, then click "Add Remote MCP". In the Name field, type triggerdev-mcp. In the URL field, paste your Vinkius endpoint: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp. Get your token from cloud.vinkius.com.
3

Enable the server

After saving, the server appears in the Cline MCP panel. Toggle the switch to enable it. The status indicator turns green when the connection is live.
4

Start using tools

Return to the Cline chat and ask: "Check my latest Trigger.dev refund status." Cline will discover the available tools and request your approval before invoking each one — giving you full control over every action.

Cline MCP Settings

{
  "mcpServers": {
    "triggerdev-mcp": {
      "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 Cline

Cline lets you treat Trigger.dev management like any other API call. Your agent can write code that calls `list_projects` to gather scope data, then use those IDs in subsequent functions. It makes job monitoring part of the build process.

First, you check existing schedules using `list_schedules`. Then, if needed, you can manually trigger and monitor it by calling `trigger_task` and tracking the results via `get_run`.

Absolutely. You use `list_runs` to find the failed job ID, then pass it to `get_run`. This pulls the exact details needed for you to diagnose why that particular workflow instance broke.

It deals with core metadata: project definitions, operational run status, and scheduled cron job configurations across your Trigger.dev setup.

You should always start by running `list_projects` to confirm the intended project exists, and then run `list_environments` to know which deployment target your code needs to respect.

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

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript