Logodochost
  • Inicio
  • Explorar
  • Precios
  • Sobre
  • FAQ
Telegram
Logodochost

Paste AI-made Markdown or HTML. Send a clean link your coworker can open.

Empezar gratis
Product
  • Telegram Bot
  • Browser Extension
  • Integrations
  • Features
  • Pricing
  • MCP server
  • FAQ
Resources
  • Blog
Use cases
  • PDF to Markdown
  • Word to Markdown
  • Markdown to Word
  • CSV to Markdown
  • Markdown to Google Docs
  • Markdown to Excel
  • Markdown to HTML
  • HTML to Markdown
  • URL to Markdown
  • Markdown Preview
  • Free HTML Hosting
  • Share ChatGPT HTML
  • All tools
Company
  • About
  • Contact
  • Changelog
Legal
  • Cookie Policy
  • Privacy Policy
  • Terms of Service
© 2026 dochost All Rights Reserved.
Featured on Corey.ToolsFeatured on ToolDirsFazier badgeFeatured on Twelve ToolsFeatured on Twelve ToolsFeatured on Wired BusinessFeatured on Wired Business
Model Context Protocol · OAuth, no API keys

Publish Markdown and HTML to a link — straight from your AI assistant.

The dochost MCP server gives Claude, ChatGPT and Cursor a publish tool. Ask your assistant to share a document and it hands back a clean, public dochost link — no copy-paste, no separate dashboard.

Install dochostSee the tools
Markdown & HTMLSecure OAuth sign-inRespects your plan
Run in your terminalone line
claude mcp add --transport http dochost \
 https://dochost.io/api/mcp
Then run /mcp inside Claude Code and approve in the browser.
Your assistant publishes as you — output follows your plan's entitlements.
★ Built for headless agents

Publish straight from OpenClaw & Hermes

Install the dochost skill once and your agent gets a publish-to-link command. Headless agents authenticate with an API key — created in seconds.

OpenClaw 1-command

Publish from your Telegram agent — no Claude Code session needed.

openclaw skills install dochost-publish
Set up OpenClaw API key
Hermes 1-command

Drop the skill into Hermes — plain HTTP, no MCP wiring.

cp -r dochost-mcp/…/dochost-publish .hermes/skills/
Set up Hermes API key
Open source — view the MCP server on GitHub
Also works with any MCP clientClaudeChatGPTCursorClaude CodeWindsurf

Install for your tool

Pick your client, copy one command, authorize once. No SDK, no deploy.

How to add the dochost MCP server to Claude Code, Codex and Cursor

Add the remote server over HTTP, then authorize from inside Claude Code.

Terminal
claude mcp add --transport http dochost \
 https://dochost.io/api/mcp
Run /mcp in Claude Code and approve in the browser. Add --scope user to use it in every project.
1 Add the server2 Authorize with OAuth3 Ask it to publish

Tools your assistant gets

Six tools — publish, then manage and inspect what you published. Ownership and entitlements come from your account, never from tool input.

publish
Publish Markdown or HTML as a hosted page and get a shareable URL.
Parameters
bodyrequiredThe Markdown or HTML content to publish.
format"markdown" | "html"Auto-detected when omitted.
publicbooleanList on Explore. Defaults to false (unlisted).
customSlugProstringChoose the link path instead of a random slug.
passwordProstringGate the page behind a password.
noBrandingProbooleanHide the dochost footer badge.

Returns url, slug, expiresAt.

Use case · Publish a document
you"Publish my Q3 report as a private page with a password."
publishformat: markdown, password: •••dochost.co/d/q3-report
MarkdownPassword7-day link
list_my_pages
List the pages you have published, newest first. Paginated.
Parameters
limitnumber (1–50)How many pages to return. Defaults to 20.
offsetnumberSkip this many for pagination. Defaults to 0.

Returns compact records — slug, url, title, format, views, expiresAt. Never the page body or password.

Also live — get_page, get_account, update_page and delete_page.

Use case · Review your pages
you"Which of my pages expire this week, and how many views do they have?"
list_my_pageslimit: 20
Q3 report1.2K2d
Launch landing page8605d
Team offsite notes1436d
manage & inspect
Once a page exists, your assistant can check it, edit it, or take it down — all scoped to your account.
Tools
get_accountYour plan, page-quota usage, and limits — so it knows what it can do before publishing.
get_pageOne page's title, status, views and likes by slug. Never the body or password.
update_pageReplace a page's content in place — same URL, same view count, same expiry.
delete_pagePermanently delete a page by slug. The link stops working immediately and the slug is freed.

Built for the way you already work with AI

The publish step disappears. Your assistant ships the page; you get the link.

Markdown and full HTML

Most publish tools take Markdown only. dochost ships raw HTML too — so AI-generated pages, demos and prototypes render exactly as written.

OAuth, not pasted keys

One-click sign-in over OAuth 2.1. Nothing to copy into a config, nothing to leak in a prompt or a shared machine.

Your plan, your rules

Output mirrors the website: free links last 7 days; Pro unlocks permanent links, passwords, custom slugs and no branding.

Private by default

Pages are unlisted unless you ask to make them public. They never land on Explore by accident.

Rate-limited and audited

20 publishes a minute, 300 an hour, per account. Every call is logged for safety — document bodies never are.

One dashboard for everything

Pages published from chat show up next to the ones you made on the web — same views, likes, expiry and analytics.

From "share this" to a live URL

A real exchange once dochost is connected. The tool call and result are inline in the chat.

Assistant · dochost connected
You
Take the release notes you just wrote and publish them as a public page I can post in our Discord.
AI
On it — publishing as a public Markdown page.
publishcalling tool
{ format: "markdown", public: true, body: "# Release v2.4 …" }
Done. Here is your shareable link:
dochost.co/d/release-v2-4

MCP, answered

The Model Context Protocol questions people ask before connecting dochost.

What is the dochost MCP server?

It is a hosted Model Context Protocol server at dochost.io/api/mcp. Connect it to an AI assistant and the assistant gains a publish tool that turns Markdown or HTML into a live, shareable dochost link — no copy-paste between chat and a browser.

Which AI clients can connect?

Any MCP client over streamable HTTP — including Claude, ChatGPT, Cursor, Claude Code and Windsurf. One-click clients only need the server URL; config-file clients add it to their mcp.json.

Do I need an API key?

No. Connecting uses OAuth — you sign in once and approve access, and the assistant publishes as you. A manual API key is available for headless and CLI clients that cannot run the browser sign-in flow.

Is my published content private?

Pages publish unlisted by default and are not added to Explore unless you set public to true. Pro accounts can also password-protect a page. Your document body is never sent to analytics.

Does it respect my plan?

Yes. Output follows your account exactly like the website: free links last 7 days, while Pro and Lifetime unlock permanent links, passwords, custom slugs and no branding. The tool can't grant a feature your plan doesn't include.

How is this different from the REST API?

The REST API is for code you write. The MCP server is for assistants you talk to — it advertises the publish and list_my_pages tools so an AI client can discover and call them on its own, with OAuth handling identity. Same publishing engine underneath.

Free links expire after 7 days

Agents publish in bulk.
Pro keeps every link alive.

  • Permanent links — nothing your agent ships ever 404s
  • 200 live pages, 10 MB each
  • Custom slugs, password protection, no branding
Make my links permanentOr keep free — 7-day links, no card required.

Give your assistant a publish button

Connect dochost once and turn any Markdown or HTML your AI writes into a shareable link — from inside the chat.

Connect dochost