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 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):

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.

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:

npm ci --ignore-scripts
node server/index.js

Or run it in Docker:

docker build -t dochost-mcp .
docker run --rm -i dochost-mcp

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?

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.

publish

Publish Markdown or HTML as a hosted page and get a shareable URL.

Returns url, slug, expiresAt, and an editToken.

Example: "Publish my Q3 report as a private page with a password." → dochost.co/d/q3-report (password-gated, 7-day link on free).

update_page

Replace the content of a page in place. The URL, view/like counts and expiry all survive — only body, format and title change.

Prefer this over publishing again whenever you are revising something already published — a second publish mints a second link and strands the one the reader already has. Resending identical content is a no-op.

list_my_pages

List the pages you have published, newest first. Paginated (limit, offset); returns compact records without page bodies.

get_page

Look up one page by slug: title, format, status, view/like counts, expiry, and whether it is password-protected. Never returns the body or the password.

get_account

Your plan, page-quota usage and entitlement flags (size cap, custom slug, password, branding). Worth calling before publish so the assistant knows your limits up front instead of failing on them.

delete_page

Permanently delete a page by slug. The link stops working immediately and the slug is freed. Deleting an already-deleted page is a safe no-op.

Notes

• Ownership and entitlements come from your authenticated account, never from tool input.
• Published pages live on dochost.co, a separate cookieless content origin — never on the app origin dochost.io. That is what lets dochost serve author HTML under a hardened policy without it touching your session. dochost.io/d/… permanently redirects to dochost.co/d/…, so old links keep working.
• 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.