How ChatGPT MCP Events Work (It's Webhooks)
Blog post from Svix
MCP Events is a draft extension to the Model Context Protocol that enables AI clients to subscribe to system events, such as document comments, pull requests, or incidents, and respond through authorized MCP tools. Servers expose available events through an event catalog and manage subscriptions using list, subscribe, and unsubscribe methods, with polling, streaming, or webhook delivery options; ChatGPT currently supports webhook delivery only for compatible plugin-based MCP servers. Events use Standard Webhooks-style signed payloads, deduplication IDs, cursors, retries, expiration and refresh mechanisms, while clients provide signing secrets that can be rotated without interruption. Implementations must verify callback endpoints, protect against SSRF, prompt injection, unauthorized access, and event loops, and should use durable event logs to support reliable replay after outages or subscription gaps. Svix offers dedicated routes and infrastructure for ChatGPT MCP Events, handling endpoint verification, signing, retries, secret rotation, expiration, and webhook delivery while leaving MCP servers responsible for authorization, event definitions, channel mapping, and translating errors into the JSON-RPC responses ChatGPT expects.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| MCP | 37 | 11,696 | 1,199 | 231 | +10% |
| Real-time | 2 | 4,128 | 1,085 | 233 | -15% |
| Secrets Management | 1 | 3,057 | 597 | 151 | +49% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.