ANHA in Hermes
Hermes keeps MCP servers in a YAML config file and reloads them from inside the agent.
Install
Open the config file
Create ~/.hermes/config.yaml if it is not already there.
Path~/.hermes/config.yamlAdd ANHA
Add an mcp_servers block. YAML is indentation-sensitive, so keep the two-space indents exactly as shown.
~/.hermes/config.yamlmcp_servers: anha: command: npx args: ["-y", "anha-mcp"]Load it
Run this inside Hermes to reload the server list.
In Hermes/reload-mcpSign in
Approve the handle you want Hermes to act for.
Terminalnpx -y anha-mcp login
Test
Check the server list
After reloading, Hermes lists ANHA among its servers.
/mcpYou should see
anha loaded 8 toolsThen ask for something real
A passing check only proves the connection works. This proves the model can actually reach the tools.
“Use ANHA to resolve @nike.ai and tell me what it can do.”
Troubleshoot
- Hermes reports a config error on start
Cause — The YAML indentation is wrong — tabs instead of spaces is the usual cause.
Fix — Replace every tab with two spaces. YAML rejects tabs outright.
- The tools are listed, but every call answers that you are not signed in
Cause — The browser approval was closed before it finished, or you approved with an email address that owns no handle.
Fix — Run npx -y anha-mcp login again and sign in with the same email you registered the handle under. If you have no handle yet, register one first — the approval screen has nothing to offer otherwise.
- npx: command not found, or the package will not install
Cause — Node.js is missing or older than v20, so npx is unavailable or refuses anha-mcp.
Fix — Run node --version. Below v20, install the LTS build from nodejs.org and open a new terminal so the new PATH takes effect.
- An order or payment just hangs
Cause — This is not a fault. The merchant requires phone approval, so the call returns a pending status with a request id.
Fix — Approve it on your phone. A human decision can take minutes, and the caller polls until it lands.
Still stuck?
Every guide shares the same sign-in and the same tools, so a fix on another platform often applies here too.