# MCP Events

Published 29 October 2026 · Event Gateway

Receive MCP events with a new source type, and turn webhooks into MCP events with an open-source bridge

Event Gateway now supports [MCP Events](/webhooks/guides/what-are-mcp-events), the draft MCP extension (SEP-3415) that lets an agent subscribe to events instead of waiting for a prompt, in two ways.

**Turn webhooks into MCP events.** The open-source [MCP Events bridge](https://github.com/hookdeck/mcp-events-bridge) is an MCP server built on Event Gateway. It turns webhooks from Resend, GitHub, Stripe and other services, or your own, into MCP events. Event Gateway verifies each webhook with its source type, turns it into an MCP event, and delivers it to each subscriber, signed with that subscriber's secret on every attempt. The bridge takes subscriptions over MCP and sets each one up as an Event Gateway connection. ChatGPT and other MCP Events clients subscribe, and Claude Code gets the same events through a plugin that polls the bridge.

**Receive MCP events in your own agent runtime.** The new `MCP_EVENTS` source type puts Event Gateway in front of an agent that subscribes to MCP events. It answers each subscription's verification challenge at the edge, within a 5-minute timestamp window, and never delivers the challenge as an event. It verifies the Standard Webhooks signature on every delivery and answers `401` to a bad one, so the MCP server sees the failure. See [Use Event Gateway as a forward proxy for MCP Events](/docs/guides/how-to-use-event-gateway-as-mcp-events-forward-proxy).

**Limits.** SEP-3415 is a draft, so details may change. An `MCP_EVENTS` source holds one `whsec_` secret, with no rotation yet. Payloads over 2.5 MiB skip edge verification.