Skip to main content
Glama

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.

Related MCP server: htmlbook

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.

Gemini CLI (extension):

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

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

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

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?

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:

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.

Parameter

Type

Notes

body

string (required)

The Markdown or HTML content to publish.

format

"markdown" | "html"

Auto-detected when omitted.

public

boolean

List on Explore. Defaults to false (unlisted).

customSlug

string · Pro

Choose the link path instead of a random slug.

password

string · Pro

Gate the page behind a password.

noBranding

boolean · Pro

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

Parameter

Type

Notes

slug

string (required)

The page to update.

body

string (required)

The new Markdown or HTML content.

format

"markdown" | "html"

Auto-detected when omitted.

title

string

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

License

MIT — see LICENSE.

Available Tools

6 tools
delete_pageDelete a dochost pageA
Destructive
Inspect

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.

Inputs: slug (required). Returns: ok, slug, alreadyDeleted

get_accountGet my dochost accountA
Read-only
Inspect

Get your plan, page-quota usage, entitlement flags (size cap, custom slug, password, branding), and the primary host new links publish on. Call before publishing so you know your limits up front. The primary host is chosen in the dashboard (manageDomainsUrl), not through this API.

Inputs: no named parameters. Returns: ok, plan, password, analytics, +9 more

get_pageGet one of my dochost pagesA
Read-only
Inspect

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

Inputs: slug (required). Returns: ok, url, slug, likes, +8 more

list_my_pagesList my dochost pagesA
Read-only
Inspect

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

Inputs: limit, offset. Returns: limit, pages, total, offset, +1 more

publishPublish to dochostAInspect

Publish Markdown or HTML as a hosted dochost page and get a shareable URL. Respects your plan: link lifetime, password protection, custom slug, and branding all follow your account entitlements. Paid plans publish without dochost branding by default — pass noBranding: false to keep the mark. The link is issued on the account's primary host (a custom domain or subdomain when one is set in Settings › Domains, otherwise dochost.co/d); get_account reports which.

Inputs: body (required), format, public, password, +2 more. Returns: url, note, slug, format, +3 more

update_pageUpdate a dochost pageA
Destructive
Inspect

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.

Inputs: body (required), slug (required), title, format. Returns: ok, slug, title, format, +1 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct responsibility: publish creates, list_my_pages enumerates, get_page retrieves metadata for one page, update_page modifies content, delete_page removes, and get_account covers account/plan details. The potential publish/update_page overlap is explicitly disambiguated in the descriptions.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern: list_my_pages, get_account, get_page, update_page, delete_page. The lone exception is publish, which lacks an explicit object like publish_page, and list_my_pages includes a possessive that the other list/get tools do not.

    Tool Count5/5

    Six tools is well-scoped for a page hosting service: publish, list, get, update, delete, and account awareness. Each tool covers a necessary workflow step without unnecessary redundancy.

    Completeness4/5

    The core page lifecycle is covered: create, list, read metadata, update, delete, plus account/plan information. Minor gaps exist because page bodies are never retrievable via the API, so content recovery or editing an already-published page without the original source is not fully supported.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Publishes HTML pages straight from your AI assistant to a shareable URL, then lets you manage them - update, list, search, fetch, and delete pages in a public or private workspace. Turns "share what I just made" into a single tool call from Claude, Cursor, or any MCP client.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to publish HTML or Markdown to a public URL with a single HTTP POST, automatically converting Markdown to a styled webpage, with no account or setup required.
      7 npm
      1
      MIT