Bring Background Jobs
to Claude Desktop
Create your Vinkius account to connect Trigger.dev to Claude Desktop and start using all 8 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Trigger.dev MCP Server?
Connect Trigger.dev to your AI agent and manage your background job infrastructure conversationally.
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.
How it works
- Subscribe to the Trigger.dev integration on the marketplace.
- Generate a Secret API Key from your Trigger.dev dashboard (Project → API Keys section — keys start with
tr_dev_ortr_prod_). - Ask your AI agent to list job runs, check failures, or inspect task outputs.
Who is this for?
- Backend Developers — Monitor background job health, debug failed runs, and verify task outputs without leaving your code editor.
- DevOps Engineers — Track job execution across environments and identify bottlenecks in your processing pipeline.
- Technical Leads — Get instant visibility into production job queues during incident response without switching to the Trigger.dev dashboard.
Built-in capabilities (8)
Cancel a running task
Get run details
List deployment environments
List all projects
List task runs
List cron schedules
Replay a completed task
Trigger a background task
Why Claude Desktop?
Claude Desktop is the definitive way to connect Trigger.dev to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 8 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Trigger.dev in Claude Desktop
Why run Trigger.dev with Vinkius?
The Trigger.dev connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 8 tools are ready to work instantly without any complex setup.
You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.
* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure
Over 4,000 integrations ready for AI agents
Explore a vast library of pre-built integrations, optimized and ready to deploy.
Connect securely in under 30 seconds
Generate tokens to authenticate and link external services in a single step.
Complete visibility into every agent action
Audit live requests, latency, success rates, and active security compliance policies.
Optimize spending and track token ROI
Analyze real-time token consumption and cost metrics detailed by connection.
Explore our live AI Agents Analytics dashboard to see it all working
This dashboard is included when you connect Trigger.dev using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
Trigger.dev and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect Trigger.dev to Claude Desktop through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.
Raw MCP | Vinkius | |
|---|---|---|
| Ready-to-use MCPs | Find and configure each manually | 4,000+ MCPs ready to use |
| Connection Setup | Manual coding & server setup | 1-click instant connection |
| Server Hosting | You host it yourself (needs 24/7 uptime) | 100% hosted & managed by Vinkius |
| Security & Privacy | Stored in plaintext config files | Bank-grade encrypted vault |
| Activity Visibility | Blind execution (no logs or tracking) | Live dashboard with real-time logs |
| Cost Control | Runaway AI token spend risk | Automatic budget limits |
| Revoking Access | Must delete files or code to stop | 1-click disconnect button |
How Vinkius secures
Trigger.dev for Claude Desktop
Every request between Claude Desktop and Trigger.dev is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.
Frequently asked questions
How do I get my Trigger.dev API key?
Log in to your Trigger.dev dashboard at cloud.trigger.dev. Open your project, then find the API Keys section in the project settings. Copy your Secret API Key (it starts with tr_dev_ for development or tr_prod_ for production). Paste it into the configuration field below. For Personal Access Tokens (used for admin operations), go to Profile → Personal Access Tokens tab instead.
Can my AI agent tell me why a background job failed in production?
Yes. Ask your agent to list failed runs and it returns the task name, error message, stack trace, execution duration, and retry count for each failure. You can then drill into a specific run to see the exact input payload and which step failed — cutting your debugging time from minutes to seconds.
What if I'm on-call and need to check job health at 2 AM?
Just ask your AI agent 'Are there any failed jobs in production?' and get an instant triage report — number of failures, which tasks are affected, when they started failing, and whether retries resolved them. No need to open a browser, log in, or navigate dashboards in the middle of the night.
Does it support multiple environments like dev, staging, and production?
Yes. Each API key is scoped to a specific environment (dev or prod), just like in Trigger.dev itself. You can configure separate integrations for each environment, or switch between them by updating the API key — giving you full control over which environment your AI agent queries.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
UPYUN Developer Platform
5 toolsBring UPYUN's Massive CDN and Image Processing APIs to your AI. Interact with buckets and deploy files to the cloud.
Coda
11 toolsCombine docs, spreadsheets, and apps into powerful all-in-one documents that grow with your team and automate routine work.
Orkes Conductor
6 toolsOrchestrate microservice workflows via Orkes Conductor — list definitions, track running executions, search workflow history, and inspect task states from any AI agent.
YAML/JSON Converter
1 toolsPrevent DevOps YAML hallucination. Convert complex YAML files to JSON for safe AI processing, and back to perfect YAML.