Publish from Claude to a private link.
Share reports, prototypes and client drafts with exactly the people you choose. They don't need a Claude account, and you see who opened each one — by name, or by the link they used.
rtfx.pro is an MCP server for Claude — web, desktop, mobile and Claude Code. Free plan, no card.
Client proposal
Privatertfx.pro/acme/client-proposal
Who can open it
- dana@example.comViewer
- alex@example.comEditor
- Link “Board preview”Expires in 7 days
Recent views
- dana@example.comMac · 2 min ago
- Link “Board preview”iPhone · 1 h ago
Three ways to share
Named people
Each person signs in with a one-time code we email them. No password, no Claude account.
Your workspace
Members of a team workspace can open what's published to it. Viewers read; members can publish new versions.
Share links
Anyone holding the link can open it without signing in. Name it, set an expiry, revoke it any time.
Every artifact is private when it is published: only you, and members of its workspace if it belongs to a team, can open it. Signed-in opens show who it was; share-link opens show which link was used.
How it works
Connect Claude once
Add rtfx as a custom connector in claude.ai or Claude Desktop — it then works on mobile too — and sign in with an email code.
Ask Claude to publish
Publish this as a private link.
You get a link that stays private until you
share it.
Share, then see who opened it
Share it with dana@acme.com.
Later: Who has opened it?
— or open its view
log.
https://mcp.rtfx.pro/mcp
Connector steps for Claude on web, desktop and mobile
- Open Customize → Connectors (or Settings → Connectors), click + Add, then Add custom connector.
- Name it
rtfxand use the URLhttps://mcp.rtfx.pro/mcp. - Keep the detected defaults and click Add, then Connect.
- Sign in with the code we email you, then Allow.
Once added, it works in Claude on web, desktop and mobile. The consent screen lists “Manage access and delete artifacts” — allow it so Claude can share and delete from chat.
Claude Code and other MCP clients
Any client with remote MCP and OAuth connects the same way, with nothing to paste. It asks for read and publish by default; it must also request rtfx:manage to share and delete from chat.
claude mcp add --transport http rtfx https://mcp.rtfx.pro/mcp
{"mcpServers":{"rtfx":{"url":"https://mcp.rtfx.pro/mcp"}}}
No OAuth in your client? Create a token under Settings → Integrations
(rtfx.pro/admin/integrations) and send it as
Authorization: Bearer <token>.
Keep control after you share
- Update at the same link
Publish the fix to the same link.
Every publish is a new version; the link always shows the latest. For big sites or images, Claude gives you an upload link. - Roll back
Roll back to version 2.
The same link shows the earlier version again. - Delete it
Delete q3-report.
Claude confirms the name first, then every version, the link and its share links are gone for good.
Pricing
Start free. Choose more room when you need it.
Every plan includes private links, sharing controls, a dedicated URL and a view log for every artifact. Pro and Team are billed monthly per workspace — one email code, then checkout.
Free
Free
- 10 artifacts
- 100.0 MB storage
- Keeps the last 5 versions of each artifact
- 1 person
Pro
$12/mo
- Branded workspace address
- 100 artifacts
- 5.0 GB storage
- Full version history
- Up to 3 people
Team
$40/mo
- Branded workspace address
- 10,000 artifacts
- 50.0 GB storage
- Full version history
- Up to 25 people
Enterprise
Talk to us
- Everything in Team, plus a conversation
- Security review, DPA and invoicing
- Not available yet: SSO, SCIM, contractual SLAs
- Or self-host it: the source is MIT
Limits are per workspace, not per person. Storage counts every version you've kept, which is why Free keeps your last 5 and the paid plans keep every one.
Questions
How do I share a Claude artifact privately?
Add rtfx.pro to Claude as a custom connector (https://mcp.rtfx.pro/mcp), then ask Claude to publish your artifact. You get a private link that only you (and your workspace, if it is a team's) can open. Then ask Claude to share it with named people as viewers or editors, or with everyone in your workspace. For someone without an account, create a named share link on the artifact's Share page; it can expire, and you can extend or revoke it any time. Read more →
Isn't Claude's own sharing enough?
Claude can share an artifact with anyone who has the link — then anyone it's forwarded to can open it too — or with people you invite by email, who each need a Claude account. Claude's help article doesn't describe expiring links or a view log. rtfx is for sharing with exactly the people you choose — no Claude account needed — and seeing who opened it. Read more →
Does it work with Claude Desktop, claude.ai, mobile, Claude Code and other MCP clients?
Yes. rtfx.pro is a remote MCP server. Add it once in claude.ai on the web or in Claude Desktop (Customize → Connectors → + Add → Add custom connector, with the URL https://mcp.rtfx.pro/mcp) and it is available in the Claude mobile apps too. In Claude Code, run: claude mcp add --transport http rtfx https://mcp.rtfx.pro/mcp. Other MCP clients connect with the same URL. Sign-in is OAuth, so there is nothing to paste. Connecting is optional: you can also sign up and publish from the dashboard in your browser by dropping an HTML file or pasting HTML.
Who can see my artifacts?
You, the people you add (or everyone in your workspace, if you choose), and anyone holding a share link you created. rtfx staff (operators) see metadata only, never artifact content or who viewed it.
Can I see who opened an artifact?
Yes. Each artifact has a view log on its Share page showing who opened it and when. You can also ask Claude who has opened it.
Can I update an artifact without sending a new link?
Yes. Publish again under the same name and the same link shows the new version. Each publish is a new version, and you can roll back to an earlier one from chat.
Is it free?
There is a Free plan; sign up with your email. Pro is $12/mo and Team is $40/mo, both bought right here on the site (email code, then checkout); Enterprise is a conversation. See the pricing section below for the limits.
Open source (MIT) — read the code or self-host it rtfx staff see metadata only, never your content Privacy · Terms