How to Use the Trigger.dev MCP in Windsurf

Q: Can Windsurf view all my scheduled jobs in Trigger.dev?

Yep. Using listschedules gives you a full list of cron schedules configured within Trigger.dev. This is crucial for making sure your agent knows what recurring tasks are running.

Q: If I need to debug a specific run in Trigger.dev, how do I do it with Windsurf?

You grab the run ID first by using listruns. Then, you pass that ID into the getrun tool within Windsurf. It pulls all the raw details for that specific execution right into your workflow.

Q: Does Windsurf support replaying old jobs from Trigger.dev?

Yes. The replayrun tool allows you to take a completed task's definition and rerun it programmatically through the MCP Server, letting you test fixes without manual intervention.

Manage and automate background jobs in Trigger.dev workflows directly within Windsurf.

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 Windsurf

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Control Background Tasks

You can initiate or cancel automated processes using `trigger_task` or `cancel_run`. If a task is running, you'll first use `get_run` to grab its current status before taking action. This gives your autonomous agent precise control over the execution lifecycle. You also need visibility into what's happening across your accounts. Use `list_projects` to see every project available and `list_environments` to check which deployment settings are active.

Monitor Workflow History

Windsurf lets you track the full history of background jobs. The `list_runs` tool returns a list of past task executions, giving immediate context about what ran and when. You can then use `get_run` to pull detailed results for any specific run ID. Need to check scheduled tasks? `list_schedules` shows all cron jobs set up in Trigger.dev. Plus, if something finished but failed, you can run `replay_run` to re-test the job without manually modifying anything.

Discover All Available Jobs

Start by getting a clear picture of your setup using `list_projects`. This function returns every project defined in Trigger.dev, letting you scope out where to start your automation effort. Once you know the projects, you can list all associated jobs with `list_runs`. Remember that many workflows are tied to specific environments. Calling `list_environments` ensures Cascade knows exactly which deployment context it needs for the next step of the plan.

Setup guide

Set up Trigger.dev MCP in Windsurf

Prerequisites

Windsurf IDE installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Click the Cascade assistant icon in the sidebar, then click the hammer icon (🔨) at the top of the panel. Select "Configure" to open ~/.codeium/windsurf/mcp_config.json.
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

Refresh MCPs

Go back to the hammer icon (🔨) in Cascade and click "Refresh". Windsurf will detect the new server. No full restart is needed — the connection is hot-reloaded.
4

Verify in Cascade

Start a new Cascade conversation and ask something like "Show my Trigger.dev payment history." If connected, Cascade will call the Trigger.dev tools directly. You will see a green dot next to the server name in the MCP panel.

mcp_config.json

{
  "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 Windsurf

Windsurf lets your agent interact with Trigger.dev's API directly. You don't need to open a browser; instead, you simply tell it the goal—like 'cancel this run.' The platform handles sending the command and getting the result back.

Yep. Using `list_schedules` gives you a full list of cron schedules configured within Trigger.dev. This is crucial for making sure your agent knows what recurring tasks are running.

You grab the run ID first by using `list_runs`. Then, you pass that ID into the `get_run` tool within Windsurf. It pulls all the raw details for that specific execution right into your workflow.

This server handles project metadata, task run status (success/failure), and cron schedule definitions. Essentially, it deals with the operational context of your workflows in Trigger.dev.

Yes. The `replay_run` tool allows you to take a completed task's definition and rerun it programmatically through the MCP Server, letting you test fixes without manual intervention.

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