The MCP server for @triggerdotdev does a lot more than deploy and trigger tasks now.
Your coding assistant can chat with your deployed agents, manage prompt versions, and pull a health report. All from Claude Code or Cursor. ↓
Trigger.dev
@triggerdotdev
Build and deploy fully‑managed AI agents and workflows.
→ trigger.dev
→ github.com/triggerdotdev
→ trigger.dev/discord
- You could always see what a task did. Now you can see what it spent. Every LLM call your @triggerdotdev tasks make becomes a span in the trace. One flag, 𝚎𝚡𝚙𝚎𝚛𝚒𝚖𝚎𝚗𝚝𝚊𝚕_𝚝𝚎𝚕𝚎𝚖𝚎𝚝𝚛𝚢, on any Vercel AI SDK call. Nothing to install. Whole AI bill, or any single
- 𝚌𝚑𝚊𝚝.𝚊𝚐𝚎𝚗𝚝 is a chat backend where every conversation runs on its own real machine. It boots on the first message, runs as long as the work takes, and keeps its memory between turns. Here's how one is put together, with @triggerdotdev ↓
- SCIM directory sync is live for orgs on SSO. Assign someone to @triggerdotdev in your IdP and they land in your org. Unassign them and their access is gone. Okta, Microsoft Entra, Google Workspace, JumpCloud, OneLogin, and more.
- chat.agent is live on Product Hunt today (hunted by @fmerian) It's our durable backend for AI chat apps. Every conversation gets its own machine that lives for the whole conversation, sleeps when nobody's typing, and wakes up where it left off.
