Issue 2026-11-10 Β· Voices

Guillermo Rauch @rauchg

So bullish on MCP. Its utility exceeds the "M" part: even AI aside, it'll be a civilization-scale accomplishment to get all our systems communicating through one universal open protocol. A missing piece was how to get arbitrary callbacks across sessions. MCP could read and write, but it couldn't tell you later "this event happened." MCP Events fixes this. We're adding support in our own MCP. Say an agent makes a deployment, and wants to know when it's complete. Instead of polling, it can subscribe to πšπšŽπš™πš•πš˜πš’πš–πšŽπš—πš.𝚜𝚞𝚌𝚌𝚎𝚎𝚍𝚎𝚍. PSA: With Vercel Queues and Workflows, writing the backend machinery for your own MCPs to do this is easy peasy. [引用 @vercel_dev]: Vercel MCP now publishes events. Agents can subscribe to events like πšπšŽπš™πš•πš˜πš’πš–πšŽπš—πš.𝚜𝚞𝚌𝚌𝚎𝚎𝚍𝚎𝚍 and πšπšŽπš™πš•πš˜πš’πš–πšŽπš—πš.πšŽπš›πš›πš˜πš› and get webhook notifications when they fire. No more polling for changes. Changelog β†’ https://t.co/YCAXxa5Bcs https://t.co/de030gQEH1

X12 d ago
Read original β†—