OpenAI Adds MCP Events to ChatGPT, Enabling Event-Driven Automated Responses
Summary
- • ChatGPT can now subscribe to external server events and act automatically via MCP Events
- • Feature requires MCP 2.0 (protocol version 2026-07-28); webhook delivery only, no polling
- • Use cases: auto-open PRs from Slack bug reports, auto-implement document review edits
- • Based on draft MCP Events spec; polling and streaming not supported in current integration
Details
MCP Events: ChatGPT subscribes to server events and responds automatically
Users define what to monitor and how ChatGPT should respond; ChatGPT subscribes via the MCP server, supplies a callback URL, receives webhook payloads, and executes the user-defined response — without requiring a new user prompt for each event.
MCP 2.0 required (protocol version 2026-07-28); three new server methods needed
Servers must implement events/list (catalog available events and filter schemas), events/subscribe (create or refresh a subscription), and events/unsubscribe (terminate a subscription) on the same authenticated MCP endpoint as existing tools.
Webhook-only delivery; ChatGPT supplies callback URL and signing secret at subscribe time
At subscribe time ChatGPT provides a callback URL and signing secret; the MCP server sends matching events via HTTPS to that URL. Polling, streaming, and the draft's gap and terminated control notifications are explicitly not supported in this integration.
Server requirements: persistent subscription storage and outbound HTTPS callback access
MCP servers must maintain persistent subscription records (surviving restarts) and have outbound HTTPS access to ChatGPT's callback URLs. Event support is advertised via the capabilities object in the server/discover response.
Automation use cases: Slack bug reports auto-generate PRs; doc review comments auto-implemented
OpenAI's documented examples: (1) Monitor a Slack #product-feedback channel for bug reports, then auto-open draft pull requests with fixes and tests; (2) Watch a document for review comments and automatically implement the requested edits.
Draft spec basis: polling, streaming, and gap/terminated notifications not yet supported
The integration follows the draft MCP Events specification but omits several draft features including polling delivery, streaming, and gap/terminated control notifications. The partial implementation signals the feature will expand as the spec matures and MCP 2.0 adoption grows.
Product Launch = new ChatGPT capability, Tech Info = protocol requirements, Infrastructure = server-side implementation requirements, Insight = documented use cases, Context = specification status and roadmap
What This Means
OpenAI's MCP Events feature upgrades ChatGPT from a purely reactive assistant into a proactive, event-driven agent that can continuously monitor external systems and automatically act when conditions are met — no re-prompting required. Built on MCP 2.0, it enables enterprise automation use cases like bug triage and document review at scale. The webhook-first design is practical for server integrators but requires non-trivial infrastructure (persistent subscriptions, outbound HTTPS). Since this is based on a draft specification with several features still absent, the feature will evolve, but its release marks a clear step toward ChatGPT as an always-on, workflow-integrated AI agent rather than a conversational tool.
Sources
- MCP EventsDevelopers