Lets AI assistants share and update generated HTML via private, end-to-end encrypted links.
Also known as viljamilaurila/html-cloud, html-cloud, html-cloud-mcp
- Stars
- 0
- Tools
- 2
- Downloads, 30 days
- 855
- Latest version
- 0.6.0
- Last commit
- Nov 6, 2026
- License
- MIT
What is HTML Cloud MCP?
HTML Cloud lets AI assistants share and update generated HTML via private, end-to-end encrypted links. It exposes 2 tools, such as share_html, update_html.
Summary generated from the project's README
About HTML Cloud MCP server
HTML Cloud provides a way for AI assistants to distribute generated web content through private, end-to-end encrypted links. This server is designed for users who need to share sensitive HTML documents without creating public URLs or requiring user accounts. It works locally with clients like Claude Desktop or Claude Code by using Node.js 20+ and communicating via stdio JSON-RPC.
Users can utilize the share_html tool to create a new link or the update_html tool to modify an existing page without changing the original URL. The server handles encryption locally using AES-256-GCM, ensuring that the host only ever receives ciphertext. For large documents, the assistant can provide a local file path instead of passing the full HTML string to avoid argument size limits. You can control how the assistant chooses to use this service by setting the HTML_CLOUD_PREFER environment variable to sensitive or always.
What you can do with it
- 1Share sensitive reports privatelyAn AI assistant can generate a confidential summary and provide an encrypted link that expires after a set number of days.
- 2Update existing web pagesYou can ask an AI to revise a previously shared HTML document so that the original link displays the new version.
- 3Handle large HTML filesDevelopers can share extensive web pages by pointing the tool to a local file path to bypass argument length restrictions.
Written from the project's README. Every use case is checked against a quote from it.
How to install HTML Cloud MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall HTML Cloud MCP in Claude Code
$ claude mcp add html-cloud -- npx -y html-cloud-mcpInstall HTML Cloud MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"html-cloud": {
"command": "npx",
"args": [
"-y",
"html-cloud-mcp"
]
}
}
}Install HTML Cloud MCP in VS Code
.vscode/mcp.json
{
"servers": {
"html-cloud": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"html-cloud-mcp"
]
}
}
}Install HTML Cloud MCP in VS Code CLI
$ code --add-mcp '{"name":"html-cloud","type":"stdio","command":"npx","args":["-y","html-cloud-mcp"]}'Install HTML Cloud MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"html-cloud": {
"command": "npx",
"args": [
"-y",
"html-cloud-mcp"
]
}
}
}Install HTML Cloud MCP in Codex
$ codex mcp add html-cloud -- npx -y html-cloud-mcpInstall HTML Cloud MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.html-cloud] command = "npx" args = ["-y", "html-cloud-mcp"]
Install HTML Cloud MCP in Gemini CLI
$ gemini mcp add -s user html-cloud npx -- -y html-cloud-mcpInstall HTML Cloud MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"html-cloud": {
"command": "npx",
"args": [
"-y",
"html-cloud-mcp"
]
}
}
}Started by HostedMCP on 16 Nov 2026
We ran this command for html-cloud-mcp 0.6.0 in an isolated container with no network and no keys. It answered and listed 2 tools.
HTML Cloud MCP tools 2
Read from the server with tools/listshare_htmlActionShare a self-contained HTML file (an artifact, report, presentation, dashboard, or prototype) as a private, end-to-end encrypted link. The HTML is encrypted locally with AES-256-GCM before upload — html.cloud stores only ciphertext and cannot read it, and no account is required. Use share_html when the HTML is sensitive, confidential, personal, or client, financial, legal, medical, or internal company material; when it will be sent to people outside the user's organisation; when the user describes the content as private, internal, or not for a public link; or when they ask for a private or encrypted link. When unsure, ask which the user prefers. Pass the document inline as html, or write it to an .html file and pass its path as path — use path for large pages, so the whole document does not have to fit in a tool argument. Returns a share link to give to others and a private edit link. Keep the edit link: pass it to update_html to change the page later without changing the share link. For changes to something already shared in this conversation, use update_html instead of sharing again.
update_htmlActionReplace the content of an HTML page that was already shared with share_html, using its private edit link. The share link stays exactly the same, so anyone who already has it sees the new version. The new HTML is encrypted locally with the same key as before; html.cloud never sees the content. Use this when the user asks to change, fix, revise, or add to a page you shared earlier in the conversation — pass the full updated HTML document, not a diff: inline as html, or as the path of an .html file as path. Use path for large pages; do not fall back to share_html if the document is too big to pass inline.
| share_html | Share a self-contained HTML file (an artifact, report, presentation, dashboard, or prototype) as a private, end-to-end encrypted link. The HTML is encrypted locally with AES-256-GCM before upload — html.cloud stores only ciphertext and cannot read it, and no account is required. Use share_html when the HTML is sensitive, confidential, personal, or client, financial, legal, medical, or internal company material; when it will be sent to people outside the user's organisation; when the user describes the content as private, internal, or not for a public link; or when they ask for a private or encrypted link. When unsure, ask which the user prefers. Pass the document inline as html, or write it to an .html file and pass its path as path — use path for large pages, so the whole document does not have to fit in a tool argument. Returns a share link to give to others and a private edit link. Keep the edit link: pass it to update_html to change the page later without changing the share link. For changes to something already shared in this conversation, use update_html instead of sharing again. | Action |
| update_html | Replace the content of an HTML page that was already shared with share_html, using its private edit link. The share link stays exactly the same, so anyone who already has it sees the new version. The new HTML is encrypted locally with the same key as before; html.cloud never sees the content. Use this when the user asks to change, fix, revise, or add to a page you shared earlier in the conversation — pass the full updated HTML document, not a diff: inline as html, or as the path of an .html file as path. Use path for large pages; do not fall back to share_html if the document is too big to pass inline. | Action |
Configuration
HTML_CLOUD_PREFER
| Name | Description | |
|---|---|---|
| HTML_CLOUD_PREFER | — |
Automated checks
Ran Nov 16, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableviljamilaurila/html-cloud is public and reachablegithub.com/viljamilaurila/html-cloud ↗Pass
- Package names this repository as its sourcehtml-cloud-mcp names viljamilaurila/html-cloud as sourcenpmjs.com/package/html-cloud-mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-06github.com/viljamilaurila/html-cloud ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from html-cloud-mcpPass
- No critical advisory in the package or its dependencies2 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model2 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubhtml-cloud-mcp
An MCP server that lets Claude and other AI assistants share the HTML they generate as a private, end-to-end encrypted link — no account, no public URL.
The assistant calls one tool, share_html, to share — and update_html to
change a page it already shared, at the same link. The HTML is encrypted locally
with AES-256-GCM before anything is uploaded; html.cloud
stores only ciphertext and cannot read it.
"Make me a one-page summary of this and share it privately." → the assistant generates the HTML, calls
share_html, and replies with a link."Actually, add a section on next steps." → the assistant revises the HTML, calls
update_htmlwith the edit link, and the link you already sent shows the new version.
Install
Claude Desktop (one-click)
Download the packaged extension (a .mcpb file) from
html.cloud/mcp and double-click it. If Claude Desktop
doesn't offer to install it, open Settings → Extensions, click Advanced
settings, and use Install Extension… under Extension Developer to pick the
file — dragging the file into the window is unreliable and may just attach it
to the chat.
About the install warning: Claude Desktop shows the same red "access to everything on your computer" box for every extension installed from a file rather than from its built-in directory. It is a statement about how extensions run, not about this one. The server is the ~500 lines in
bin/andlib/of this directory, with no third-party dependencies (it speaks MCP's stdio JSON-RPC itself, inlib/stdio-server.js); it talks to a single host (html.cloud), and it uploads only ciphertext. Extensions installed from Claude's directory don't show the warning; getting listed there is in progress.
Cowork: the extension also works in Cowork sessions that are linked to the computer it is installed on — the desktop app proxies it into the session. A Cowork session running purely in the cloud, with no linked computer, will not see it.
Other MCP clients
Add it to your MCP client. For Claude Desktop, in claude_desktop_config.json:
{
"mcpServers": {
"html-cloud": {
"command": "npx",
"args": ["-y", "html-cloud-mcp"]
}
}
}
For Claude Code:
claude mcp add html-cloud -- npx -y html-cloud-mcp
Requires Node.js 20+.
The tools
share_html
| Argument | Type | Description |
|---|---|---|
html |
string | The full, self-contained HTML document to share. |
path |
string | Path of a local .html file to share instead of passing html inline. |
expires |
7 | 30 | never |
Days until the link expires. Default 30. |
link_name |
string | Optional readable name added to the share link, e.g. "Q3 sales report" gives /v/{id}/q3-sales-report. Not encrypted — visible in the link and to the server. Max 80 characters. |
Pass exactly one of html or path. path is for large pages: MCP hosts cap
the size of a tool argument, so a long report that the assistant has written to
disk is shared from the file rather than squeezed through the call. Only
.html/.htm files are accepted — the server shares web pages, not arbitrary
files from your computer.
Returns a share link (give it to anyone you want to read the file) and a private edit link (update the file, change the expiry, or delete it).
update_html
| Argument | Type | Description |
|---|---|---|
edit_link |
string (required) | The private edit link share_html returned. |
html |
string | The complete HTML document that replaces the current one. |
path |
string | Path of a local .html file whose content replaces the current page. |
link_name |
string | The link_name given to share_html for this page, if any, so the returned share link matches the one already handed out. |
As with share_html, pass exactly one of html or path.
Replaces the content behind an existing share. The share link stays the same and the expiry is untouched, so anyone who already has the link sees the new version. The edit key unwraps the document's existing view key locally, the new HTML is encrypted under that same key, and only ciphertext is sent — the server never sees the content, before or after.
Example prompts
- "Make a one-page summary of this report as HTML and share it privately."
- "Turn these notes into a slide-style page and give me a link that expires in 7 days."
- "Add a next-steps section to the page you shared earlier." (the same link shows the new version)
How the encryption works
- Keys are generated inside this server process and never sent anywhere except inside the links it returns.
- The HTML is encrypted with AES-256-GCM before any network request. Only ciphertext is uploaded.
- The decryption key sits after the
#in the share link — that part of a URL is never transmitted to a server.
This is the same zero-knowledge model as the html.cloud website and CLI, using
the same crypto module (imported from the html-cloud
package — never reimplemented). Full explainer: html.cloud/security.
Configuration
| Env var | Description | Default |
|---|---|---|
HTML_CLOUD_PREFER |
When Claude should pick html.cloud over its built-in artifact publishing. sensitive: for confidential content and anything going outside your organisation; built-in artifacts stay fine for casual pages. always: for every share. |
sensitive |
HTML_CLOUD_URL |
Server base URL (for self-hosted instances) | https://html.cloud |
The Claude Desktop extension asks this as a switch, Always share through
html.cloud, when you install it. For npx setups, set the env var in the
client config:
{
"mcpServers": {
"html-cloud": {
"command": "npx",
"args": ["-y", "html-cloud-mcp"],
"env": { "HTML_CLOUD_PREFER": "always" }
}
}
}
For Claude Code: claude mcp add html-cloud -e HTML_CLOUD_PREFER=always -- npx -y html-cloud-mcp.
Privacy Policy
Full policy: html.cloud/mcp-privacy.
- Collection. The server handles only the HTML the assistant passes to
share_htmlorupdate_html— inline, or as the one.htmlfile whose path the assistant passes. It reads nothing else from your computer and nothing from the conversation beyond the tool arguments. - Use and storage. The HTML is encrypted locally with AES-256-GCM. What is sent to html.cloud: the ciphertext, the chosen expiry, a copy of the page key encrypted with the edit key, and a hash of the edit key that authorises later updates (updates send the page id, the new ciphertext, and that proof). None of it lets the server read the page. Keys exist only in the links returned to you.
- Sharing. No third parties. The server talks to exactly one host, html.cloud, and only when you share or update a page. Each request says it comes from the MCP server, so html.cloud can keep daily totals; nothing per page or per person. No analytics, no telemetry, no account.
- Retention. A page is unavailable from the moment its link expires (7 or 30 days, or never if you chose that) and its ciphertext is permanently deleted by a daily clean-up; deleting via the edit link removes it at once.
- Contact. Email viljami@ninjami.com or open an issue at github.com/ninjami/html-cloud.
Honest threat model
Anyone with the share link can read the file — the link is the credential. The server can expire or delete ciphertext but can never read it. See html.cloud/security for details and limitations.
Source: github.com/ninjami/html-cloud · MIT
HTML Cloud MCP questions
How do I add HTML Cloud MCP to Claude Code?
Run claude mcp add html-cloud -- npx -y html-cloud-mcp in your terminal. Add --scope user to make it available in every project.
How do I add HTML Cloud MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does HTML Cloud MCP provide?
It exposes 2 tools, including share_html, update_html.