Set up Thing in Hermes Agent
Give Hermes a publishing tool for the reports and documents it creates. This guide is for Nous Research’s Hermes Agent running on a machine you control.
Already connected? Publish your first artifact
Connect thing to Hermes
On the machine running Hermes, install Node.js LTS and sign in:
npx -y @unravel-tech/thing@latest login
Merge this server into ~/.hermes/config.yaml, preserving existing settings:
mcp_servers:
thing:
command: npx
args: ["-y", "@unravel-tech/thing@latest", "mcp"]Restart Hermes and ask it to call Thing’s whoami tool before publishing.
A login on your laptop does not authenticate Hermes on another host. For a headless host, provision THING_TOKEN through its secret environment; never paste tokens into a chat or commit them. Hermes MCP documentation.
Publish your first artifact
Paste this into Hermes. It creates a real artifact; no existing file is required.
The agent should return a Thing URL. Open it while signed in and confirm the report is there. Check Share before sending it: personal artifacts default private, and team artifacts default team-visible. Invite a person or choose the visibility you need.
For your next report, use the same name to add a version at the same URL.
Something not working?
Check npx --version, then run npx -y @unravel-tech/thing@latest whoami on the machine running your agent. If sign-in is missing, run npx -y @unravel-tech/thing@latest login there and restart the agent. For MCP, confirm Thing’s tools appear before asking it to publish. Never put credentials in a prompt or a committed config.
Not using Hermes for everything?
The same artifacts work from every other agent, and from CI. See artifacts for any coding agent for Claude Code, Aider, Cline, shell tools, and pipelines, and for why a page that outlives the session it came from is worth the extra step of publishing.