What does Dochost do that alternatives don’t?
Dochost is a dedicated MCP tool that turns any Markdown or HTML into a normal web page at its own URL, without requiring screenshots or raw file transfers.
D
Dochost MCP Server
@zyli5313
基本情報
Dochost MCP Server について
Publish Markdown or HTML to a clean, shareable link straight from your AI assistant. Hosted remote MCP server (Streamable HTTP) with OAuth sign-in — no API keys. Two tools: publish (Markdown/HTML → URL, with optional password, custom slug, and unlisted/public) and list_my_pages.
Dochost MCP Server の設定
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"dochost": {
"type": "http",
"url": "https://dochost.io/api/mcp"
}
}
}Dochost MCP Server のツール
8Publish 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.
List the pages you have published to dochost, newest first. Paginated; returns compact records (no page bodies).
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 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.
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.
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.
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.
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.
概要
What is Dochost?
Dochost is an MCP server that lets AI assistants publish Markdown or HTML content as clean, shareable web pages with persistent URLs. It integrates with MCP clients like Claude, ChatGPT, and Cursor via OAuth or API key authentication.
How to use Dochost?
Add the remote HTTP server with URL https://dochost.io/api/mcp to your MCP client’s configuration. For headless agents, create an API key at dochost.io and export it as DOCHOST_API_KEY. Authorize via OAuth once in a browser; the assistant then publishes as your authenticated account.
Key features of Dochost
- Publish Markdown or HTML as a hosted page with a shareable URL.
- Auto-detect content format (Markdown or HTML) when omitted.
- Optional password protection and custom slug (Pro).
- List your published pages with pagination via
list_my_pages. - OAuth for interactive clients, API key for headless agents.
- Free links last 7 days; paid plans for permanent links and custom features.
Use cases of Dochost
- Share AI-generated reports or documentation instantly via a single tool call.
- Publish HTML artifacts (charts, dashboards) as private web pages.
- Create password-gated pages for sensitive content.
- Publish unlisted pages for team feedback without public listing.
- Maintain a personal archive of AI outputs with permanent URLs (paid plan).
よくある質問
How does authentication work?
Interactive MCP clients (Claude, Cursor, VS Code, Windsurf) use OAuth with a one-time browser approval. Headless agents (OpenClaw, Hermes) use a static API key stored as an environment variable.
What are the pricing and limitations of Dochost?
Free published links expire after 7 days. Paid plans offer permanent links, password gating, custom slugs, custom subdomains, and removal of the dochost branding.
Can I publish HTML content?
Yes. The `publish` tool accepts HTML input and auto-detects the format; you can also explicitly set `format: "html"`.
Where does published data live?
Content is hosted on dochost.io servers. Ownership and entitlements are tied to your authenticated account; the server never uses tool input to determine access rights.
「開発者ツール」の他のコンテンツ
Casefile
azimov777One case file per task — shared by every session, agent and person that touches it. Self-hosted MCP server and live board. MIT.
3
Foremerge
naw103Catch intent conflicts before code conflicts. The open-source coordination protocol for coding agents, built above Git.
50
FARPY
mangomunchrVerified distributed compute for humans, applications, and agents. Submit Blender, Octane, and video workloads, route them across qualified GPUs, track asynchronous execution, download finished artifacts, and verify FARP
1
JiCo for Jira & Confluence – PII-redacting MCP server with Human-in-the-Loop
drkv-comJiCo for Jira & Confluence: local MCP server for Jira Data Center - redacts personal data before the AI model, holds every write for approval
Mcp-Warden
ermolukLocal-first credential broker for MCP. AI coding agents (Claude Code, Cursor, Codex…) call APIs, SSH and databases through scoped presets; secrets stay in your OS keychain and never enter the agent's context.
4
コメント