Gemini CLI · MCP
Gemini wrote it.
Now give it to someone.
Gemini CLI is quick at turning a folder of data into a report or a dashboard as one HTML file. What it cannot do on its own is put that file in front of the people who asked for it. Add the MCP server and it can.
No card required · Unlimited viewers · Secure by default
The situation
What happens to Gemini CLI's output today
It ends as a file on disk
The session finishes with report.html in the working directory. Getting it to the people who asked means email, a shared drive, or a hosting project.
A file is a copy the moment it leaves
You send it. It gets forwarded. When Gemini rebuilds it with the new numbers, the people holding the old one never find out.
Hosting it properly is a project
A domain, an auth layer, permissions and a way to update in place — for something that might be thrown away on Friday. So it stays on localhost.
Setup
Connect Gemini CLI
One command in the terminal, then Gemini can publish what it writes.
gemini mcp add --transport http deliverd https://deliverd.dev/api/mcp
- 1.
Add the server
gemini mcp add --transport http deliverd https://deliverd.dev/api/mcp
- 2.
Approve it
/mcp auth deliverd
Inside Gemini, if it has not already opened a browser for you.
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 Gemini CLI 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
Gemini CLI and Deliverd.
Do I need a token?
No. Gemini CLI supports OAuth for remote MCP servers: the first connection is refused, Gemini discovers the sign-in, opens a browser, and you approve it. Nothing is pasted into a config file.
What if the browser does not open?
Run /mcp auth deliverd inside Gemini. The approval needs a machine that can open a browser and receive a redirect on localhost, so a headless server or a remote SSH session is the one place this does not work — use the CLI with a token there instead.
Where is the server stored?
In Gemini's settings.json — your user settings by default, or the project's .gemini/settings.json with --scope project. The entry holds only the address.
What can Gemini do once it is connected?
Publish a report, update one in place, rename it, file it into a workspace, search what exists, read reader comments and resolve them, and check which recurring reports are waiting on it.
Stop sending Gemini CLI’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.