Share a DeepSeek page as a real link.
DeepSeek is very good at writing a dense, self-contained HTML page cheaply. Pagepost turns whatever it writes into a live URL you can send to anyone.
Works for interactive HTML dashboards and Markdown reports alike.
Before you start
DeepSeek's own chat app at chat.deepseek.com has no connector or MCP settings — there is nothing to paste a URL into. What DeepSeek does have is an API with tool calling, so the way to use Pagepost with it is to run a DeepSeek model inside a client that speaks MCP. That's the setup below, and it takes about two minutes.
Why sharing the chat link doesn't work
A DeepSeek 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.
- 1
Pick an MCP-capable client
Anything that speaks MCP and lets you choose the model works — Cherry Studio, LibreChat, Cline, and Continue are common picks. Point it at DeepSeek with your DeepSeek API key and choose a DeepSeek model. - 2
Add Pagepost as an MCP server
In the client's MCP settings, add a remote server with the streamable-HTTP transport and the URLhttps://pagepost.app/api/mcp. Clients that support OAuth discovery will prompt you to sign in with Google or Slack; the token is cached after that. - 3
Ask DeepSeek to publish
Have it write a dashboard, brief, or report, then say “publish it to Pagepost”. DeepSeek calls the connector and returns the live URL.
If your client has no OAuth support
A few MCP clients only accept a static header rather than running the OAuth flow. Those can't connect to Pagepost yet — we issue tokens through OAuth only, so there's no long-lived key to paste. Pick a client with OAuth discovery, or upload the file directly and skip the connector.
Same connector, any client
Pagepost speaks standard MCP, so the server URL above is the same one Claude, ChatGPT, and Gemini use. Nothing is DeepSeek-specific.
Load a page back and revise it
DeepSeek can pull down a page you published earlier, edit the real source, and write it back to the same URL — the link you already shared just updates.
Your links, your dashboard
Everything DeepSeek publishes lands in your Pagepost dashboard next to your manual uploads and anything another assistant published. Rename, revoke, or expire any of them from one place.
Using a different assistant? Set it up for Claude, ChatGPT or Gemini. 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.