Publish Markdown and HTML to a link — straight from your AI assistant.
The dochost MCP server gives Claude, ChatGPT and Cursor a publish tool. Ask your assistant to share a document and it hands back a clean, public dochost link — no copy-paste, no separate dashboard.
claude mcp add --transport http dochost \ https://dochost.io/api/mcp
/mcp inside Claude Code and approve in the browser.Publish straight from OpenClaw & Hermes
Install the dochost skill once and your agent gets a publish-to-link command. Headless agents authenticate with an API key — created in seconds.
Publish from your Telegram agent — no Claude Code session needed.
openclaw skills install dochost-publishDrop the skill into Hermes — plain HTTP, no MCP wiring.
cp -r dochost-mcp/…/dochost-publish .hermes/skills/Install for your tool
Pick your client, copy one command, authorize once. No SDK, no deploy.
How to add the dochost MCP server to Claude Code, Codex and Cursor
Add the remote server over HTTP, then authorize from inside Claude Code.
claude mcp add --transport http dochost \ https://dochost.io/api/mcp
/mcp in Claude Code and approve in the browser. Add --scope user to use it in every project.Tools your assistant gets
Six tools — publish, then manage and inspect what you published. Ownership and entitlements come from your account, never from tool input.
Returns url, slug, expiresAt.
Returns compact records — slug, url, title, format, views, expiresAt. Never the page body or password.
Also live — get_page, get_account, update_page, delete_page, get_page_content (read a page's source back before editing it) and set_page_options (change visibility, indexing or password without a new link).
Built for the way you already work with AI
The publish step disappears. Your assistant ships the page; you get the link.
Markdown and full HTML
Most publish tools take Markdown only. dochost ships raw HTML too — so AI-generated pages, demos and prototypes render exactly as written.
OAuth, not pasted keys
One-click sign-in over OAuth 2.1. Nothing to copy into a config, nothing to leak in a prompt or a shared machine.
Your plan, your rules
Output mirrors the website: free links last 7 days; Pro unlocks permanent links, passwords, custom slugs and no branding.
Private by default
Pages are unlisted unless you ask to make them public. They never land on Explore by accident.
Rate-limited and audited
20 publishes a minute, 300 an hour, per account. Every call is logged for safety — document bodies never are.
One dashboard for everything
Pages published from chat show up next to the ones you made on the web — same views, likes, expiry and analytics.
From "share this" to a live URL
A real exchange once dochost is connected. The tool call and result are inline in the chat.
MCP, answered
The Model Context Protocol questions people ask before connecting dochost.
What is the dochost MCP server?
It is a hosted Model Context Protocol server at dochost.io/api/mcp. Connect it to an AI assistant and the assistant gains a publish tool that turns Markdown or HTML into a live, shareable dochost link — no copy-paste between chat and a browser.
Which AI clients can connect?
Any MCP client over streamable HTTP — including Claude, ChatGPT, Cursor, Claude Code, Codex, Gemini CLI, VS Code and Windsurf. One-click clients only need the server URL; config-file clients add it to their mcp.json; Gemini CLI installs it as an extension.
Do I need an API key?
No. Connecting uses OAuth — you sign in once and approve access, and the assistant publishes as you. A manual API key is available for headless and CLI clients that cannot run the browser sign-in flow.
Is my published content private?
Pages publish unlisted by default and are not added to Explore unless you set public to true. Pro accounts can also password-protect a page. Your document body is never sent to analytics.
Does it respect my plan?
Yes. Output follows your account exactly like the website: free links last 7 days (3 days if published as private), while Pro and Lifetime unlock permanent links, passwords, custom slugs and no branding. The tool can't grant a feature your plan doesn't include.
How is this different from the REST API?
The REST API is for code you write. The MCP server is for assistants you talk to — it advertises the publish and list_my_pages tools so an AI client can discover and call them on its own, with OAuth handling identity. Same publishing engine underneath.
Agents publish in bulk.
Pro keeps every link alive.
- Permanent links — nothing your agent ships ever 404s
- 200 live pages, 10 MB each
- Custom slugs, password protection, no branding
Give your assistant a publish button
Connect dochost once and turn any Markdown or HTML your AI writes into a shareable link — from inside the chat.
Connect dochost