dochost

io.github.zyli5313由 GitHub 账号 zyli5313 发布v1.1.0更新于 Oct 24, 2026

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

已验证Streamable HTTP可网页运行效率与工作流文件与存储

概览

AI 生成的概览

让 AI 助手把 Markdown 或 HTML 发布成可分享的托管网页链接，并可列出、读取、更新、调整选项和删除这些页面。

可以做什么
  • 把 Markdown 或 HTML 发布为托管页面并返回可分享链接，可选公开列出、自定义路径、密码保护或去除品牌标识
  • 按最新优先分页列出已发布的页面（不含正文）
  • 查看单个页面的标题、格式、状态、浏览与点赞数、到期时间、是否加密，并读回当前 Markdown 或 HTML 正文
  • 原地替换页面正文，保留原链接、浏览数与到期时间
  • 在不重新发布的情况下修改可见性、搜索引擎索引或密码
  • 永久删除页面并释放其路径
适用场景
适合助手产出报告、README、测验、计算器或 HTML 作品，需要以普通网页而非截图或原始文件分享时；也适合链接需要后续修改维护、而不是每次重新生成的情况。
运行要求
使用 dochost.io 上的远程 Streamable HTTP 端点，通过浏览器 OAuth 登录，交互式客户端无需 API 密钥。无头运行或使用 stdio/Docker 桥接时需要 Node.js 22 或更高版本，以及 DOCHOST_API_KEY 运行时密钥。套餐限制由 dochost 账户决定。
安装前请注意
发布的页面是公开网页内容，托管在独立的内容域名上；HTML 中的 JavaScript 在沙箱中运行。免费链接 7 天后过期，永久链接、密码、自定义路径、子域名和去除品牌标识需付费套餐。update_page 会整体替换正文，修改前应先读取当前内容。delete_page 为永久删除，链接立即失效。DOCHOST_API_KEY 应按密钥保管，泄露后及时轮换。

安装

在 SourceWeft 中

  1. 打开 控制台中的 dochost，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.zyli5313%2Fdochost-mcp/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "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.

来源：README.md，提交 f52649d

工具

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.

输入参数body必填formatpublicpasswordcustomSlugnoBranding

list_my_pages

List my dochost pages

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

输入参数limitoffset

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.

无需输入参数。

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.

输入参数slug必填

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.

输入参数slug必填

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.

输入参数body必填slug必填ifShatitleformatifVersion

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.

输入参数slug必填publicpasswordsearchableremovePassword

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.

输入参数slug必填

版本历史

2
  1. v1.1.0最新Oct 20, 2026
  2. v1.0.0Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分