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

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

Run the command listschedules to see all active cron jobs managed by this MCP Server. For immediate status, use getrun .

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

You can programmatically set them using createenvvar or update existing ones with updateenvvar. This allows your scripts to be fully self-contained.

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

If you need to test a job manually, use triggertask . To see historical runs, pipe the output of listruns into your script.

Q: What are the best practices for managing concurrency with Trigger.dev (Background Tasks & Jobs) and Claude Code?

Use overridequeueconcurrency to limit how many tasks run at once. If you need to stop processing entirely, use pauseresumequeue.

Q: What is the best way to set up scheduled jobs using Trigger.dev (Background Tasks & Jobs) and Claude Code?

Start by calling createschedule with your cron expression. Then, verify it works immediately by running a test job via triggertask.

Write CI/CD pipelines and cron jobs for headless execution with Claude Code.

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 Claude Code

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Schedule Jobs from the Terminal

Need a task to run every night? Use `create_schedule` to set up an IMPERATIVE cron job right in your script. This is pure terminal automation. You can also manage scheduled jobs by listing them with `list_schedules`, making it easy to audit what's running automatically.

Control Job Status and Context

A job needs manual intervention? Use `complete_waitpoint` when the task is ready. For monitoring, run `get_run` or `list_runs`. This gives you instant status updates in your CI/CD output. If a critical step fails, use `cancel_run` to stop unnecessary processing immediately.

Manage Credentials and State

Don't hardcode secrets. Use the MCP Server's tools: `create_env_var`, `update_env_var`, or `delete_env_var`. This keeps your environment variables clean and accessible via shell commands. Need to check what keys are available? Just run `list_env_vars`.

Setup guide

Set up Trigger.dev (Background Tasks & Jobs) 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-background-tasks-jobs-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Trigger.dev (Background Tasks & Jobs) transactions." It will automatically discover and invoke the available Trigger.dev (Background Tasks & Jobs) tools.

Terminal

claude mcp add --transport http triggerdev-background-tasks-jobs-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 (Background Tasks & Jobs) 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-background-tasks-jobs-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 (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 Claude Code

Run the command `list_schedules` to see all active cron jobs managed by this MCP Server. For immediate status, use `get_run `.

You can programmatically set them using `create_env_var` or update existing ones with `update_env_var`. This allows your scripts to be fully self-contained.

If you need to test a job manually, use `trigger_task `. To see historical runs, pipe the output of `list_runs` into your script.

Use `override_queue_concurrency` to limit how many tasks run at once. If you need to stop processing entirely, use `pause_resume_queue`.

Start by calling `create_schedule` with your cron expression. Then, verify it works immediately by running a test job via `trigger_task`.

Use it with your favorite AI tools

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

OpenAI Agents SDK sdk-python