How to Use the Trigger.dev MCP in Claude

Q: How do I check my Trigger.dev project status using Claude Desktop?

You can call listprojects to see all available projects. Then, use getrun(runid) to get the current status of any specific run ID within those projects.

Q: What is the best way to trigger a test job using Trigger.dev with Claude Desktop?

The triggertask tool lets your agent start a background task immediately, bypassing the need to log into the dashboard. This is great for quick testing when you're just chatting with your AI client.

Get full visibility into CI/CD pipelines, whether you're using the Claude Desktop app or claude.ai in the browser.

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

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Monitor your deployments with Claude Desktop

You can see all active projects and available environments using `list_projects` and `list_environments`. This lets you check if a deployment target exists before running any commands, regardless of whether you're in the native app or connected via URL. You also get full visibility into scheduling with the `list_schedules` tool. Check when jobs are set to run using this list, and then confirm that job details by calling `get_run(run_id)`.

Control tasks directly via Claude Desktop

Need to test something immediately? You can force a workflow to start right away by invoking `trigger_task(project, task)`. If that task goes sideways, don't panic—you can shut it down using the `cancel_run` tool. If you need to manually rerun a job for testing, use `replay_run(run_id)`. This lets your agent re-execute a completed workflow without needing manual intervention on the dashboard.

Manage task history with Claude Desktop

Tracking down why something failed months ago is easy. The `list_runs` tool gives you an overview of all historical attempts, and `get_run(run_id)` pulls the granular details for any specific run ID. Use `list_projects` first to narrow your scope, then use `list_runs` to get a targeted list of runs. This lets your agent pull exactly what you need from the MCP Server.

Setup guide

Set up Trigger.dev MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The Trigger.dev MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Trigger.dev MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under triggerdev-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 Claude Desktop

You can call `list_projects` to see all available projects. Then, use `get_run(run_id)` to get the current status of any specific run ID within those projects.

The Desktop app handles this via local stdio transport, letting tools run as subprocesses on your machine. For the web browser (claude.ai), you must use a custom connector and provide a publicly reachable HTTPS URL for the MCP Server.

The `trigger_task` tool lets your agent start a background task immediately, bypassing the need to log into the dashboard. This is great for quick testing when you're just chatting with your AI client.

No. While the Desktop app supports local access, Claude Web (claude.ai) also supports connecting remote MCP Servers via a custom connector URL in Settings → Integrations.

It primarily handles Project Metadata and Task Run IDs, allowing your agent to read details 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