PasteHTML MCP server

pastehtml.dev

Share HTML pages in seconds. Drop an HTML file, get a private link your friends can open, preview, and view the source of. Anonymous publishing still works, and accounts add folders, custom subdomains, view counts, browser-based re-upload updates, and account API keys for agent publishing into folders.

How it works

claimed custom subdomain like https://launch-plan.pastehtml.dev/ — with an inspector page (copy link, preview, highlighted source) at /p/. Tokens are random 32-character lowercase-alphanumeric IDs (~165 bits of entropy — lowercase because they double as subdomains, and browsers lowercase hostnames), so random links are private unless shared.

• Drag and drop (or browse for) an .html/.htm file up to 2 MB.
• The document is published at https://.pastehtml.dev/ — or at a

the inspector page, raw bytes, rendered preview, or live subdomain are served.

• Pastes can be password-protected. Locked pastes require the password before

replacement .html/.htm file without changing the share link. Pastes can never be deleted. API-created update tokens still work for token-based automated updates.

• Signed-in users can save pastes into folders, see view counts, and re-upload a

a Rouge-highlighted source view.

• The share page offers a live preview (with an in-site fullscreen mode) and

https://.pastehtml.dev/ — so scripts and localStorage work (review-progress checklists persist) while staying fully isolated from other pastes and from the app itself. The path-based /p//raw endpoint returns the paste's exact bytes as text/plain — a byte-exact copy for programmatic clients, immune to any CDN HTML rewriting in transit — while /p//render serves the same bytes as text/html inside a CSP sandbox.

• Every paste is served as a real page from its own origin —

Agent API

Publish without a browser — ideal for AI agents that produce design documents or implementation plans and want to hand back a share link. Anonymous publishing still works with no credentials; signed-in users can also create account API keys at /api_keys so an agent can publish into their account and target folders.

# Multipart upload
curl -F "file=@plan.html" https://pastehtml.dev/api/pastes

# Or stream the HTML straight from a pipe
curl --data-binary @plan.html -H "Content-Type: text/html" \
  "https://pastehtml.dev/api/pastes?filename=plan.html"

Anonymous creation returns 201 with { token, title, customsubdomain, folder, owner, accountpaste, passwordprotected, viewscount, liveurl, url, rawurl, renderurl, markdownurl, updatetoken } (or 422 with { errors }). Account-key creation returns the same paste fields but omits updatetoken; update account-owned pastes with the account key so revoking the key stops that agent's future access. Add password= (or customsubdomain=, which requires an account key) to creation/update requests; send clearpassword=1 on updates to remove a paste password. Fetch raw_url to read a paste's exact bytes back (text/plain, never rewritten in transit).

Account API keys for agents

A signed-in user can open API keys from the dashboard, create a key, and give that secret to an agent. Use it as either Authorization: Bearer pht... or X-PasteHTML-API-Key: pht.... When a valid account key is present on POST /api/pastes, the paste is owned by that user and appears in their dashboard. Folder targeting is account-only:

curl -H "Authorization: Bearer $PASTEHTML_API_KEY" \
  --data-binary @plan.html -H "Content-Type: text/html" \
  "https://pastehtml.dev/api/pastes?filename=plan.html&folder_name=Roadmap"

Shortened. The full README is on GitHub.