Trigger.dev MCP Server for Cline 8 tools — connect in under 2 minutes
Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Trigger.dev through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Trigger.dev and 2,500+ MCP Servers from a single visual interface.
{
"mcpServers": {
"triggerdev": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About Trigger.dev MCP Server
Connect Trigger.dev to your AI agent and manage your background job infrastructure conversationally.
Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Trigger.dev tool calls without waiting for prompts between steps. Connect 8 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.
What you can do
- Job Monitoring — List active, completed, and failed task runs with execution times, statuses, and error details.
- Project Overview — Query projects, environments, and their associated job definitions.
- Run Inspection — Drill into individual runs to view payloads, outputs, logs, and retry history.
- Environment Management — Switch between dev, staging, and production environments to inspect runs across your deployment pipeline.
The Trigger.dev MCP Server exposes 8 tools through the Vinkius. Connect it to Cline in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect Trigger.dev to Cline via MCP
Follow these steps to integrate the Trigger.dev MCP Server with Cline.
Open Cline MCP Settings
Click the MCP Servers icon in the Cline sidebar panel
Add remote server
Click "Add MCP Server" and paste the configuration above
Enable the server
Toggle the server switch to ON
Start using Trigger.dev
Ask Cline: "Using Trigger.dev, help me...". 8 tools available
Why Use Cline with the Trigger.dev MCP Server
Cline provides unique advantages when paired with Trigger.dev through the Model Context Protocol.
Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts
Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window
Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation
Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing
Trigger.dev + Cline Use Cases
Practical scenarios where Cline combined with the Trigger.dev MCP Server delivers measurable value.
Autonomous feature building: tell Cline to fetch data from Trigger.dev and scaffold a complete module with types, handlers, and tests
Codebase refactoring: use Trigger.dev tools to validate live data while Cline restructures your code to match updated schemas
Automated testing: Cline fetches real responses from Trigger.dev and generates snapshot tests or mocks based on actual payloads
Incident response: query Trigger.dev for real-time status and let Cline generate hotfix patches based on the findings
Trigger.dev MCP Tools for Cline (8)
These 8 tools become available when you connect Trigger.dev to Cline via MCP:
cancel_run
Cancel a running task
get_run
Get run details
list_environments
List deployment environments
list_projects
List all projects
list_runs
List task runs
list_schedules
List cron schedules
replay_run
Replay a completed task
trigger_task
Trigger a background task
Example Prompts for Trigger.dev in Cline
Ready-to-use prompts you can give your Cline agent to start working with Trigger.dev immediately.
"Are there any failed background jobs in production?"
"Show me the details of the last 'process-webhook' run."
"How many jobs ran successfully today?"
Troubleshooting Trigger.dev MCP Server with Cline
Common issues when connecting Trigger.dev to Cline through the Vinkius, and how to resolve them.
Server shows error in sidebar
Trigger.dev + Cline FAQ
Common questions about integrating Trigger.dev MCP Server with Cline.
How does Cline connect to MCP servers?
Can Cline run MCP tools without approval?
Does Cline support multiple MCP servers at once?
Connect Trigger.dev with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Trigger.dev to Cline
Get your token, paste the configuration, and start using 8 tools in under 2 minutes. No API key management needed.