Vercel 为其 MCP 加入 Events 事件订阅功能
So bullish on MCP. Its utility exceeds the "M" part: even AI aside, it'll be a civilization-scale ac...
Rauch 这条推文把 MCP 一个长期痛点讲得很清楚：以前智能体只能轮询等结果，现在 Vercel MCP 直接支持事件订阅，部署成功或失败会主动推 webhook 通知。你自己想搭 MCP 的话，他用 Queues 和 Workflows 给了现成方案，做智能体后端的开发者可以直接抄。
Vercel CEO Guillermo Rauch 宣布 Vercel MCP 现已支持发布事件，智能体可以订阅 deployment.succeeded、deployment.error 等事件，并在事件触发时收到 webhook 通知。此前 MCP 只能读写数据，无法跨会话主动告知"某事件已发生"，智能体只能靠轮询查询状态。
新机制解决了这个缺口：例如智能体发起一次部署后，可以直接订阅 deployment.succeeded 事件，部署完成时会收到回调，而不必反复轮询。Rauch 还提示开发者可用 Vercel Queues 和 Workflows 轻松搭建自己 MCP 的事件后端。
Rauch 认为如果所有系统能通过一个通用开放协议通信，其意义将超出 AI 本身。此次事件回调能力补上了 MCP 协议在异步通知上的短板，对构建长时间运行智能体工作流的开发者尤为实用。
So bullish on MCP. Its utility exceeds the "M" part: even AI aside, it'll be a civilization-scale ac...
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 Developers @vercel_dev Vercel MCP now publishes events. Agents can subscribe to events like 𝚍𝚎𝚙𝚕𝚘𝚢𝚖𝚎𝚗𝚝.𝚜𝚞𝚌𝚌𝚎𝚎𝚍𝚎𝚍 and 𝚍𝚎𝚙𝚕𝚘𝚢𝚖𝚎𝚗𝚝.𝚎𝚛𝚛𝚘𝚛 and get webhook notifications when they fire. No more vercel.com/changelog/verc… hangelog → https://t.co/YCAXxa5Bcs
本条情报归属 AITOP「产品」核心栏目，重点聚焦北美前沿实验室与硅谷科技巨头。在跨区域产业观察坐标中，该动态直接关联「AI 开发者工具链、Coding Agent 与工程化实践」研究主线，反映出当前技术演进与商业落地的最新风向。涉及核心实体与技术议题包括：MCP/工具、Vercel、智能体、webhook，读者可通过下方标签进入对应专题页查阅历史脉络与关联对比。
信源核验说明：本文原始线索采编自「Guillermo Rauch」（@rauchg），经 AITOP 多维评分管线结构化提炼。
