Configure the remote server
Hermes Agent reads MCP servers from ~/.hermes/config.yaml. Add Home MCP as a
remote HTTP server and use the client’s OAuth flow instead of a static token.
mcp_servers:
hombee:
url: https://your-public-home-mcp-url/mcp
auth: oauth
- Save the configuration and restart Hermes Agent.
- Run
hermes mcp login hombee. - Complete Hombee authorization in the browser.
- Review the tool list. Use Hermes tool filtering to expose only the Home MCP capabilities needed for the task.
On a remote or headless host, follow Hermes’ documented paste-back or SSH forwarding flow. Treat the returned authorization URL and redirect address as sensitive. Never paste a browser session or refresh token into the YAML file.
Verify Home Assistant from Hermes Agent
Ask: “Use hombee to list the Home Assistant areas available to me and explain
which tools are read-only. Do not change state.” Keep approval enabled for any
operation that controls a device, changes security, runs an automation or sends
data outside the installation.
If hermes mcp login does not recognize the server, check YAML indentation and
the configured name. If authentication works but discovery is empty, restart the
agent and verify the Hombee user and installation. A narrower tool set can be
correct: Home MCP matches tools to the account, modules and available
capabilities.


