rtfx.pro

Remote MCP server for Claude: publish pages, PDFs and small sites to a private link only the people you choose can open. Share with viewers or editors, see who opened it, roll back versions. OAuth sign-in, free plan, MIT open source.

View on rtfx.pro

Hosted MCP Server

npx add-mcp 'https://mcp.rtfx.pro/mcp'

Installs into Claude Code, Codex, Cursor and more

Documentation

Publish from Claude to a private link.

rtfx.pro is an MCP server. Connect it to Claude once, then ask Claude to publish, share or delete what it made — each artifact gets a private link only the people you choose can open.

https://mcp.rtfx.pro/mcp

Connect to Claude Start free

Already have an account? Sign in

One minute: connect, publish, share, see who opened it. Step by step with screenshots →

1. Add rtfx to Claude

Claude on web, desktop and mobile

  1. Open Customize → Connectors (or Settings → Connectors), click + Add, then Add custom connector.
  2. Name it rtfx and use the URL https://mcp.rtfx.pro/mcp.
  3. Keep the detected defaults and click Add, then Connect.
  4. 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.

See every step with screenshots →

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>.

2. Publish

  • Publish this as a private link. Claude replies with your link, like https://rtfx.pro/your-workspace/q3-report. It is private to you until you share it.
  • Publish the fix to the same link. A new version at the same URL. Roll back to version 2. The link points at the earlier version again.

For big sites or images, Claude gives you an upload link instead. See it step by step →

4. Delete

  • Delete q3-report. Claude confirms the exact name first, then it's gone: every version, the link and its share links. This can't be undone.

You can also delete it from the artifact's page on rtfx.pro.

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 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 Publish enough?

On Free, Pro and Max plans, Claude's own Publish makes an artifact public to anyone with the link (on Team and Enterprise it is limited to your organization). rtfx is for when you want only the people you choose to open it: every artifact is private by default. 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.

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, Team and Enterprise are for more artifacts, storage and people. See the pricing section below for the limits.

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 Start free

Pro

$12/mo

  • Dedicated URL for every artifact
  • Branded workspace address
  • 100 artifacts
  • 5.0 GB storage
  • Full version history
  • Up to 3 people Start free, upgrade anytime

What Pro is →

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 Talk to us

What Team is →

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 Talk to us

What Enterprise is →

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.