dochost

io.github.zyli5313Published by GitHub account zyli5313v1.1.0Updated Oct 24, 2026

Publish, list, update and delete shareable Markdown/HTML pages from your AI assistant.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

Publishes Markdown or HTML from an AI assistant as a hosted, shareable web link, then lets the assistant list, read, update, re-option and delete those pages.

What you can do
  • Publish Markdown or HTML as a hosted page and get a shareable URL, with optional public listing, custom slug, password or branding removal
  • List your published pages, newest first, in compact paginated records
  • Inspect a single page's metadata (title, format, status, views, likes, expiry, password protection) and read back its current Markdown or HTML source
  • Replace a page's body in place, keeping the same URL, view counts and expiry
  • Change visibility, search-engine indexing or password without republishing
  • Delete a page permanently, freeing its slug
When to use it
Useful when the assistant produces a report, README, quiz, calculator or HTML artifact that should be shared as a normal web page instead of a screenshot or raw file, and when that link needs to be revised or maintained over time rather than re-created.
Requirements
Remote Streamable HTTP endpoint at dochost.io with OAuth sign-in in the browser; no API keys needed for interactive clients. Headless or stdio/Docker bridge use needs Node.js 22 or newer and a DOCHOST_API_KEY runtime secret. A dochost account determines plan limits.
Before you install
Published pages are public web content on a separate content origin; HTML JavaScript runs in a sandbox. Free links expire after seven days, and permanent links, passwords, custom slugs, subdomains and branding removal require a paid plan. update_page replaces the body wholesale, so read current content first. delete_page is permanent and breaks the link immediately. Treat DOCHOST_API_KEY as a secret and rotate it if leaked.

Installation

In SourceWeft

  1. Open dochost in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.zyli5313%2Fdochost-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "dochost": {
      "type": "http",
      "url": "https://dochost.io/api/mcp"
    }
  }
}

README

dochost MCP server

[dochost-mcp MCP server]

English | 简体中文

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 eight tools — publish, update_page, get_page_content, set_page_options, 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.

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

bash
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.

Gemini CLI (extension):

bash
gemini extensions install https://github.com/zyli5313/dochost-mcp

Or add a remote HTTP server in ~/.gemini/settings.json:

json
{  "mcpServers": {    "dochost": {      "httpUrl": "https://dochost.io/api/mcp"    }  }}

Claude Desktop / Cursor / VS Code / Windsurf — add a remote HTTP server:

json
{  "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:

sh
npm ci --ignore-scriptsnode server/index.js

Or run it in Docker:

sh
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?

ClientRecommended authWhy
OpenClaw, HermesAPI keyHeadless 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 clientsOAuthOne 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:

One-shot from a shell: examples/publish.sh.

Tools

Eight 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.

ParameterTypeNotes
bodystring (required)The Markdown or HTML content to publish.
format"markdown" | "html"Auto-detected when omitted.
publicbooleanList on Explore. Defaults to false (unlisted).
customSlugstring · ProChoose the link path instead of a random slug.
passwordstring · ProGate the page behind a password.
noBrandingboolean · ProHide the dochost footer badge.

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.

ParameterTypeNotes
slugstring (required)The page to update.
bodystring (required)The new Markdown or HTML content.
format"markdown" | "html"Auto-detected when omitted.
titlestringOverride the derived title.

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.

get_page_content

Read back the current Markdown or HTML of one of your pages by slug. Call it before update_page whenever the assistant did not write the live content itself in the same conversation — update_page replaces the body wholesale, so editing from memory silently discards edits made elsewhere, including in the browser. Returns version and sha256; pass them to update_page as ifVersion / ifSha so the write is refused instead of overwriting a change it did not read. Expired pages are readable, and updating one republishes it on the same URL.

set_page_options

Change a published page's visibility, search-engine indexing or password without republishing it — the URL, view count and content stay the same. Parameters: slug (required), public, searchable, password, removePassword; send only the fields to change. Turning a paid capability off never needs an entitlement; turning one on is checked against the current plan. A password always forces the page private, so asking for both public: true and a password is refused. Branding is not settable here.

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

License

MIT — see LICENSE.

Source: README.md at commit f52649d

Tools

8

publish

Publish to dochost

Publish HTML or Markdown as a hosted web page and return a shareable URL. Use when the user asks to share an HTML quiz, calculator, report or Markdown document as a link. HTML JavaScript runs in a sandbox. Free links expire after seven days; paid link lifetime and options follow account entitlements. For revisions of an existing page, use update_page to keep the same link. Results report expiry and any ignored options; relay ignoredOptions/ignoredNote instead of claiming all requested settings were applied. New links use the account primary host; get_account reports it.

ParametersbodyrequiredformatpublicpasswordcustomSlugnoBranding

list_my_pages

List my dochost pages

List the pages you have published to dochost, newest first. Paginated; returns compact records (no page bodies).

Parameterslimitoffset

get_account

Get my dochost account

Get your plan, page-quota usage, entitlement flags (size cap, custom slug, password, branding, subdomain, custom domain), and the primary host new links publish on. Call when you need plan limits, domain details or paid-option availability; a basic publish can use defaults without this extra call. The primary host is chosen in the dashboard (manageDomainsUrl), not through this API.

Takes no parameters.

get_page

Get one of my dochost pages

Get one of your pages by slug: title, format, status, view/like counts, expiry, whether it is password-protected, and its current visibility / indexing / branding state. Never returns the page body or the password — call get_page_content when you need the source itself, and set_page_options to change any of the settings it reports.

Parametersslugrequired

get_page_content

Read one of my dochost pages

Read back the CURRENT Markdown or HTML of one of your pages. Call this before update_page whenever you did not write the live content yourself in this same conversation — update_page replaces the body wholesale, so editing from memory silently discards anything you cannot see, including edits the user made in the browser. Returns `version` and `sha256`; pass them to update_page as ifVersion / ifSha so the write is refused instead of overwriting a change you did not read. Expired pages are readable, and updating one republishes it on the same URL.

Parametersslugrequired

update_page

Update a dochost page

Replace the content of one of your pages in place. The URL, view/like counts, and expiry stay the same; only the body, format, and title change. Resending identical content is a no-op. Prefer this over publishing again whenever the user is revising something you already published for them — a second publish creates a second link and strands the one they already shared. This replaces the WHOLE body, so unless you wrote the live content yourself in this conversation, call get_page_content first and pass its version/sha256 back as ifVersion/ifSha — the write is then refused with the current version instead of overwriting an edit you never saw.

ParametersbodyrequiredslugrequiredifShatitleformatifVersion

set_page_options

Change a published page’s settings

Change a published page's visibility, search-engine indexing or password WITHOUT republishing it — the URL, view count and content all stay the same. Use this instead of deleting and publishing again, which changes the link the user already shared. Send only the fields you want to change. Turning a paid capability off never needs an entitlement; turning one on is checked against the current plan. A password always forces the page private, so asking for both `public: true` and a password is refused rather than silently resolved. dochost branding is NOT settable here: it is resolved from the account's live plan at render time, so there is nothing per-page to flip — read `brandingHidden` from get_page for the rendered answer.

ParametersslugrequiredpublicpasswordsearchableremovePassword

delete_page

Delete a dochost page

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

Parametersslugrequired

Version history

2
  1. v1.1.0LatestOct 20, 2026
  2. v1.0.0Sep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts