htmlbook

Publish AI-generated HTML and Markdown to a hosted, shareable URL. htmlbook is an MCP server and REST API that takes a document your coding agent just generated — an HTML report, a data dashboard, a spec, meeting notes, an interactive page — and turns it into a clean link you can open on your phone or send to someone, instead of leaving it as a local .html file buried in a project folder.

Push from Claude Code, Cursor, Codex, or claude.ai. htmlbook stores the document, re-themes it for comfortable reading on any device (paper / sepia / dark), keeps every edit as a version, and gives each document one share link — public for anyone, or a private secret link only you and your workspace can open.

Share the output as a link, not a file. When an agent makes HTML, the awkward part is everything after: getting it off your laptop, onto your phone, in front of someone else. htmlbook is the shelf that part lives on.

• 🌐 Website: https://htmlbook.io
• 🔌 MCP endpoint: https://htmlbook.io/api/mcp
• 📡 REST publish: POST https://htmlbook.io/api/docs
• 💬 Community: Discord

---

Quickstart

1. Connect your agent

Get an API key at https://htmlbook.io → Settings, then add the MCP server.

Claude Code (browser login, no key needed):

claude mcp add --transport http htmlbook https://htmlbook.io/api/mcp
# then run `claude` and approve the htmlbook login

Claude Code (with an API key):

claude mcp add --transport http htmlbook https://htmlbook.io/api/mcp \
  --header "Authorization: Bearer $HTMLBOOK_API_KEY"

Cursor — ~/.cursor/mcp.json:

{
  "mcpServers": {
    "htmlbook": {
      "url": "https://htmlbook.io/api/mcp",
      "headers": { "Authorization": "Bearer hb_live_REPLACE_WITH_YOUR_KEY" }
    }
  }
}

Codex CLI — ~/.codex/config.toml:

[mcp_servers.htmlbook]
url = "https://htmlbook.io/api/mcp"
bearer_token_env_var = "HTMLBOOK_API_KEY"

claude.ai / Claude Desktop — add a custom connector with URL https://htmlbook.io/api/mcp (OAuth — no key to paste).

See docs/getting-started.md for every client.

2. Publish a document

Just ask your agent. With the MCP server connected, it calls the publish tool:

You: Write up the Q3 numbers as a dashboard and put it on htmlbook.

Agent: htmlbook → publish
       ✓ shelved (hbdoc) · acme/q3-dashboard · v1 · read: https://htmlbook.io/app/p/acme/q3-dashboard

Prose (a report, a plan, notes) is easiest as Markdown — htmlbook keeps the .md as the source of truth and renders a themed reader view from it:

{
  "tool": "publish",
  "project": "acme",
  "markdown": "# Q3 Review\n\nRevenue is up 8% QoQ...\n\n## Highlights\n- ..."
}

3. Share it

Documents are private by default. Make one public to get a link anyone can open:

Agent: htmlbook → set_access  (visibility: public)
       ✓ acme/q3-dashboard is now public · https://htmlbook.io/d/a1b2c3

That's the whole loop: generate → publish → share.

---

What you can publish

The format is auto-detected at publish. You never have to declare it — push Markdown, push an hb-doc fragment, or push a full standalone HTML page and htmlbook routes it.

See docs/publishing.md and docs/hb-doc-contract.md.

---

Why htmlbook

• Off your laptop. An agent's HTML output is stuck on the machine that made it. htmlbook gets it onto your phone and into a shareable link.
• Readable everywhere. Because an hb-doc carries no CSS of its own, the reader themes it — the same document looks right on a phone in the dark and a desktop in daylight.
• Versioned. Every publish and every in-reader edit is a new immutable version. The History panel shows who changed what; any version restores.
• Markdown stays Markdown. A Markdown push is not lossily converted to HTML — the original .md is the source of truth and round-trips on download.
• Private by default. Nothing is public until you flip it. Secret links are session-gated to you and your workspace.
• Token-cheap. Push a large document as a file over the REST API so its bytes never pass back through your agent's context. See docs/rest-api.md.

---

The MCP tools

The htmlbook MCP server exposes 8 tools. Full reference: docs/mcp-tools.md.

---

Supported clients

---

Documentation

• Getting started — connect every client, get a key
• Publishing — the three formats, the publish tool, examples
• Markdown — source of truth, frontmatter, folder sync
• The hb-doc contract — classes, tokens, components
• Sharing & access — public, secret links, workspaces
• MCP tools reference — all 8 tools with example calls
• REST API — POST /api/docs, token-cheap file pushes
• examples/ — a report, a dashboard, a folder-sync setup

---

Made by Streamize. Documentation is MIT-licensed; htmlbook itself is a hosted service at htmlbook.io.