Respira now supports Hermes Agent

On 18 August, two Respira customers connected Hermes Agent to their WordPress sites. Nobody had told them it was supported, because it was not.

It worked anyway. The MCP server takes the client name a tool declares about itself and passes it through untouched, so an agent it has never heard of gets treated like any other agent. It signs in, it reads, it writes, and every change lands in the activity log under the name it gave. Between them the two customers edited posts, pages and custom posts. Nothing broke, and i found out afterwards.

So today it is official rather than accidental.

What Hermes Agent is

Hermes Agent is an open-source CLI and desktop agent from Nous Research, MIT licensed. It keeps its MCP servers in ~/.hermes/config.yaml under an mcp_servers: key, and it can run one either as a local command or as a remote server it signs into over OAuth. Both shapes reach a WordPress site through Respira, and which one you want depends on whether you would rather hold a key on disk or a browser session.

What changed today

Hermes now sits alongside Claude Code, Cursor, Codex and the rest in the client list on respira.press/mcp, and it has its own entry on the setup page in your dashboard, which is where the buttons and the filled-in config live. Picking it gives you three routes in, plus a shortcut if another agent is already configured on the same machine.

Three ways to connect

Add to Hermes, in one click. The setup page in your dashboard gives you a button. It opens a hermes://mcp/install link, which the desktop app catches and turns into a confirmation dialog naming the server it is about to add. Nothing installs silently, and closing the dialog installs nothing. The link carries your whole account, so every connected site arrives at once. There is a ceiling worth knowing: Hermes refuses an install payload over 32KB, and a large enough fleet crosses it. When that happens the dashboard tells you and points at the config file, rather than handing you a link that would fail in the app with no explanation.

Sign in per site, with no key on disk. Hermes can also talk straight to the MCP endpoint your site already runs, at https://yoursite.com/wp-json/respira/v1/mcp with auth: oauth under it. Hermes handles the whole handshake itself, discovery through registration, PKCE and refresh, and sends you to your browser to approve it. That is one entry per site, because the endpoint lives on the site, so the config the dashboard hands you ships those entries commented out, one line per connected site, ready to uncomment. Then run hermes mcp login with the name you picked.

One config for every site. The third route is the local server: npx, the Respira MCP package, and your account registry passed in an environment variable. One server definition covers the fleet, and the agent moves between sites with the site tools instead of you keeping a block per site. The setup page in your dashboard gives you the YAML to paste into ~/.hermes/config.yaml. Merge it under mcp_servers: and keep any servers you already have there.

If Claude Code is already set up on the same machine you can skip all three. Run hermes import-agent claude-code and Hermes copies the existing server block across for you.

Who did what, afterwards

Connections made this way show up as Hermes Agent in your Respira dashboard and in each site's activity log, next to every change made through them. Attribution is per client, so a site edited from both Claude Code and Hermes reads back as two names instead of one blur. That was the part i wanted in place before saying the word supported: a connection you cannot account for later is not really supported, it just works.

Where to go next

• Hermes Agent and WordPress, for what it does and what it costs.
• Managing WordPress through Hermes Agent, for the walkthrough with the actual config.
• The setup page in your dashboard, if you already have Hermes installed and just want the button.