Vercel Connect adds MCP Events support in public beta for apps and agents

What MCP Events in Vercel Connect does

With the new support, applications and agents can react to events as they happen on an MCP server. Vercel names several example tasks: summarizing new messages, reviewing newly created issues, and responding to document feedback.

Connect takes over much of the plumbing. According to Vercel, it creates subscriptions on the MCP server and renews them automatically as needed. It also verifies the server's webhooks and forwards the events to the developer's application using authenticated delivery.

Subscribing and verifying with the Connect SDK

Developers can subscribe to events through the Connect SDK. Vercel's example imports experimental_subscribe from @vercel/connect/mcp and requests a subscription to the issue.created event on an oauth/issues connection, filtered by a project ID of ABC. The example sets a time to live of 24 hours, which Vercel describes as requesting a 24-hour subscription to issue events.

The example also passes an idempotency key. Vercel's code comments advise using a new key for each subscription and reusing it when retrying the same request. The destination is a path in the app, /hooks, where events will be delivered.

On the receiving side, the SDK provides experimental_verifyMcpEvent. In Vercel's Next.js route example, the handler calls it with the incoming request and the /hooks path to confirm that each delivery came from Connect, then returns an empty response with status 204 to acknowledge receipt.

Both function names carry the experimental_ prefix, in line with the feature's beta status.

Agent tools and eve integration

Vercel says developers can also expose AI SDK event discovery and subscription APIs as agent tools. This uses Connect's MCP Events adapter to manage subscriptions.

In eve, enabling events on an MCP connection gives agents tools to discover the server's events and to use Connect to create, inspect, or stop subscriptions. This lets an agent decide which events it needs and manage its own subscriptions rather than relying on fixed configuration.

What it means for developers

For teams building event-driven agents on MCP servers, the beta offers a managed route for subscriptions, renewal, webhook verification and authenticated delivery, instead of building those pieces themselves. Vercel points developers to the Vercel Connect quickstart for SDK setup and authentication.

Because the feature is in public beta and the SDK functions are marked experimental, details may change. The source does not give pricing or availability terms, so developers should check Vercel's documentation before relying on it in production.