Publish AI-generated HTML & Markdown to a hosted, shareable URL via MCP.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"htmlbook": {
"url": "https://htmlbook.io/api/mcp",
"headers": {
"Authorization": "Bearer hb_live_REPLACE_WITH_YOUR_KEY"
}
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in writing
Markdown to WeChat CLI | 一键排版发布到微信公众号:支持 40+ 排版样式和专业主题 、AI 配图 、批量发布
Define task-specific AI sub-agents in Markdown for any MCP-compatible tool.
AI prompt optimization for 58+ platforms across 7 categories with custom platforms
URL to LLM-ready markdown — plus per-page category, page_structure, and query-driven highlights.
MCP Security Weekly
Get CVE alerts and security updates for io.github.Streamize-llc/htmlbook and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
https://htmlbook.io/api/mcpPOST https://htmlbook.io/api/docsGet 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.
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- ..."
}
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.
| Format | When | What htmlbook does |
|---|---|---|
| Markdown | Prose: reports, plans, notes, specs | Keeps the .md as the source of truth, renders a themed reader view (TOC, tables, callouts, task lists), stays downloadable + editable as Markdown |
| hb-doc HTML | Rich docs: dashboards, KPIs, inline SVG charts | A <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) |
| Bundle | A self-contained page with its own CSS/JS | Stored verbatim and rendered in a sandboxed iframe — your scripts run, your styling is preserved. Can be multi-file (index.html + |