Dochost
dochost MCP server
Publish Markdown or HTML to a clean, shareable link — straight from your AI
assistant. The dochost MCP server gives Claude, ChatGPT, Cursor and any other MCP
client a publish tool: ask your assistant to share a document and it hands back
a public dochost link. No copy-paste, no separate dashboard.
- 🌐 Website: https://dochost.io
- 🔌 MCP server: https://dochost.io/mcp
- 🛰️ Endpoint:
https://dochost.io/api/mcp(Streamable HTTP, OAuth) - 🔑 Auth: OAuth sign-in — no API keys
Why
Your LLM produced a report, a README, an HTML artifact. Sending it shouldn't mean
a screenshot or a raw .md blob. dochost turns that output into a normal web page
at its own URL, in one tool call. Markdown and HTML are rendered live.
Quick start
Claude Code (one line):
claude mcp add --transport http dochost https://dochost.io/api/mcp
Then run /mcp inside Claude Code and approve in the browser. Add --scope user
to use it in every project.
Claude Desktop / Cursor / VS Code / Windsurf — add a remote HTTP server:
{
"mcpServers": {
"dochost": {
"type": "http",
"url": "https://dochost.io/api/mcp"
}
}
}
You authorize once via OAuth in the browser; the assistant then publishes as you, and output follows your dochost plan's entitlements.
Which auth method?
| Client | Recommended auth | Why |
|---|---|---|
| OpenClaw, Hermes | API key | Headless agents (e.g. a Telegram orchestrator). A static Bearer key works with the plain-HTTP skill and any MCP runner, with no browser step per session. |
| Claude, Cursor, ChatGPT, VS Code, Windsurf, and all other MCP clients | OAuth | One browser approval, nothing long-lived stored in config; the assistant publishes as you. |
Keep the API key like any secret: store it as an environment variable / host secret (never commit it), and revoke or rotate it from Settings → API keys if it leaks.
Agents (OpenClaw, Hermes) — API key
OpenClaw and Hermes are headless, so they authenticate with an API key. Create
one at dochost.io → Settings → API keys, export it as
DOCHOST_API_KEY, and either:
- Install the skill — a self-contained
publishskill that works on any agent that can make an HTTP request:skills/dochost-publish/. - Wire the MCP — point the agent at
https://dochost.io/api/mcpwith the key as a Bearer header:examples/mcporter.config.json.
Per-host install guides:
- OpenClaw →
clients/openclaw.md - Hermes →
clients/hermes.md
One-shot from a shell: examples/publish.sh.
Tools
publish
Publish Markdown or HTML as a hosted page and get a shareable URL.
| Parameter | Type | Notes |
|---|---|---|
body | string (required) | The Markdown or HTML content to publish. |
format | "markdown" | "html" | Auto-detected when omitted. |
public | boolean | List on Explore. Defaults to false (unlisted). |
customSlug | string · Pro | Choose the link path instead of a random slug. |
password | string · Pro | Gate the page behind a password. |
noBranding | boolean · Pro | Hide the dochost footer badge. |
Returns url, slug, expiresAt, and an editToken.
Example: "Publish my Q3 report as a private page with a password." →
dochost.io/d/q3-report(password-gated, 7-day link on free).
list_my_pages
List the pages you have published, newest first (paginated).
Notes
- Ownership and entitlements come from your authenticated account, never from tool input.
- Free links last 7 days; permanent links, password, custom slug, custom subdomain and branding removal are on the paid plans — see dochost.io.
Links
- Homepage — https://dochost.io
- MCP setup & docs — https://dochost.io/mcp
License
MIT — see LICENSE.
Server Config
{
"mcpServers": {
"dochost": {
"type": "http",
"url": "https://dochost.io/api/mcp"
}
}
}