Hermes is a full MCP client, so it talks to AgentValet the way it already talks to any MCP server. Connect it over OAuth and the agent is issued an identity, not raw credentials - then every platform call runs through scoped credentials, deny-by-default rules, and a full audit trail. This integration is in beta. The connect flow is proven; want early access? Talk to us.
In the AgentValet dashboard, the Add to Hermes action builds your connection snippet from your
owner id alone. There is nothing secret to copy: the snippet is a config.yaml block
with auth: oauth plus a matching
hermes mcp add command. No token, no bearer, no api key in the output.
mcp_servers: agentvalet: url: https://api.agentvalet.ai/mcp/v1/<your-owner-id> auth: oauth timeout: 60
config.yaml block, or run the hermes mcp add command it gives you. Both are built from your owner id - no key to handle.hermes agent type so its actions are attributable in the audit log.
The dashboard snippet is the recommended path. If you'd rather wire it up from the terminal, the Add to Hermes action also gives you the equivalent hermes mcp add agentvalet --url … command, built from the same owner id. Either way the connection uses OAuth, so no secret ever lands in your config.
Copy one snippet. Approve in the browser. Free to start, no credit card.