How to share a Claude artifact privately (and see who opened it)

Yogev Gabrielovitch — Wed, 04 Nov 2026 14:00:00 +0000

Claude is great at making things you want to send to someone: a client draft, a one-page report, a prototype. Sending it privately is the awkward part.

What Claude's own sharing does

Claude artifacts start private. From the Share menu you can open one to anyone with the link, invite people by email, or (on Team and Enterprise) share it inside your organization. But according to Anthropic's help article on sharing artifacts, everyone who opens a shared artifact needs a Claude account, even with the link. The exceptions are legacy artifacts published from a chat, and Claude Code artifacts shared as a public link. Those open for anyone who has the link, which also means anyone it gets forwarded to.

So you either ask your client to sign up for Claude, or you send something public. The help article doesn't describe expiring links or a log of who opened it.

Adding a private link with an MCP server

I built rtfx.pro for the case in between. It's a remote MCP server, so Claude can publish to it directly:

Connect once. In Claude: Customize → Connectors → Add custom connector, URL https://mcp.rtfx.pro/mcp. Sign in with a code sent to your email; there's nothing to paste. In Claude Code:

  claude mcp add --transport http rtfx https://mcp.rtfx.pro/mcp

Publish. Ask Claude: "publish it with rtfx as a private link." You get a link that only you can open until you share it. (If you publish into a team workspace, its members can open it too.)

Sharing by name, or by link

By name: "Share it with dana@acme.com." Dana signs in with a one-time code sent to that address. She needs no Claude account and no password. Remove her any time without affecting anyone else.
By share link: for someone you'd rather not add by email, create a named share link on the artifact's Share page. It opens with no sign-in, can expire after 1 to 365 days, and can be revoked on its own.

Why no shared password? A password can be forwarded, nothing records who it went to, and shutting one person out means changing it for everyone. Per-person sign-in avoids all three.

Seeing who opened it

Every artifact has a view log: who opened it if they were signed in, which share link was used if not, when, and on what device. You can also just ask Claude "who has opened q3-report?"

Updating without sending a new link

Publish again under the same name and the same link shows the new version. Earlier versions are kept, and you can roll back from chat.

Not using Claude's connectors?

You don't have to connect anything. Sign up at rtfx.pro and drop a .html page, a .pdf or a .zip (with index.html at its root, up to 50 MB) into the dashboard, or paste the HTML Claude wrote. Sharing and the view log work the same way.

Open source

The whole thing runs on Cloudflare Workers, and the source is MIT on GitHub, including the security model if you want to check how access works. There's a free plan; Pro is $12/month.

If you share things Claude makes, I'd love to hear what's missing.

rtfx.pro is on Product Hunt today, if you'd like to follow along or leave feedback there.

DEV Community: Yogev Gabrielovitch