dochost.io

Publish shareable pages

dochost lets users publish Markdown or HTML from your AI as hosted pages, get clean shareable links, inspect their account limits, list and review published pages, update page content, and delete pages they no longer want online.

MCP connector

Server URL: https://dochost.io/api/mcp
Login: OAuth
Protocol: MCP 2025-11-25 · Interactive UI
Instructions: Use dochost when the user asks to publish HTML or Markdown and obtain a shareable web link, including quizzes, calculators, reports and documents. Publish only content the user has asked to share; drafting or previewing alone is not a request to publish. Pass the complete source as body, not a summary, file path or URL. Set format to html for HTML source or markdown for Markdown. For a basic publish, omit optional settings unless requested; call when you need plan limits or domain and paid-option availability. To revise an existing page, use to keep its link. Read first when you need the current source, and pass its version/sha256 as ifVersion/ifSha to avoid overwriting intervening edits. After success, return the exact result URL and explain any expiry or ignoredOptions/ignoredNote. If the result has firstPublishWelcome, follow it: relay the link first, then offer the one next step it names. When the user asks to change a page you already published in this conversation, call with its slug instead of publishing again, so the link they shared keeps working. Do not claim a link is permanent or password-protected unless the result confirms it. On failure, explain the returned error rather than inventing a URL or reporting success.

Tools

Reads data4

Changes data2

Deletes or can't be undone2

Skills

None in the store listings or on the server

MCP connector

Server URL

https://dochost.io/api/mcp

OAuth

Protocol

MCP 2025-11-25 · Interactive UI

Instructions

Use dochost when the user asks to publish HTML or Markdown and obtain a shareable web link, including quizzes, calculators, reports and documents. Publish only content the user has asked to share; drafting or previewing alone is not a request to publish. Pass the complete source as body, not a summary, file path or URL. Set format to html for HTML source or markdown for Markdown. For a basic publish, omit optional settings unless requested; call when you need plan limits or domain and paid-option availability. To revise an existing page, use to keep its link. Read first when you need the current source, and pass its version/sha256 as ifVersion/ifSha to avoid overwriting intervening edits. After success, return the exact result URL and explain any expiry or ignoredOptions/ignoredNote. If the result has firstPublishWelcome, follow it: relay the link first, then offer the one next step it names. When the user asks to change a page you already published in this conversation, call with its slug instead of publishing again, so the link they shared keeps working. Do not claim a link is permanent or password-protected unless the result confirms it. On failure, explain the returned error rather than inventing a URL or reporting success.