ChatGPT · MCP
ChatGPT does the work.
A person signs it off.
Get a sign-off from the person who owns the decision before what ChatGPT drafted is sent, posted or acted on — without copying it anywhere — and keep a record of who said yes. Connect Deliverd once and ChatGPT can put the decision in front of the right person, and go on when they answer.
No card required · Approvals on every plan · No token to paste
The situation
What happens when ChatGPT needs a person today
The answer is right; the decision is nobody's
ChatGPT produces the recommendation and the person reading it is the only check. When the person who should sign off is someone else, the draft goes out as an email and the sign-off is a reply, or nothing.
Copy and paste is the approval workflow
The text moves to a document, the document to an email, the email to whoever is around. By the time it is acted on, nobody can say which version was approved or by whom.
Nothing is on the record
A shared chat shows your prompts and no decision. When the action is questioned, there is no record of who said yes, what they saw, or when.
Setup
Connect ChatGPT
Give ChatGPT a person to ask before it acts on what it wrote — and a real home for the result: a URL, an audience, a version history.
- 1
Turn on developer mode
Settings → Apps → Advanced settings → Developer mode. Custom connectors need a paid ChatGPT plan.
- 2
Add a custom connector with this address
https://deliverd.dev/api/mcp
The connector registers itself and sends you to a screen where you choose the organisation and approve access.
No token is written anywhere. Deliverd implements the MCP authorization spec, so the client registers itself and you approve it in a browser — and removing someone from your organisation cuts their connection off at once, rather than whenever a token happens to expire.
What you get
Once it is connected
Everything below is one call from ChatGPT, over the connection you just made — the ask first, and publishing last.
One call to ask a person
request_approval, request_review or request_information over the connection above. The agent says what it wants to do, why, and what it affects, and the question goes to a named person — not to whoever is at the keyboard.
Decided wherever they are
They approve, correct a figure the agent marked as correctable, reject with a reason or ask the agent a question — on a page built for a phone, from an email link, or from a Slack or Teams card. A colleague can cover while they are away.
The agent carries on
The decision comes back as something the agent can branch on: poll get_approval, wait on a callback URL, or let the SDK block. Approved, it does the action. Rejected, it stops and knows why.
A check before it acts
Before a payment, a deployment or a message to a customer, check_gate declares the action. With no rules a named person decides every one; with rules, the routine cases are settled and the rest go to a person.
A record of who allowed what
Who was asked, what they were shown, what they decided and when — kept as the work happens, and exported as an evidence pack in JSON, CSV or PDF with a digest so an altered copy can be told apart.
And when there is a report, a URL instead of a file
publish_report puts the HTML the agent writes on an address behind your organisation's sign-in, versioned, with comments anchored to the passage they are about. One capability among the rest, over the same connection.
request_approval over the connection above, answered on a page that works on a phone, with the decision back in ChatGPT as soon as it is made. See how approvals work →Questions
ChatGPT and Deliverd.
What do I need to add a custom connector?
Developer mode, under Settings → Apps → Advanced settings. Custom MCP connectors are on the paid ChatGPT plans; this is OpenAI's restriction rather than ours.
Is a token involved?
No. The connector registers itself, sends you to a consent screen where you choose which organisation it may ask and publish in, and receives its own credentials. Consenting to one organisation is not consenting to all of them.
What can ChatGPT do once it is connected?
Ask a named person for approval, a review or information it is missing, check a gate before a consequential action, and keep a task's objective and state across sessions — all over the same connection. It can also publish a report, update it in place, read reader comments and resolve them.
What if I would rather use the API?
Any script or agent that can make an HTTP call can ask a person, check a gate or publish — Python, a Lambda, a GitHub Action. The REST API takes the same requests and the same audiences.
Will readers see your branding?
On the paid plans they see yours: your organisation's name and logo, on your own domain if you have added one, with email sent from your domain once it is verified.
Let ChatGPT act. Know who said it could.
One call to ask a person, answered where they are, and a record of who allowed what — from the tool you already have open.