commentable<html>
New · Claude connector

Claude writes it.
commentable ships it.

Add commentable to Claude as a custom connector. Then just ask — Claude publishes the HTML it wrote as a private, end-to-end-encrypted link your team can comment on. No copy-paste, no leaving the chat.

claude.ai
+ New chat
Here is your dashboard:
Q3 Revenue · Kestrel

Want me to publish it as a commentable link for your team?

Yes. Expire in 30 days, no password.
✓commentable · create_commentable_link
Published with your branding:share.acme.studio/a/k3mX9pQr#key=aG9wZQ
# design-review Dana, Sam, Mia + 9
Y

You 2:41 PM

Q3 dashboard is live — comments welcome 👇

Q3 Revenue · Kestrel

share.acme.studio · end-to-end encrypted

Open the live page →

share.acme.studio/a/k3mX9pQr
Acme Studio💬 0
Q3 Revenue · Kestrel v2
DDana · Q3 target line here?
SSam · love this trend 🔥
MMia · swap axis labels
v2 published — the link never changed
Feedback in minutes. On the work itself.
Same link. Every version.

commentable <html>

commentable <html>

Share HTML artifacts as live, commentable links.

html.commentable.link

The whole flow: build in Claude, answer expiry and password, get your branded link, and watch the comments land. Claude always asks before publishing — you stay in control.

Setup

Two minutes, three steps.

  1. 01

    Create your API key

    Sign in and open your dashboard → Claude connector → New API key. Copy the key — it's shown only once. It links published pages to your account, and you can revoke it anytime.

  2. 02

    Add the connector in Claude

    On claude.ai (Pro, Max, Team, Enterprise)

    SettingsConnectorsAdd custom connector
    Add custom connector✕
    commentable
    paste your URL here
    https://html.commentable.link/api/mcp?key=YOUR_API_KEY
    CancelAdd

    Copy your connector URL below and paste it into that Remote MCP server URL field — your key from step 1 is already baked in:

    https://html.commentable.link/api/mcp?key=YOUR_API_KEY

    Recommended:after connecting, open the connector's settings and set the Publish HTML as a commentable link tool to Always allow— so publishing doesn't pause for approval every time. Then start a new conversation so Claude picks up the connector.

    In Claude Code

    Prefer the terminal? Run this one command — it fills in your key for you:

    claude mcp add --transport http commentable "https://html.commentable.link/api/mcp?key=YOUR_API_KEY"
  3. 03

    Just ask

    “Create a commentable link for this page.” Claude asks about expiry and an optional password, publishes, and drops the live link into the chat. The page appears in your dashboard like any other — comments, notifications, and Update HTML all work.

Still end-to-end encrypted.

Each publish generates a fresh AES-256-GCM key that lives only for the duration of the request — it's embedded in the link's #fragment and never stored or logged. Our database only ever holds ciphertext.

Your API key authorizes publishing under your account — it can't read existing pages, and you can revoke it in the dashboard at any time.

Treat the connector URL like a password: it contains your key.

Which Claude plans support this?

Custom connectors are available on Claude Pro, Max, Team, and Enterprise. Claude Code works on any plan that includes it.

Can I update a published page later?

Yes — open it and hit Update HTML. The link (and everyone who has it) stays the same.

Does Claude decide the expiry or password?

No. The connector instructs Claude to always ask you both questions before publishing.

What if my API key leaks?

Revoke it in the dashboard — the connector stops working instantly. Already-published pages are unaffected.

From prompt to feedback in one message.

Get your API key