The event and the useful response
Choose the product change worth monitoring, the resource filters and the task the user wants ChatGPT to perform. Confirm which connected tools the response needs.
MCP Events · ChatGPT extension
Let users monitor a document, feedback channel or job in your product, and choose what ChatGPT should do when something changes.
We scope event subscriptions, webhook delivery and the tools needed for the response. Quoted after scoping. Your workflow. Your code.
A separately scoped extension. Not included in the $4,900 Build or its ten-business-day timeline.
Watch this document for new review comments and prepare the requested edits for my review.
A reviewer asks for the rollout dates.
comment.created · Only the selected document
ChatGPT uses the connected document tools to prepare an edit for review.
An update with a purpose
Document feedback becomes a proposed edit. A bug report becomes an investigation. A failed job becomes a useful summary. Choose one event and one response before expanding the workflow.
Choose the product change worth monitoring, the resource filters and the task the user wants ChatGPT to perform. Confirm which connected tools the response needs.
Scope MCP 2.0 event discovery, event schemas, authorised subscribe and unsubscribe methods, and persistent subscription storage for your server.
Callback verification, signed payloads, destination checks, delivery retries and event IDs that remain stable across retry attempts.
Creation, refresh, expiry, restarts, revoked access and stopping delivery. Test filtering, duplicate events and workflows that write data.
What we need to scope it
Platform requirements
OpenAI specifies MCP 2.0, protocol version 2026-07-28, persistent subscriptions and webhook delivery with callback verification.
We confirm your account access, protocol migration and target workflow at scoping. The draft event specification and platform behaviour can change.
OpenAI’s MCP Events documentation ↗Scope and expectations
No. The $4,900 Build covers the agreed tools and submission work. MCP Events adds subscriptions, storage and outbound delivery. We quote the event sources, delivery behaviour, platform testing and maintenance separately, with a written price and timeline before implementation.
Yes, after checking the server, authentication, source events and hosting. We confirm the MCP 2.0 changes and the selected ChatGPT workflow before proposing the implementation. A protocol upgrade may be part of the agreed scope.
This offering follows OpenAI’s documented MCP Events integration for ChatGPT. Claude support is not assumed. We check each requested client separately before including it in a quote.
The user chooses an event, its filters and what ChatGPT should do. Only matching events should be delivered for that subscription. Actions also depend on the connected tools, permissions and platform controls. We scope and test the workflow, including any review or approval steps.
We quote after scoping because the event source, persistence, replay needs and downstream actions differ by product. Send your server URL or API docs and one example of an update you want a user to monitor. The Events project has its own scope and delivery target.
One event. One useful response.
Send your product URL and an example workflow. We’ll confirm feasibility and propose the scope, price and delivery target. Invoiced by FINAL MASTER LLC.