jh-presentation

io.github.pei-jzv0.5.2Updated Oct 5, 2026

AI-built HTML presentations: single-file decks with live diagrams, charts, editing and PDF export.

Overview

AI-generated overview

Lets an AI assistant build single-file HTML presentation decks with diagrams, charts, step reveals, in-place editing and PDF export.

What it does
Turns AI-written content into one self-contained HTML deck: engine, theme, branding and images are embedded, so it works offline from a local file. Tools cover deck creation and editing (create_deck, read_deck, write_deck, replace_slide, add_asset, upgrade_deck, repair_deck), themes, templates, history restore, and output such as open_deck and PDF export. Diagram components (flow, zoom maps, ER, sequence, charts, 3D layers) are driven by JSON the AI writes. audit_deck and screenshot_deck let the assistant check layout and fix its own work.
When to use it
Useful when you want presentation decks produced as real web pages rather than PowerPoint files, especially decks needing animated diagrams, step-by-step reveals, or a single portable HTML file. Also suited to letting the assistant verify layout before you present.
Requirements
Runs locally over stdio via the npm package jh-presentation (npx). Needs Node.js 20 or later and Google Chrome or Microsoft Edge for audits, screenshots and PDF export; set CHROME_PATH if the browser is in a non-default location. Decks are saved under JH_PRESENTATION_HOME (default ~/jh-presentation) or a --workspace folder. No API key is required.
Before you install
Decks contain JavaScript written by your AI client and run in your browser, so review generated decks before opening or sharing them. The server writes files inside the configured workspace folder (JH_PRESENTATION_HOME or --workspace), so point it at a directory you are willing to have modified. Avoid the browser's Save page as, which breaks decks; use in-deck Ctrl+S or repair_deck.

Installation

In SourceWeft

  1. Open jh-presentation in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

jh-presentation

[CI] [License: MIT]

Let AI build your presentations as real web pages. jh-presentation is an MCP server plus a small, dependency-free slide engine. Your AI client (Claude Desktop, Claude Code, VS Code, …) writes the content; jh-presentation turns it into a single self-contained HTML file with live diagrams, step-by-step animation, in-place editing and PDF export — and lets the AI check its own work with layout audits and screenshots.

No API key is needed: the thinking is done by the AI client you already use.

日本語の説明はこちら

[Flow diagram that highlights each step of a request]

Why HTML instead of PowerPoint?

AI models are far better at writing HTML/CSS/JS than at driving PPTX. That makes things possible that slide tools struggle with:

  • Diagrams that build up step by step, with data flowing along the arrows
  • A system overview you can click to zoom into, revealing the parts inside
  • ER diagrams and sequence diagrams generated from data
  • Charts that animate, code that highlights line by line, demos that actually run
  • Everything in one HTML file that works offline — mail it, put it on a share, present from a browser
[Zoom map][ER diagram]
Click a box to zoom into its internalsClick a table to highlight its relations and join keys
[Chart][3D stack]
Charts with grow animation and legend togglesLayered architecture exploded in 3D

Features

  • Single-file decks — engine, theme, brand and images are embedded. No build step, no CDN, works from file://
  • Diagram components (data in, motion out) — flow diagrams / zoom maps, ER diagrams, sequence diagrams, charts (bar, line, pie, donut), 3D layer stacks, before/after sliders, terminal replays. The AI writes JSON; layout, animation, clicks and the static PDF view are handled for you
  • Steps — arrow keys reveal content one step at a time; components hook into the same steps
  • Themes — five built-in themes (default, dark, corporate, pop, mono), a live theme gallery, and AI-generated custom themes
  • Branding — your name, logo and a label (e.g. DRAFT) in a header/footer band
  • Self-checking AI — audit_deck detects overflow, clipping, overlapping text, low contrast, missing images and external requests; screenshot_deck returns slide images so the AI can look and fix
  • Edit without AI — double-click any text box to edit it in place, press Ctrl+S to save straight back to the file (only the edited text is replaced)
  • Presenting — presenter view with notes, next slide and timer; overview; blackout; fullscreen window
  • Safe saving — atomic writes, revision checks against concurrent edits, 20-version history with restore
  • Request templates — tech talk, lightning talk, progress report, tech proposal (as MCP prompts)

[Theme gallery]

Requirements

  • Node.js 20 or later
  • Google Chrome or Microsoft Edge (used for audits, screenshots and PDF export; set CHROME_PATH if it is installed somewhere unusual)

Quick start

Claude Desktop

Open Settings → Developer → Edit Config and add:

json
{  "mcpServers": {    "jh-presentation": {      "command": "npx",      "args": ["-y", "jh-presentation"],      "env": { "JH_PRESENTATION_HOME": "C:/Users/you/Documents/decks" }    }  }}

Quit Claude Desktop from the tray icon and start it again. Then ask, for example:

Make a 15-minute deck explaining Git branching strategies, with diagrams and step-by-step reveals.

Claude Code

