Build the docs, say "publish", get a live URL. Nothing to install: connect Claude Code, claude.ai or Claude Desktop to the hosted MCP server, or run it locally to publish straight from your build folder. Custom domain with TLS, redeploys that clean up after themselves, password-protected previews.
acme-docs.https://thin.host/s/acme-docs/ — 277 pages, 400 assets, uploaded in 5 requests. This build uses baseUrl /, so it will render fully once you map a custom domain; want me to set up docs.acme.com?https://thin.host/claim/…Everything a docs site needs, exposed as two MCP tools and three REST endpoints — so the agent that wrote the docs can ship them.
Point publish_website at build/. Hundreds of files are batched across requests automatically; you get back a URL.
Every Docusaurus build renames its hashed chunks. sync=true deletes what the new build no longer ships instead of hoarding it forever.
Map docs.yourco.com from the dashboard or let the agent provision it. Sitemap, robots.txt and canonical tags are generated for you.
Protect the whole site or single pages — internal docs, pre-launch previews, partner-only sections. Survives every redeploy.
The build's 404.html becomes the site's not-found page, served with a real 404 status so search engines get the message.
A drop-in Claude skill encodes the whole flow — baseUrl decision, publish, sync, domain — so "deploy my docs" just works.
Static hosts that only upsert files quietly accumulate every previous build. thin.host treats a synced upload as the whole site: new files land first, pages switch over, then everything the manifest doesn't list is removed.
Docusaurus bakes baseUrl into every asset path, so there is one decision to make. The publish tools detect Docusaurus, read the build's baseUrl, and warn you when it won't resolve where the site is served — instead of you staring at an unstyled page.
| Where readers look | baseUrl |
|---|---|
Custom domain docs.acme.com | / |
Preview thin.host/s/acme-docs/ | /s/acme-docs/ |
Pick how Claude reaches thin.host. Same tools either way; the only difference is whether the server can read your build folder or receives it as a zip.
Points Claude Code at https://thin.host/mcp. A browser tab asks you to allow the connection; or skip OAuth and pass a dashboard API key as a header.
Runs the same server on your machine, so publish_website reads build/ straight from disk and batches the upload itself. No zipping, and large builds stream in several requests.
claude.ai and Claude Desktop connect to the hosted server through their Connectors settings and sign you in with OAuth. Give Claude a public link to the zipped build and it publishes from there.
https://thin.host/mcp, then Allow on the thin.host consent pageTeaches Claude the baseUrl decision, the sync rule, and which publish path fits the connection, so you never have to.
"Build the docs and publish them to thin.host as acme-docs." Then "map docs.acme.com". Then, forever after, "redeploy the docs".
The tools work on any static build folder. Docusaurus gets the baseUrl detection because it is the one that needs it; everything else just uploads. Hand-written HTML sites use the same tools — without sync, to keep editing single pages. Use it from claude.ai or Claude Desktop too: add https://thin.host/mcp as a custom connector and sign in.
Hosted, unless your build is large or you redeploy every few minutes. Hosted means nothing to install and works from claude.ai and Claude Desktop too, but the build travels as a zip (30MB per upload). The local server reads the build folder directly and streams big sites in batches. You can switch any time; both talk to the same account.
They host Docusaurus fine — for a human with a CI pipeline and a hosting dashboard. thin.host is for the case where an agent produced the docs and should also ship them: publish, redeploy, domain, and access control are tool calls with structured errors, not YAML and web forms.
A real docs site with an API reference is a few hundred files and tens of megabytes; that uploads in a handful of requests. The per-site cap is 150MB and single files over about 15MB do not fit a request — compress videos or host them elsewhere.
Yes. One curl: zip the build folder and POST it to /v1/websites/:slug/archive — files the new build dropped are pruned automatically. The recipe has the command.
Anything Docusaurus writes into build/ is served as-is — versioned docs, locales, search indexes, the OpenAPI plugin's generated pages. Nested index.html files map to clean paths (docs/1.0/intro/index.html → /docs/1.0/intro).
Hosting on a thin.host URL is free. Custom domains are billed per domain — see billing.