Turn Claude's work into a private link you can send.
You asked Claude for the proposal, the report, the dashboard. Ask it to publish, and you get back one secure link only the people you name can open — kept up to date as you change it, with an email the first time each named person reads it.
One email code creates your workspace. No password, no card for Free. Sign in if you already have an account.
Already know you want it? Setup takes about two minutes →
Ask Claude to make it
A proposal, a board report, a research dashboard, a working prototype — whatever you were going to send anyway.
Ask Claude to publish it
One sentence, in the same session that made it. Nothing to build, deploy or set up.
Send one link
Only the people you name can open it. To everyone else the page simply doesn't exist.
Watch it land
You're told the first time each person opens it — and when you publish a change, the link you already sent shows it.
What people send with it
For the things you'd otherwise email as an attachment.
You don't have to be a developer. If Claude can make it, rtfx.pro can put it behind a link that belongs to you.
Send a client a private preview
A proposal, a mockup, a draft page. One link, opened only by the people on that account — not by whoever it gets forwarded to.
Share a report or a PDF
Board packs, analyses, monthly numbers. They live at a real address instead of in an inbox, and you can see who actually read them.
Hand over a research dashboard
The chart-heavy page Claude built out of your data. It stays live at its link for the people who need it, instead of being a screenshot in a deck.
Show an app prototype
A one-page site, a working demo, a clickable flow. It runs at its link straight away — no hosting account, no deploy, no domain to buy.
Update it without resending
Publish again and the link you already sent shows the new version. Nobody needs a new URL, and nothing you shared before is lost.
Know it was read
The first time each person you named opens it, you get an email. The rest — when, how often, which version they saw — is on the artifact's own page.
Inside the session
You don't learn a tool. You finish the sentence.
Once Claude is connected, publishing, updating and rolling back are things you ask for in the same conversation that produced the work.
Publish this as a private link.
Claude puts it on rtfx.pro and hands back the link. It's restricted to you until you say otherwise.
Give me the link for Dana.
Claude hands back the artifact link; you decide access from rtfx so only the right person can open it.
Publish the fix to the same link.
A new version at the address you already sent. The old ones stay, so a bad revision is an undo.
Roll it back to version 2.
The link points at the earlier version again — no re-export, no second URL, no email that starts “ignore the last one”.
Control & evidence
A link that stays yours.
Who can open it. Every artifact is access-protected from the moment it exists. You share it with named people, by identity — they open it with their own email sign-in, so there's no password to pass around. Everyone else gets the same 404 as a page that was never published, so a forwarded link gives nothing away.
For someone who'll never have an account. Create a share link instead. Whoever holds that URL can open this one artifact with no sign-in; you can expire it on a date you choose, and revoke it the second the project ends.
What you can see. You're emailed the first time each person you named opens it. The view log has the rest: who, when, from which country, and which version they were looking at.
What happens when you change it. Publishing again keeps the same link and adds a version. The version history stays, so going back is one click.
Where it lives. Your work belongs to a workspace you can add people to, and nothing you publish is indexed by a search engine.
- Restricted private until you say otherwise
- Shared with 2 named people, by identity
- Share link expires in 30 days · revoke any time
- v4 v1–v3 still there · roll back in one click
- Viewed alex@example.com · 2 min ago · v4
Setup
Two clicks, or two commands. Once.
Add rtfx to the Claude you already use, sign in the one time, and every session after this one can publish.
rtfx.dxt, open it, sign in once.
/plugin install rtfx@rtfx then /rtfx:login.Add it in a few clicks
- Download rtfx.dxt.
- Open the file — Claude Desktop installs the rtfx connector.
- Connect your account once: a browser sign-in, nothing to paste.
- Ask Claude: “publish this as a private link.”
It runs on your own computer, so Claude can publish a file or folder you point it at. Full Claude Desktop steps →
Two commands in the terminal
/plugin marketplace add yogevgab/artifacts-server
/plugin install rtfx@rtfx
/rtfx:login browser sign-in — no token to copy
/rtfx:publish ./out client-demo
https://rtfx.pro/client-demo/ · v1After that, publish this is an ordinary sentence in the session. Full Claude Code steps →
Under the hood
Connect Claude once. Publish for the rest of the project.
Four ways in, for whichever Claude you work in. The first three are the two cards above plus a hosted endpoint that needs no install; the API is there for CI.
The Claude Code plugin
/plugin install rtfx@rtfx
/rtfx:login
/rtfx:publish ./out client-demoOne browser sign-in connects the session, and there is no token to copy, paste or leave sitting in a shell profile. After that publish this is an ordinary sentence: the session picks the build output, versions it under a slug and hands back the link.
The local MCP server
tools: publish
list_artifacts
get_versions
rollback · doctorBundled in the same plugin, so a client with no shell — Claude Desktop, or anything else that speaks MCP — publishes as a tool call. It runs beside your files, which is exactly why it can send the build output you point it at.
Remote MCP, authorized by OAuth
claude mcp add --transport http rtfx https://mcp.rtfx.pro/mcp
claude mcp login rtfx
tools: publish · doctorA hosted endpoint your client authorizes in the browser — authorization code with PKCE, no bearer token to paste. It publishes content sent inside the tool call — an HTML page, a PDF, or a small explicit file list — and runs doctor for connection checks. It never reads a filesystem path; larger folders still belong to the plugin and local server above.
API, CLI and Hermes
POST /api/machine/artifacts
Authorization: Bearer rtfx_…The advanced paths, for CI and scripted work: a scoped, revocable token against the HTTP API, the CLI out of a checkout of the repository, or a Hermes run. Same endpoints and same rules as every other route — an agent path here is never a weaker one.
Publishing happens in two ways: local connectors read files beside the client, while the hosted MCP endpoint publishes content bytes sent inside the tool call. It never reads a path on the server. Every connector, side by side →
Going deeper: who uses it and for what · what agent-native publishing means · why not a generic static host · every way to connect · FAQ
Pricing
Free to start. Upgrade only if you outgrow it.
Every workspace starts on Free, and Pro is a switch inside Settings. Team and Enterprise are set up with a person, because the parts that would make them self-serve aren't built yet.
Free
Free
- Dedicated URL for every artifact
- 10 artifacts
- 100.0 MB storage
- Keeps the last 5 versions of each artifact
- 1 person
Pro
$12/mo
- Dedicated URL for every artifact
- Branded workspace address
- 100 artifacts
- 5.0 GB storage
- Full version history
- Up to 3 people
Team
$40/mo
- Dedicated URL for every artifact
- Branded workspace address
- 10,000 artifacts
- 50.0 GB storage
- Full version history
- Up to 25 people
Enterprise
Talk to us
- Dedicated URL for every artifact
- Branded workspace address
- Everything in Team, plus a conversation
- SSO, SCIM and contractual SLAs — none built yet
- Security review, DPA, invoicing
- 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.
Start free
One email code creates your workspace. Upgrade later only if you outgrow the free limits.
No password and no card for Free. Paid upgrades happen in Settings once you're inside. Setup takes about two minutes, and the privacy policy has the data model.