rtfx.pro

How to share Cursor-generated HTML privately

Add rtfx.pro to Cursor as a remote MCP server in mcp.json, ask the agent to publish the page, and share it with named people who sign in with an email code.

Updated 2026-11-06

Connect rtfx to Cursor

Cursor's docs put remote servers in mcp.json with a url key instead of a command. For rtfx, in ~/.cursor/mcp.json:

{
  "mcpServers": {
    "rtfx": { "url": "https://mcp.rtfx.pro/mcp" }
  }
}

Cursor supports OAuth for servers that need it, using the authorization code flow with PKCE. When it asks you to sign in to rtfx, use the code we email you.

Source: Cursor's MCP docs, read 2026-11-06.

Publish, share, update

  • Publish. Ask Cursor: Publish this page with rtfx as a private link. It replies with the link. The artifact is private to you, plus members of your team workspace if you publish to one.
  • Share. Ask: Share it with dana@acme.com. Dana signs in with a one-time code sent to her email; she needs no account with Cursor. For someone you would rather not add by name, create a named share link on the artifact's Share page, with an optional expiry of 1 to 365 days that you can extend or revoke.
  • See who opened it. The view log on the Share page records who, when and on what device.
  • Update. Publish again to the same name and the same link shows the new version; you can roll back.

Questions

Why does Cursor ask me to approve a publish?

Publishing creates something, so the rtfx publish tool is a write action, not a read-only one. Cursor's docs say it asks for approval before using MCP tools by default; click the arrow next to the tool name to see the arguments of a call. Listing artifacts and reading details or view statistics are marked read-only.

Can Cursor publish a whole built site?

Through the MCP server the agent sends the page contents. For a built folder or zip on disk, drop the zip into the rtfx dashboard in your browser (index.html at its root).

Do the people I share with need a Cursor account?

No. People you add by email sign in with a one-time code sent to their address, and a share link opens with no sign-in. They never need an account with the tool that made the page.

Can I see who opened the page?

Yes. Every artifact has a view log on its Share page: who opened it when signed in, which share link was used, when, and on what device. You can also ask the assistant who has opened it.

What does it cost?

There is a Free plan. Pro and Team add more artifacts, storage and people. rtfx staff see metadata only, never artifact content.

Share what Cursor built, privately.