ChatGPT · MCP
ChatGPT wrote something good.
Don't paste it into an email.
The analysis is right, the structure is right, and then it is copied into a document and loses all of it. Connect ChatGPT once and it can publish to a real address instead.
No card required · Unlimited viewers · Secure by default
The situation
What happens to ChatGPT's output today
Copy and paste destroys the work
Tables collapse, charts become screenshots, formatting resets to whatever the email client thinks is best. What arrives is visibly worse than what you were looking at.
A shared chat is not a deliverable
It shows your prompts, it has no version history, and it carries your name rather than your organisation's. It is a transcript, not a report.
Nobody knows if it is current
There is no address to return to, so the answer to “is this the latest?” is always another message to you.
Setup
Connect ChatGPT
Give ChatGPT's output a real home: a persistent URL, an audience, and 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 what happens to a report after ChatGPT publishes it.
A URL instead of a file
The report lands on an address you can send. It stays put, so a link you shared last month still opens the report — not a stale copy of it.
Behind your own sign-in
Readers authenticate with the identity your organisation already uses, including SAML single sign-on. Nobody gets a password to remember or a file to lose.
You choose who, in plain English
“Finance team”, “Sarah Jones”, “everyone”. Ambiguous phrases come back as a list to pick from rather than a guess, so a board pack cannot land in the wrong inbox.
Every version kept
Publishing again updates the same URL and keeps what was there before. You can see what changed, and roll back if the new one is wrong.
Comments on the passage, not the page
A reader selects a sentence and comments on it. Your agent can read those threads, fix what they point at, and mark them resolved.
A record of who opened it
Views, versions, access changes and share links are all written to an audit trail you can export.
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 can publish to, and receives its own credentials. Consenting to one organisation is not consenting to all of them.
What if I would rather use the API?
Any script or agent that can make an HTTP call can publish — Python, a Lambda, a GitHub Action. The REST API takes the same HTML and the same audience.
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.
Stop sending ChatGPT’s output around as files.
Publish it to an address instead, and let the people who need it open it with the sign-in they already have.