Why can't I just share the Claude chat link?

A chat link drops the recipient into your conversation history rather than onto the page, and they may need a Claude account to open it at all. Publishing gives you a normal URL that renders the page for anyone.

Does Claude's built-in publish do the same thing?

Claude's own share link works for a same-day demo, but it lives on Anthropic's domain and is tied to the artifact. Pagepost gives you a permanent URL you control, with view counts, revocation, expiry and in-place editing.

Can Claude edit a page it already published?

Yes. Pagepost's MCP connector exposes fetch and update_file, so Claude can load the real source of a page you published earlier, revise it, and write it back to the same URL. Anyone holding the link sees the update.

Do interactive HTML dashboards keep working?

Yes. HTML is served verbatim inside a sandboxed iframe, so scripts, charts and interactivity keep working. Markdown is rendered to styled HTML instead.

Claude MCP connector

Share a Claude artifact as a real link.

No copy-paste, no download-then-upload. Claude builds the page and publishes it for you through our MCP connector — the live link lands right back in the chat, ready to paste anywhere a URL works.

Works for interactive HTML dashboards and Markdown reports alike.

Why sharing the chat link doesn't work

A Claude artifact 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.

1
Add Pagepost as a connector
Open Claude's “Add custom connector” dialog. Set the name to PagePost, paste https://pagepost.app as the URL, and click Save. Then sign in once with Google or Slack — that's the only setup.
2
Ask for an HTML page or Markdown brief
Prompt Claude the way you normally would — a slide deck, an interactive dashboard, a one-page client briefing, a Markdown report. Anything it can write as HTML or MD.
3
Tell it to publish to Pagepost
Say “publish it to Pagepost”. Claude calls the connector and posts the live link right back into the chat. Paste it anywhere a URL works.

Open Claude connectorsName PagePost, URL https://pagepost.app

One sign-in, then it just works

Authenticate the connector once with Google or Slack. After that, every chat where you mention Pagepost can publish without re-asking for permission.

Works with any Claude artifact

HTML artifacts, Markdown reports, single-file dashboards — if Claude can write the file, Pagepost can publish it.

Your links, your dashboard

Everything Claude publishes shows up in your Pagepost dashboard alongside your manual uploads. Rename, revoke, or expire any of them from one place — and fix a typo right on the published page, no re-prompting, same URL.

Using a different assistant? Set it up for ChatGPT, Gemini 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.

Share a Claude artifact as a real link.

Why sharing the chat link doesn't work

Add Pagepost as a connector

Ask for an HTML page or Markdown brief

Tell it to publish to Pagepost

One sign-in, then it just works

Works with any Claude artifact

Your links, your dashboard