bash
claude mcp add jh-presentation -e JH_PRESENTATION_HOME=~/decks -- npx -y jh-presentation

VS Code (.vscode/mcp.json)

json
{  "servers": {    "jh-presentation": {      "command": "npx",      "args": ["-y", "jh-presentation"],      "env": { "JH_PRESENTATION_HOME": "${userHome}/Documents/decks" }    }  }}

Decks are saved in JH_PRESENTATION_HOME (default ~/jh-presentation), or the folder given with --workspace <dir>.

What the AI can do (MCP tools)

AreaTools
Guideget_guide — authoring rules, component catalog, workflow
Themeslist_themes, open_theme_gallery, preview_themes, get_theme_guide, create_theme
Templateslist_templates (also exposed as MCP prompts)
Deckslist_decks, create_deck, read_deck, write_deck, replace_slide, add_asset, upgrade_deck, list_history, restore_history, repair_deck
Checkingaudit_deck, screenshot_deck
Outputopen_deck (optionally fullscreen), export_deck (PDF)

Presenting

KeyAction
→ / Space / EnterNext (including steps)
←Previous
SPresenter view (notes, next slide, timer)
E / double-click a boxEdit text in place (Ctrl+S saves, Esc or "✕" exits)
OOverview
FFullscreen
BBlackout
number + EnterJump to slide
?Help

Do not use the browser's "Save page as…" — it saves the rendered page and breaks the deck. Use Ctrl+S inside the deck. If it happens anyway, repair_deck restores it.

[Editing text in place]

Working in this repository

bash
npm installnpm run dev        # http://localhost:4000 — deck list, theme gallery, feature samplenpm test
CommandDescription
npm run devPreview server with live reload (local only, 127.0.0.1)
npm run new -- <name> "Title" [--theme <t>] [--brand footer] [--fullscreen]New deck in decks/
npm run upgrade [-- <name>]Re-embed the latest engine, theme and brand
npm run pdf -- <name>Export a PDF to dist/
npm run repair -- <name>Repair a deck broken by the browser's "Save page as"
npm run galleryBuild the theme gallery
npm run mcpStart the MCP server (workspace .workspace/)

The feature sample is examples/sample.html. Rules for AI authors live in CLAUDE.md (Claude Code), AGENTS.md (Codex, Cursor and other agents) and docs/authoring-guide.md; the edit protocol for host applications is in docs/edit-protocol.md.

The authoring guide, templates and tool descriptions are currently written in Japanese. LLMs follow them fine whatever language you chat in, and decks can be in any language.

Security

Everything runs on your machine: no telemetry, no outbound requests, the preview/save server binds to 127.0.0.1 only, and files are written only inside the workspace. Decks contain JavaScript written by your AI client and run in your browser. See SECURITY.md.

License

MIT. Every deck carries the MIT notice for the embedded engine, components and themes in its generated section, so decks can be shared as-is. The content of your slides is yours.


日本語

AI にプレゼンを「Web ページ」として作らせる MCP サーバーです。Claude Desktop・Claude Code・VS Code などの AI クライアントが内容を書き、jh-presentation が1 ファイルの HTML デッキにします。動く図・段階表示・その場での文字編集・PDF 出力に対応し、AI は検査とスクリーンショットで自分の出来を確認して直せます。API キーは不要です (考えるのは普段使っている AI クライアント)。

  • 動く図の部品: 関連図・ズームマップ・ER 図・シーケンス図・グラフ・3D 分解図・ビフォー・アフター・ターミナル再生 (AI は JSON を書くだけ)
  • テーマ 5 種 + 自作テーマ、名前・ロゴの帯、依頼文テンプレート (技術解説・LT・進捗報告・技術提案)
  • 枠をダブルクリックして文字を直し、Ctrl+S で元のファイルに保存 (ブラウザの「名前を付けて保存」は使わない)
  • 発表者ビュー・一覧・全画面、保存履歴と復元、壊れたデッキの復旧

使い方 (Claude Desktop)

設定 → 開発者 → 「構成を編集」で次を追加し、タスクトレイから終了して再起動します。

json
{  "mcpServers": {    "jh-presentation": {      "command": "npx",      "args": ["-y", "jh-presentation"],      "env": { "JH_PRESENTATION_HOME": "C:/Users/you/Documents/decks" }    }  }}

あとは「Git のブランチ戦略を 15 分で説明するデッキを、図とステップ表示を多めに作って」のように頼むだけです。 詳しい設定 (Claude Code・VS Code) は mcp/README.md を参照してください。 このリポジトリで AI に作業させる場合のルールは CLAUDE.md (Claude Code) / AGENTS.md (Codex・Cursor など)、スライドの書き方は docs/authoring-guide.md にあります。

ライセンスは MIT です。デッキには埋め込んだエンジン・部品・テーマの MIT 表記が自動で入るので、そのまま配布できます。スライドの内容は作成者のものです。

Source: README.md at commit fc6f996

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.5.2LatestOct 5, 2026