Htmlbook

io.github.Streamize-llcPublished by GitHub account Streamize-llcv1.0.0Updated Oct 24, 2026

Publish AI-generated HTML & Markdown to a hosted, shareable URL via MCP.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

Hosted MCP server that publishes AI-generated HTML or Markdown documents to a shareable, versioned URL with public, password or private access.

What you can do
Publish HTML, Markdown or multi-file bundles as hosted, versioned documents with a share link and reader themes (paper, sepia, dark). Browse, fetch and full-text search your shelved library, optionally by project. Organize documents: set title, tags and path, move between projects, rename. Control access: make a document public, password-protected or private. Get deep links to a specific section, restore earlier versions, and move documents to the trash. Fetch the authoring contract for hand-composed HTML before publishing.
When to use it
Use it when an agent produces an HTML report, dashboard, spec or notes that should leave the local machine and be opened on a phone or sent to someone as a link. Also useful for keeping a searchable, versioned library of generated documents.
Requirements
A remote MCP endpoint over Streamable HTTP. Authentication is required: OAuth (browser login, e.g. claude.ai or Claude Desktop) or an API key sent as a Bearer token in the Authorization header, obtained from the service's settings. Network access to the hosted service.
Before you install
Documents are uploaded to a third-party hosted service, so avoid publishing confidential content. Documents are private by default; making one public or password-protected exposes it to others, and changing a password revokes prior access. Tools can rename, move, restore and delete documents, so review write actions. An API key is a credential and should be kept out of shared configuration.

Installation

In SourceWeft

  1. Open Htmlbook in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Streamize-llc%2Fhtmlbook/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "htmlbook": {
      "type": "http",
      "url": "https://htmlbook.io/api/mcp"
    }
  }
}

README

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 with three modes — public (anyone, no login), password-protected (anyone with the password, no login), 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):

bash
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):

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

Cursor — ~/.cursor/mcp.json:

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

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

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:

text
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:

json
{  "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:

text
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

FormatWhenWhat htmlbook does
MarkdownProse: reports, plans, notes, specsKeeps the .md as the source of truth, renders a themed reader view (TOC, tables, callouts, task lists), stays downloadable + editable as Markdown
hb-doc HTMLRich docs: dashboards, KPIs, inline SVG chartsA <article class="hb-doc"> fragment styled only with hb-* classes + --hb-* tokens — the reader supplies the stylesheet and re-themes it (paper / sepia / dark, width, font size)
BundleA self-contained page with its own CSS/JSStored verbatim and rendered in a sandboxed iframe — your scripts run, your styling is preserved. Can be multi-file (index.html + sub-pages + assets, ≤10MB) for a small static site with working relative links

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. Three share modes: public (anyone), password-protected (anyone with the password, no login — changing it revokes prior access), or a secret link session-gated to 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 10 tools. Full reference: docs/mcp-tools.md.

ToolPurpose
publishShelve a document (HTML or Markdown) to a hosted URL; new version if it exists
guideGet the authoring contract (hb-doc classes, tokens, components) before composing HTML by hand
listBrowse your library, optionally filtered by project
getFetch a document's metadata + current body (for markdown, the .md source)
searchFull-text search across everything you've shelved (recall before re-deriving)
organizeSet title / tags / path, move between projects, rename
set_accessMake a document public, password-protected, or private
citeGet a shareable deep-link to a specific section (heading) of a document
restoreRoll a document back to an earlier version
deleteMove a document to the trash

Supported clients

ClientAuth
Claude CodeAPI key over MCP, or browser login; also REST
CursorAPI key over MCP
Codex CLIAPI key over MCP; also REST
claude.aiOAuth (custom connector)
Claude DesktopOAuth (custom connector)
Any MCP clientStreamable HTTP + Bearer key or OAuth 2.1

Documentation


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

Source: README.md at commit 70d2a07

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts