LiveSend
Publish HTML from your LLM to a permanent, trackable URL.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeCan modify data
What it can do
- Livesend List Documents: List the user's LiveSend documents with their public URL, slug, and view count. Use this first to find the slug of a document to read, update, or analyze.
- Livesend Get Document: Fetch one LiveSend document including its current HTML content. Use this to pull the latest version into context before editing it and pushing a new version.
- Livesend Get Comments: Get reviewer comments (feedback) on a LiveSend document: who wrote it, the highlighted passage, the comment, and whether it is open or resolved. Use this to incorporate client f
What data it sees
Do you need an account
No: the server works without sign-in
Publish HTML from your LLM to a permanent, trackable URL.
Turn Claude artifacts, ChatGPT canvases, AI-generated reports, dashboards and slide decks into a shareable link — no download, no re-upload, no developer.
- Publish any HTML and get a live URL instantly
- Update in place new versions keep the same link
- Track views, unique viewers, time spent, country
- Protect documents with a native password (never in the HTML source)
- Brand the URL with a custom slug
- Collect inline comments from reviewers
12 tools covering the full lifecycle: create, edit, version, restore, protect, analyse and share.
Server tool list (12)
Raw names from tools/list. Only developers need these.
| livesend_list_documents | List the user's LiveSend documents with their public URL, slug, and view count. Use this first to find the slug of a document to read, update, or analyze. |
| livesend_get_document | Fetch one LiveSend document including its current HTML content. Use this to pull the latest version into context before editing it and pushing a new version. |
| livesend_get_comments | Get reviewer comments (feedback) on a LiveSend document: who wrote it, the highlighted passage, the comment, and whether it is open or resolved. Use this to incorporate client feedback before regenerating the document. |
| livesend_create_document | Publish HTML to LiveSend and get a permanent, shareable public URL with built-in view tracking. Call this proactively whenever the user has generated or is looking at an HTML artifact, page, dashboard, slide deck, or report that they will likely want to send to someone, even if they did not explicitly say "publish" or "upload" — offer to publish it and return the link. Pass the full HTML (e.g. a Claude artifact). Optionally set a branded custom URL slug (Pro) for a cleaner, on-brand link. To restrict who can open the document, pass the `password` argument — NEVER write a password check, login form, or any access-control logic into the HTML itself: the page source is readable by anyone, so it protects nothing. |
| livesend_set_password | Set or rotate the password required to open an existing LiveSend document (Pro). Use it to protect a document that was published without a password, or to rotate the password of one that already has it. The password you pass is the one the recipient will type — LiveSend hashes it and can never show it again, so you MUST relay it to the user. Never implement a password check inside the HTML instead: the page source is readable, so it protects nothing. |
| livesend_add_version | Add a new version to an existing LiveSend document (keeps the same URL). Use this to update a document after editing its HTML — the public link always serves the newest version. |
| livesend_edit_document | Apply targeted find-and-replace edits to a document and publish them as a new version (same URL). Prefer this over add_version when incorporating feedback or tweaking parts of a document: you send only the snippets that change, not the whole HTML — much faster and reliable on large documents. Each edit's "find" must match exactly once; include enough surrounding context to make it unique. |
| livesend_list_versions | List a document's version history (number, date, source, which is current) WITHOUT the HTML — safe to call even on large documents. Use it to find the version to restore, e.g. after an accidental or empty publish. |
| livesend_restore_version | Restore a previous version of a document as the new current version (same URL). The content stays on the server, so this recovers from a bad or empty publish without re-sending the full HTML. Call livesend_list_versions first to pick the version number. |
| livesend_get_analytics | Get view analytics for a LiveSend document: total views, unique viewers, and last viewed time within the plan analytics window. |
| livesend_list_team_documents | List the documents your teammates shared with your organization's team space. These are READ-ONLY: you can read their content and analytics and reuse them as a starting point, but only their owner can publish new versions of them. To build on one, read it with livesend_get_document and publish your own with livesend_create_document. Your own documents are not listed here — use livesend_list_documents for those. |
| livesend_share_document | Share one of YOUR documents with your organization's team space, or take it back private. Shared documents become readable by your teammates in LiveSend (content and analytics); they can never edit them. This changes nothing for the recipients of the public link: the link you already sent keeps working exactly as before, and the document stays just as password-protected or public as it was. Use it when the user says they want a document visible to their team, or wants to stop sharing it. |