MCP Events support in Vercel Connect is now in public beta

MCP Events lets an agent be notified when something changes in a connected service instead of repeatedly asking. MCP, the Model Context Protocol, is the standard many tools use to expose data and actions to AI agents. With this public beta, Vercel Connect can subscribe an app or agent to events from MCP servers that support them, such as a new message, a newly created issue or feedback on a document, and pass each one to the application so an agent can summarize, review or respond (vercel.com).

Connect sits in the middle of that exchange. It registers the subscription with the MCP server, renews it automatically, verifies the webhooks the server sends, and forwards each event to a route in the developer's app with its own authentication. The app, in turn, uses the Connect SDK to confirm a delivery really came from Connect before acknowledging it. Subscriptions can be time-limited, as in the changelog's 24-hour example for new issues, and agents built with the AI SDK or eve can be given tools to discover a server's events and to create, inspect or stop subscriptions themselves.

Several limits shape how far this can be relied on. Vercel's documentation says Connect implements a draft MCP Events specification, only servers that offer webhook events can be used, and the SDK functions carry an experimental prefix. Connect forwards deliveries as they arrive, with no stored outbox, redelivery or replay, so if the receiving app is down, recovery depends on the MCP server's own retry window; deduplication and processing remain the application's job. Each forwarded delivery is billed as a Connect trigger.