Turn Gemini CLI output into a link
Add MintPage to ~/.gemini/settings.json and Gemini CLI can turn any plan, report or summary into a live link with one publish_page tool call.
Gemini CLI is good at producing long answers in a terminal: a plan, a code review, a migration checklist, a summary of a repository. The terminal is where that output goes to die. MintPage gives Gemini CLI a publish_page tool, so the same output becomes a URL you can paste into a chat, a pull request or an email.
Connect Gemini CLI
Add the server to your user settings file (~/.gemini/settings.json), or to .gemini/settings.json inside a project if only that project should have it:
{
"mcpServers": {
"mintpage": {
"httpUrl": "https://mintpage.ai/mcp",
"headers": { "Authorization": "Bearer mp_your_key" }
}
}
}
The same thing from the command line:
gemini mcp add --transport http mintpage https://mintpage.ai/mcp
Restart Gemini CLI, check with /mcp that mintpage is listed with its tools, then ask: "publish this as a page and give me the link." Gemini calls publish_page and returns a URL.
Leave out the headers block to use guest mode: no key, no account, pages last 24 hours. A free key from /start makes them last 7 days and unlocks stats; Pro ($5/month or $39/year) makes them permanent with custom slugs.
MintPage is a plain streamable-HTTP MCP server with no OAuth, which is why httpUrl plus a bearer header is the whole configuration. If you would rather not keep the key in a settings file, the key can travel in the path instead: "httpUrl": "https://mintpage.ai/mcp/mp_your_key". Either way, keep that file out of version control.
Good uses
- Plan review. Ask Gemini for an implementation plan, publish it, and get a teammate's sign-off before anything touches the repo.
- Repository summaries. "Explain how this codebase is organized, then publish it" gives new contributors a link instead of a wall of terminal text.
- Living status pages. Publish once, then
update_pageat the same URL after each run; the link in your PR description never goes stale.
Example call
{"name":"publish_page","arguments":{"title":"Search service — migration checklist","content":"# Checklist\n\n- [ ] Dual-write to the new index\n- [ ] Backfill\n- [ ] Flip reads\n- [ ] Remove old index","theme":"ink","byline":"Drafted by Gemini CLI"}}
What stays safe
Pages are public to anyone with the link, and the tool description tells the agent never to publish secrets. HTML is sanitized (no scripts, forms or iframes) and served with a strict Content-Security-Policy. Delete a page any time with delete_page.
FAQ
Does this also work in Gemini Code Assist in VS Code? The agent mode of Gemini Code Assist reads the same settings.json MCP configuration, so one entry covers both.
Can Gemini update a page instead of making a new one? Yes: update_page keeps the URL and replaces the content, which is how a living status page works.
Is there a size limit? Guest pages up to 250 KB, free keys 1 MB, Pro 2 MB. Markdown and sanitized HTML are both accepted.
Which tools does the server expose? publish_page, update_page, list_pages, delete_page, get_page_stats, get_account and rotate_api_key. Run /mcp in Gemini CLI to see them with their descriptions.
Try it in one line
No account needed. Pages last 24 hours as a guest, 7 days with a free key, forever on Pro.
claude mcp add --transport http mintpage https://mintpage.ai/mcp