Which transport does the Gemini connector need?

Streamable HTTP. Use the httpUrl field in settings.json rather than url, which is reserved for SSE transports. Pagepost serves streamable HTTP at https://pagepost.app/api/mcp.

Do I need a client ID to connect?

No. Set authProviderType to dynamic_discovery and Gemini registers itself with our OAuth server automatically, so there is no client ID or secret to paste.

Can Gemini edit a page it already published?

Yes. It can fetch the real source of a page you published earlier, revise it, and write it back to the same URL.

Gemini MCP connector

Share a Gemini page as a real link.

Q: Can I add a custom MCP connector in the Gemini app?

Not yet. Google has not shipped custom MCP connectors in the consumer Gemini app at gemini.google.com. Custom MCP servers work in Gemini CLI, and in Gemini Enterprise and Gemini Spark where a workspace admin adds the server.

Point Gemini at Pagepost as a custom MCP server and it publishes the HTML or Markdown it just wrote as a live URL — no download, no re-upload.

Works for interactive HTML dashboards and Markdown reports alike.

Before you start

Google hasn't shipped custom MCP connectors in the consumer Gemini app yet — there's no “add a connector” button at gemini.google.com. Custom MCP servers work in Gemini CLI (the setup below), and in Gemini Enterprise and Gemini Spark, where a workspace admin adds the server. If you're in the consumer app, uploading the file directly is the quickest path today.

Why sharing the chat link doesn't work

A Gemini response lives inside your conversation. Send the chat link and your colleague lands in your message history and has to hunt for the thing you meant them to see — if they can open it at all. Download the file instead and you get an .html file that opens as a blank page or raw source for anyone without the right setup.

→ Publishing it gives you a normal URL. It opens the rendered page, on any device, for anyone you send it to.

Set it up in Gemini CLI

1
Add the server
Run this in your terminal:
```
gemini mcp add --transport http pagepost
  https://pagepost.app/api/mcp
```
It registers Pagepost as a streamable-HTTP MCP server in your Gemini CLI settings.
2
Authorize once
Start gemini and run /mcp auth pagepost. The CLI discovers our OAuth endpoints automatically and opens a browser — sign in with Google or Slack. The token is cached, so this is a one-time step.
3
Ask it to publish
Have Gemini write a dashboard, brief, or report, then say “publish it to Pagepost”. It calls the connector and hands back the live URL.

Prefer to edit settings.json?

The CLI command above writes this. dynamic_discovery is what lets Gemini register itself with our OAuth server — no client ID to paste.

{
  "mcpServers": {
    "pagepost": {
      "httpUrl": "https://pagepost.app/api/mcp",
      "authProviderType": "dynamic_discovery",
      "oauth": { "enabled": true }
    }
  }
}

Gemini Enterprise / Spark

An admin adds Pagepost under the custom MCP server connection, using https://pagepost.app/api/mcp. The connector only supports the streamable-HTTP transport, which is what we serve, and the endpoint is public — no Private Service Connect needed.

One sign-in, then it just works

Authorize once with Google or Slack. After that every Gemini session can publish without re-asking for permission.

Load a page back and revise it

Gemini can pull down a page you published earlier, edit the real source, and write it back to the same URL — so the link you already shared just updates.

Your links, your dashboard

Everything Gemini publishes lands in your Pagepost dashboard next to your manual uploads and anything Claude or ChatGPT published. Rename, revoke, or expire any of them from one place.

Using a different assistant? Set it up for Claude, ChatGPT or DeepSeek. Using something we haven't listed? Any MCP client works — it's the same connector. Not using an assistant at all? Upload directly or use it from Slack.