Skip to main content
Glama
viljamilaurila

HTML Cloud

by viljamilaurila
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Your browser encrypts the file with AES-256-GCM before anything is uploaded. The decryption key lives after the # in the share URL — browsers never send that part to the server. We store only ciphertext.

How it works

  1. Drop an HTML file on the homepage

  2. Your browser generates two random keys: a view key (AES-256-GCM) and an edit key

  3. The file is encrypted in-browser and uploaded as ciphertext

  4. You get two links:

    • Share link /v/{id}#viewKey — give this to anyone you want to read the file

    • Edit link /e/{id}#editKey — keep this private; it lets you replace the file, change its expiry, or delete it without changing the share link

  5. Files self-destruct after the chosen expiry (7 days, 30 days, or never — 30 days by default)

The server stores:

  • The encrypted blob

  • The view key encrypted with the edit key (so the edit page can re-encrypt without exposing the view key)

  • SHA-256(editKey) for authorization — never the plaintext keys

Related MCP server: drop

Security properties

  • Zero-knowledge uploads — the server cannot read any uploaded content

  • Key-in-fragment — browsers strip the URL fragment before sending HTTP requests; the key never reaches the server

  • Edit authorization — only SHA-256(editKey) is stored; the raw edit_key is verified on every write request (replace, expiry, settings, delete)

  • Expiry enforcement — expired documents are invisible to every route and hard-deleted daily by model:prune

  • 10 MB upload limit enforced server-side

  • No accounts — the API is stateless; every state-mutating request is authorized by the edit key, and uploads are rate-limited

See html.cloud/security for the full write-up.

CLI

Share a file from the terminal — encrypted locally, same crypto module as the browser:

npx html-cloud ./file.html

Or pipe straight from a generator:

my-report-tool | npx html-cloud -

The package lives in cli/ and on npm. See html.cloud/cli for usage and options.

MCP server

Let Claude (or any MCP client) share HTML for you. The server is published as html-cloud-mcp and lives in cli/mcp/:

{
  "mcpServers": {
    "html-cloud": {
      "command": "npx",
      "args": ["-y", "html-cloud-mcp"]
    }
  }
}

See html.cloud/mcp for setup instructions.

Stack

  • Laravel 13 (PHP 8.4+)

  • SQLite (swap to MySQL/Postgres via .env for production)

  • Vite 8 (CSS and JS build pipeline)

  • Web Crypto API (all crypto is browser-native; no external crypto libraries)

Setup

cp .env.example .env
php artisan key:generate
php artisan migrate
npm install && npm run build
php artisan serve

Run the test suite with:

php artisan test

For production, add a cron entry to run the scheduler:

* * * * * cd /path/to/html.cloud && php artisan schedule:run >> /dev/null 2>&1

Self-hosting

Clone, configure .env (APP_URL, DB_* if using MySQL/Postgres), run behind nginx or Caddy. Everything, including the encrypted blobs, lives in the database — back that up and you have the whole state.

License

MIT

Available Tools

2 tools
share_htmlShare HTML privatelyA

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
htmlNoThe full, self-contained HTML document to share. Use path instead for large documents.
pathNoAbsolute path of a local .html file to share instead of passing html inline.
expiresNoDays until the link expires. Defaults to 30.

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare it is a non-read-only, non-destructive, non-idempotent, open-world write; the description adds substantial behavior beyond that — AES-256-GCM local encryption, server stores only ciphertext and cannot read it, no account needed, expiry default of 30 days, and a dual return (public share link plus private edit link that must be retained). This is exactly the extra context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core action and encryption guarantee before the usage conditions, and every sentence contributes routing or behavioral information. Slightly long, with mild repetition of 'private'/'encrypted' phrasing, but not padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by describing both returned links and what to do with the edit link. Combined with the encryption, expiration, and no-account details, an agent has everything needed to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds rationale beyond the schema: it explains the html-vs-path tradeoff (use path for large pages so the document need not fit in a tool argument) and explains the purpose of the returned edit link rather than just its existence. Only the expires enum semantics are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('share a self-contained HTML file') plus scope ('private, end-to-end encrypted link'), and explicitly distinguishes itself from the sibling update_html for later changes. An agent can route correctly without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use conditions (sensitive/confidential/client/legal/medical content, sharing outside the org, user asks for a private or encrypted link), a fallback ('when unsure, ask which the user prefers'), and names the alternative tool plus the condition that selects it: use update_html for changes to something already shared.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

update_htmlUpdate a shared HTML pageA
DestructiveIdempotent

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
htmlNoThe complete, self-contained HTML document that replaces the current one. Use path instead for large documents.
pathNoAbsolute path of a local .html file whose content replaces the current page, instead of passing html inline.
edit_linkYesThe private edit link returned by share_html (https://html.cloud/e/{id}#{key}).

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true; the description adds value beyond them by noting the share link is preserved, that content is encrypted locally with the prior key, and that html.cloud never sees the content. These are behavioral facts the annotations cannot express, and they are consistent with destructiveHint (content is replaced).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and its consequence (same share link, encryption), then the when-to-use clause, then the parameter guidance. Every sentence carries a fact an agent needs; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description covers what matters for the return path (the share link is unchanged) plus the security model and input sizing strategy. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real decision guidance: html and path are mutually exclusive alternatives, path should be used for large pages, and the payload must be a complete document rather than a diff. That is meaningfully more than the schema alone conveys.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (replace) and resource (content of an HTML page previously shared) and explicitly names the sibling share_html as the origin of the page and edit link. An agent can distinguish this from share_html immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit trigger conditions ('when the user asks to change, fix, revise, or add to a page you shared earlier'), the only valid input form (full document, not a diff), and an explicit non-alternative ('do not fall back to share_html if the document is too big').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv0.1.0
    • First observedshare_html
    • First observedupdate_html
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.7/5.0

Scored across 2 tools

Disambiguation5/5

share_html and update_html have clearly distinct purposes: one creates a new share link, the other updates an existing page via its edit link. The descriptions explicitly guide the agent on when to use each, eliminating confusion.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern (share_html, update_html) and use snake_case throughout. The naming is predictable and easy to remember.

Tool Count4/5

With only two tools, the set is slightly thin but well-suited to the narrow purpose of sharing and updating HTML. Each tool earns its place, though the minimum viable surface for a sharing service might reasonably include a third operation like delete.

Completeness3/5

The surface covers create and update but lacks a delete or revoke operation, which is a notable gap for a privacy-focused sharing service. Users cannot stop sharing a link or clean up old shares, leaving a dead end in the lifecycle.

Maintenance

ActivityNo data
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • drop

    neuronik-io
    A
    license
    Not graded
    quality
    D
    maintenance
    Publishes HTML pages straight from your AI assistant to a shareable URL, then lets you manage them - update, list, search, fetch, and delete pages in a public or private workspace. Turns "share what I just made" into a single tool call from Claude, Cursor, or any MCP client.
    MIT

  • dochost

    zyli5313
    A
    license
    A
    quality
    C
    maintenance
    Publish Markdown or HTML to a shareable link from your AI assistant, then list, inspect, update or delete your pages. Six tools cover publishing, page management and account usage. Connect through hosted Streamable HTTP with OAuth, or use an API key for headless clients.
    6
    1
    MIT

  • shippage-mcp

    jieshu666
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to publish HTML or Markdown to a public URL with a single HTTP POST, automatically converting Markdown to a styled webpage, with no account or setup required.
    7 npm
    1
    MIT