MCP Events Support in Vercel Connect Reaches Public Beta.

Vercel has put MCP Events support in Vercel Connect into public beta, giving apps and agents a way to subscribe to webhook events from compatible MCP servers without wiring up subscription management by hand. The change comes from Vercel's changelog and sits inside Vercel Connect, the product Vercel uses to bridge agents and external services.

The practical problem this solves is upkeep. Webhook subscriptions on MCP servers need to be created, renewed before they expire, and verified on receipt so you know the payload actually came from the server you subscribed to. Connect now does all three automatically: it creates the subscription, renews it as needed, verifies the server's webhook signature, and forwards the event to your application with authenticated delivery.

For builders, this turns a class of agent you'd normally have to poll for into one that reacts. Vercel's own examples are a message summariser, an issue reviewer, and an agent that responds to document feedback as it comes in. Instead of checking an MCP server every few minutes for new issues or comments, your agent gets told the moment something changes.

The work happens through two new functions in the Connect SDK, both still marked experimental:

This follows Vercel's broader pattern of building out Connect as the agent-facing layer of the platform, alongside moves like enterprise-managed authorization for Connect. Event subscriptions fill a gap that authorization alone didn't cover: knowing who can access a server is different from knowing when something on that server has changed.

What is MCP Events support in Vercel Connect? It's a public beta feature in Vercel Connect that lets apps and agents subscribe to webhook events from MCP servers that support them. Connect handles creating and renewing the subscription and verifies each incoming webhook before forwarding it to your application.

Which Vercel plan includes MCP Events support? Vercel's changelog entry doesn't specify plan restrictions or pricing for the beta, so check the Connect product page or your account for current availability.

How does this compare with polling an MCP server for updates? Polling means repeatedly checking a server for changes and handling your own subscription renewal and verification logic. MCP Events support pushes changes to your application as they happen and handles renewal and webhook verification inside Connect, removing that maintenance work from your code.