mcp-tool

MCP Events · ChatGPT extension

Your product updates.
ChatGPT follows up.

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.

FROM UPDATE TO FOLLOW-UPIllustrative demo

THE USER SETS THE TASK

Watch this document for new review comments and prepare the requested edits for my review.

  1. Your product changes

    A reviewer asks for the rollout dates.

  2. Your server delivers the event

    comment.created · Only the selected document

  3. ChatGPT follows the agreed task

    ChatGPT uses the connected document tools to prepare an edit for review.

Example workflow with sample data. No subscription is created and no webhook or external action is sent. Event names and connected tools are defined for each implementation.

An update with a purpose

Start with the follow-up
your users already need.

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.

01

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.

02

Discovery and subscriptions

Scope MCP 2.0 event discovery, event schemas, authorised subscribe and unsubscribe methods, and persistent subscription storage for your server.

03

Verified webhook delivery

Callback verification, signed payloads, destination checks, delivery retries and event IDs that remain stable across retry attempts.

04

A tested subscription lifecycle

Creation, refresh, expiry, restarts, revoked access and stopping delivery. Test filtering, duplicate events and workflows that write data.

What we need to scope it

Bring the event.
We’ll map the path.

  • Your MCP server or API documentation.
  • An event source we are authorised to connect.
  • The account, document, channel or job the user can monitor.
  • The response you want and the tools it needs.
  • A ChatGPT plugin connection and test account for the full lifecycle.

Platform requirements

Built around the documented ChatGPT integration.

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

Before we build.

Is this included in the standard Build?

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.

Can you extend a server we already have?

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.

Does this work in Claude too?

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.

Will ChatGPT automatically act on every product update?

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.

Do you have a fixed price for Events?

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.

What should ChatGPT watch?

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.