triggerdotdev
MCP server accessible from the CLI dev command
When you're running the dev command you should be able to pass --mcp like this:
npx trigger.dev@latest dev --mcp --mcp-port 3001
As well as running the normal dev command (so you can execute tasks using your local code on your machine), this would spin up an MCP server.
The main use case would be to trigger tasks and debug your runs from something like Cursor.
Use cases
1. Triggering runs
User: "Can you help me trigger my 'process-stripe-webhooks' task from my backend?"
Cursor: "Yes, I'll help you trigger your Trigger.dev task. Let me investigate using the MCP tools."
Cursor: ...
2. Debugging a run using the source code and logs
User: "My Stripe webhook task 'process-stripe-webhooks' is failing. Can you help me diagnose and fix it?"
Cursor: "I'll help you troubleshoot your Trigger.dev task. Let me investigate using the MCP tools."
Cursor: ...
Hey @matt-aitken, sorry if this is a noob question—but I noticed that this PR was merged, yet the related issue is still open. I also wasn’t able to get it working on my end. Was the feature released behind a flag, or is there something else I’m missing?
@eelior the relevant packages haven’t been released yet because we’re about to do our v4 beta release. It will be this week.