zyli5313/dochost-mcp

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 six tools — publish, update_page, list_my_pages, get_page,
get_account, delete_page — so your assistant can hand back a public
dochost link and then keep maintaining it. 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):
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:
You authorize once via OAuth in the browser; the assistant then publishes **as
you**, and output follows your dochost plan's entitlements.
Stdio / Docker bridge
For clients or directory evaluators that need a local stdio process, this
repository includes a bridge to the same hosted MCP endpoint:
Or run it in Docker:
Node.js 22 or newer is required. The bridge forwards the live tools and schemas;
it is not a self-hosted copy of the dochost application. Initialization and
tool discovery are public. Interactive clients can use OAuth; headless tool
execution needs an existing DOCHOST_API_KEY runtime secret (Docker:
docker run --rm -i -e DOCHOST_API_KEY dochost-mcp).
Maintainers: see Glama claim, build and release instructions.
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 publish skill 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/mcp with 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
Six tools. publish creates; the rest let the assistant keep working with what it
already published, instead of stranding a link every time you revise something.