How to Use the Trigger.dev (Background Tasks & Jobs) MCP in Cline

Q: How do I search for background tasks using Trigger.dev (Background Tasks & Jobs) and Cline?

You can see all active job schedules by calling listschedules. For immediate status checks, use the getrun tool to pull specific run data.

Q: What is the best way to manage environment variables for Trigger.dev (Background Tasks & Jobs) and Cline?

Use listenvvars first to see what exists. Then, use createenvvar or updateenvvar to set or modify them before running a service.

Q: How do I search for background tasks using Trigger.dev (Background Tasks & Jobs) and Cline?

If you need to re-run a job because of a bug, just call replayrun on the old run ID. This is much faster than setting up a whole new schedule.

Execute and manage complex jobs end-to-end with Cline's coding agent.

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 (Background Tasks & Jobs) MCP to Cline

Create your Vinkius account to connect Trigger.dev (Background Tasks & Jobs) 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 (Background Tasks & Jobs) with Cline

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Run and Test Jobs

You tell Cline to run a job, and it executes the task immediately via `trigger_task`. It can also replay old tasks using `replay_run` for thorough testing. When writing code that interacts with background jobs, you'll use `get_batch_results` to confirm if your function calls successfully completed their work.

Build and Manage Environments

Setting up a new feature requires specific variables. Cline uses `create_env_var` to set them, or `list_env_vars` to see what's already there. It also lets you update these settings with `update_env_var`. If you need to tear down the environment after testing, use `delete_env_var`. This keeps your workspace clean.

Control Job Lifecycles

When a job is running, sometimes you gotta hit pause. Use `pause_resume_queue` to manage concurrency for large queues of tasks. For critical jobs that need immediate attention, the agent can cancel them using `cancel_run`. It also gives you ways to extend or complete specific steps with `complete_waitpoint`.

Setup guide

Set up Trigger.dev (Background Tasks & Jobs) 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-background-tasks-jobs-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 (Background Tasks & Jobs) 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-background-tasks-jobs-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 (Background Tasks & Jobs) 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 (Background Tasks & Jobs) MCP in Cline

You can see all active job schedules by calling `list_schedules`. For immediate status checks, use the `get_run` tool to pull specific run data.

Use `list_env_vars` first to see what exists. Then, use `create_env_var` or `update_env_var` to set or modify them before running a service.

If you need to re-run a job because of a bug, just call `replay_run` on the old run ID. This is much faster than setting up a whole new schedule.

The MCP Server handles tasks, schedules, and environment variables. It doesn't manage external API keys or user permissions—you still gotta handle those in your code.

The server touches the state of environment variables. You must ensure that any secrets passed through `create_env_var` are handled securely in your project's vault.

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