Publish Markdown or HTML to a clean, shareable link straight from your AI assistant. OAuth sign-in, no API keys. Two tools: publish (Markdown/HTML → URL, with optional password, custom slug, and public/unlisted) and list_my_pages. Homepage: https://dochost.io
Scored across 8 tools
Each tool has a clearly distinct role: publish creates a new link, update_page revises content in place, set_page_options changes metadata without republishing, and get_page vs get_page_content separate metadata from source. The descriptions explicitly warn against confusing publish with update_page and get_page with get_page_content, reducing misselection risk.
Most names follow a predictable verb_noun snake_case pattern: delete_page, get_account, get_page, get_page_content, list_my_pages, set_page_options, update_page. The standalone 'publish' and the possessive 'list_my_pages' are minor deviations but remain readable and domain-appropriate.
Eight tools is well-scoped for a page-hosting service: one create/publish, two reads, two update operations, one delete, one list, and one account/limits tool. Each tool earns its place without obvious redundancy.
The surface covers the full page lifecycle: publish, list, read metadata/content, update content, change options, delete, and inspect account entitlements. Minor gaps exist around explicit slug renaming or domain management, but the descriptions note those are dashboard/account concerns rather than API operations.
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 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.
Inputs: no named parameters. Returns: ok, plan, password, analytics, +11 more
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.
Inputs: slug (required). Returns: ok, url, slug, likes, +11 more
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.
Inputs: slug (required). Returns: url, body, note, slug, +7 more
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
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, or three days when published with public set to false; 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.
Inputs: body (required), format, public, password, +2 more. Returns: url, note, slug, format, +6 more
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.
Inputs: slug (required), public, password, searchable, +1 more. Returns: ok, url, slug, public, +3 more
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.
Inputs: body (required), slug (required), ifSha, title, +2 more. Returns: ok, slug, title, format, +1 more
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.