How to share Hermes Agent HTML privately
Add rtfx.pro to Hermes Agent as a remote MCP server with OAuth, log in once, and publish pages to private links you can share with named people.
Connect rtfx to Hermes Agent
Hermes' docs configure remote servers in ~/.hermes/config.yaml. For rtfx:
mcp_servers:
rtfx:
url: "https://mcp.rtfx.pro/mcp"
auth: oauth
Then run hermes mcp login rtfx. The docs say Hermes handles discovery, client
identification, PKCE, token exchange and refresh; your part is approving in the browser (Hermes never
opens it by itself: click Open in browser in Desktop, or press Enter in the terminal). Sign in
with the code we email you. On a headless host the docs list alternatives such as
hermes mcp login rtfx --flow device if the authorization server supports it.
Source: Hermes Agent's MCP docs, read 2026-11-06.
Publish, share, update
- Publish. Ask Hermes Agent:
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 Hermes Agent. 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
Does Hermes ask me to approve a publish?
Hermes' docs say that on a server set to trust: untrusted, write-capable calls ask for approval. Publishing is a write action in rtfx.
I added the server from inside a running session and sign-in timed out.
Hermes' docs say to run hermes mcp login from a fresh terminal after adding an entry in a session, because the config auto-reload timeout is too short for OAuth.
Do the people I share with need a Hermes Agent 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.