How to Use the Trigger.dev MCP in VS Code Copilot

Q: How does Trigger.dev improve team consistency in VS Code Copilot?

By committing the MCP configuration to .vscode/mcp.json, every developer on the team automatically gets access to tools like listprojects and listenvironments. This makes project visibility standardized across all machines.

Q: Can I use Trigger.dev to test a feature in VS Code Copilot?

Yes. You can use triggertask(project, task) to start the background job, and then use getrun(runid) to monitor its success or failure right from your terminal within the editor.

Standardize workflow management for your entire engineering team using VS Code Copilot's MCP Server integration.

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 VS Code Copilot

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Manage shared resources with VS Code Copilot

The `list_projects` and `list_environments` tools allow the entire team to see exactly what projects are available and which deployment targets exist. This knowledge is committed to the repo, ensuring every developer works off the same source of truth. Furthermore, using `list_schedules` lets your whole team audit when background jobs are scheduled, making governance transparent across the board.

Control and test tasks as a team with VS Code Copilot

If QA finds a bug in a workflow, developers can immediately use `trigger_task(project, task)` to replicate the failure. If the fix needs testing, the same tool lets them run it for everyone to see. If things get out of hand, the team can call `cancel_run(run_id)` to stop a runaway job right from within their standard VS Code workflow.

Audit historical runs with VS Code Copilot

When tracking down difficult bugs, you need history. The `list_runs` tool provides an overview of all task attempts, and the team can then use `get_run(run_id)` to pull the full execution details for any specific run. This ability means developers can review past failures without needing special access or leaving the IDE.

Setup guide

Set up Trigger.dev MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Trigger.dev MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Trigger.dev tools listed. Try asking: "List my recent Trigger.dev transactions" and Copilot will invoke them automatically.

.vscode/mcp.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 VS Code Copilot

By committing the MCP configuration to `.vscode/mcp.json`, every developer on the team automatically gets access to tools like `list_projects` and `list_environments`. This makes project visibility standardized across all machines.

Yes. You can use `trigger_task(project, task)` to start the background job, and then use `get_run(run_id)` to monitor its success or failure right from your terminal within the editor.

The MCP Server provides a committed, centralized way for your AI client to interact with Trigger.dev's API. This lets developers execute complex actions like listing schedules or replaying runs without leaving their usual coding environment.

You can set it up globally by opening User Configuration via Cmd+Shift+P. However, setting it in `.vscode/mcp.json` is best practice because it shares the tools across your entire engineering team.

The server touches Project Metadata and Task Run IDs, giving the agent access to operational data about which projects exist and the historical execution status of tasks within those projects.

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