Vercel adds event subscriptions for AI agents in Connect public beta

Vercel is offering a way to feed new messages, issues and document feedback into agent workflows. On October 15, 2026, it opened MCP Events in Vercel Connect in public beta. The release supplies the subscription and delivery machinery: apps and agents can receive events from compatible MCP servers, while Connect handles renewal and authenticated forwarding.

Vercel suggests using the feature to build agents that summarize new messages, review newly created issues or respond to document feedback. The feature connects an event source to an application through webhooks—notifications a server sends when an event occurs.

Connect manages the subscription and delivery

Connect creates the subscription on the compatible MCP server and renews it automatically as needed. That places subscription maintenance in Connect rather than making the application handle each renewal.

Delivery has two verification steps. Connect verifies the server’s webhooks, then forwards the events to the application using authenticated delivery. At the receiving end, Vercel instructs developers to use its SDK to verify that the incoming request came from Connect before acknowledging receipt.

A subscription request, field by field

The Connect SDK exposes experimental_subscribe through the @vercel/connect/mcp package. Vercel’s SDK example requests an issue.created subscription through oauth/issues, showing how to route a particular event to an application endpoint.

• Event and project: the request names issue.created and passes project_id: 'ABC' in its arguments. It also sets the token subject type to app.
• Destination and duration: events go to /hooks, and ttlMs requests a 24-hour subscription. That duration belongs to the example, not a stated service-wide limit.
• Request identity: Vercel instructs developers to use a new idempotency key for each subscription and reuse that key when retrying the same request.

The receiving example is a Next.js route that accepts a POST request at /hooks. It waits for experimental_verifyMcpEvent to verify the request against that path, then returns an empty response with status 204.

Agents can manage subscriptions through tools

Developers do not have to keep subscription management solely in application code. Vercel says its MCP Events adapter can expose AI SDK event discovery and subscription APIs as agent tools.

In eve, enabling events on an MCP connection gives agents tools to discover the server’s events and use Connect to create, inspect or stop subscriptions.