Your docs
in every Hermes chat

Hermes Agent, from Nous Research, talks to you in the terminal or in Telegram, Discord, Slack and WhatsApp. MCP (Model Context Protocol) lets it call tools on another server. Each public Revdoku docs site has a read-only MCP server at /mcp, with no sign-in.

1. Add this block to ~/.hermes/config.yaml:

   mcp_servers:
     acme_docs:
       url: "https://docs.example.com/mcp"

2. In a running Hermes session, send /reload-mcp.
3. Ask: “Use the Acme docs. How do I create an API key?”

The entry has no auth line, because the docs server needs no sign-in. Hermes names each tool with a prefix: mcp_acme_docs_search_docs, mcp_acme_docs_read_page and mcp_acme_docs_list_pages. A running Hermes gateway reads most changes in config.yaml without /reload-mcp.

The MCP server of your Revdoku account uses browser sign-in. With it, Hermes reads your support tickets and the status of your docs sites. Choose this route when Hermes does not have to upload local files.

1. Add the revdoku entry to ~/.hermes/config.yaml, next to the docs site:

   mcp_servers:
     acme_docs:
       url: "https://docs.example.com/mcp"
     revdoku:
       url: "https://mcp.revdoku.com"
       auth: oauth
       tools:
         exclude: [bucket_delete_permanently, bucket_ticket_message_delete, bucket_file_delete]

2. Run hermes mcp login revdoku. Hermes prints a sign-in URL and opens your browser when it can.
3. On the Revdoku permission screen, select the buckets for Hermes. Choose Read only for digests. Choose Read & write if Hermes must reply, or Full access if it must publish.
4. If Hermes runs on a server without a browser, copy the final redirect URL from your browser. Paste it at the Hermes prompt.
5. In a running Hermes session, send /reload-mcp.

Hermes keeps the token in ~/.hermes/mcp-tokens/revdoku.json. The exclude list hides the three delete tools from the agent. A bucket holds the files of one docs site, the site and its support tickets. If a bucket gets its files from GitHub, change the docs in the repository. The Edits in Revdoku setting of the bucket decides what happens to an edit that Hermes makes in Revdoku: it waits for a person, becomes a commit, or Revdoku refuses it.

Hermes keeps skills (folders of task instructions and scripts) in ~/.hermes/skills/. It can install a skill straight from a path in a GitHub repository. The Revdoku skill is at skills/revdoku in the public revdoku/revdoku repository. It comes with the Revdoku command-line tool, which can also upload a docs folder and publish the site. Create a Revdoku account before you start.

1. Preview the skill files: hermes skills inspect revdoku/revdoku/skills/revdoku
2. Install the skill: hermes skills install revdoku/revdoku/skills/revdoku
3. In a Hermes chat, send this slash command: /revdoku list my buckets and the address of each docs site
4. The first Revdoku command prints a sign-in link. Open it on any device and select Connect.

Hermes scans every skill from a GitHub path with its security scanner. A repository outside its trusted list, such as revdoku/revdoku, gets the community trust level. If a chat is open during the install, your next message names the new skill. You do not have to restart Hermes.

If you use the skills CLI from npm, the agent name for Hermes is hermes-agent: npx skills add revdoku/revdoku --skill revdoku -g --agent hermes-agent

• Answer a question from your team in Telegram or Slack with the matching docs page and its link.
• Read new support tickets and name the docs page that answers each question.
• List the questions that no page answers, so you know which page to write next.
• When you ask, reply to the person who wrote. Revdoku adds the reply to the conversation of the original email.
• With the skill, upload a docs folder and publish the site, for a bucket without a GitHub link.

Hermes cron (its scheduler for recurring jobs) runs agent jobs inside the Hermes gateway, so the gateway must be running. A job that you create in Telegram sends its result back to that chat. This job searches the docs through the acme_docs server.

/cron add "weekdays at 8am" "Read the support tickets of my Revdoku bucket that changed in the last 24 hours. Give each one a one-line summary. Search the Acme docs and name the page that answers it, or say that no page answers it. Do not reply to or delete anything." --skill revdoku

In the terminal, the same job starts with hermes cron create, followed by the same schedule, prompt and --skill revdoku. Add --name "Support digest" to label it. The terminal version saves its output in ~/.hermes/cron/output/.

Hermes compares each shell command with a list of dangerous patterns before it runs it. In the default smart mode, a helper model approves low-risk commands, denies dangerous ones and asks you about the rest. For a prompt on every dangerous command, set approvals.mode to manual in config.yaml.

A cron job reads new support tickets when you are not at the screen. The Revdoku skill tells Hermes that email bodies and attachments are untrusted data, and Hermes must not follow instructions in them.

To remove the skill, run hermes skills uninstall revdoku. To remove an MCP server, delete its block from config.yaml and send /reload-mcp. You approve each Hermes connection to your account separately in Revdoku, under Account → Access.

Hermes skills · Hermes MCP · Hermes cron · Hermes security · Docs for AI agents · Revdoku MCP guide