Recommended: OAuth configuration
Add this entry under mcp_servers in ~/.hermes/config.yaml. Start a fresh terminal for the first interactive login so config auto-reload does not time out while you approve access.
mcp_servers:
verifiedmrr:
url: "https://verifiedmrr.com/mcp"
auth: oauth
timeout: 30
supports_parallel_tool_calls: true
Authenticate and verify
Run the login command, open the authorization URL, sign in to VerifiedMRR, and approve revenue:read. On a remote host, Hermes can accept the final redirect URL as a paste-back when the browser cannot reach the loopback callback.
hermes mcp login verifiedmrr
hermes chat
Headless token alternative
Create a personal MCP token in VerifiedMRR Settings and replace auth: oauth with an Authorization header. Treat config.yaml as a secret-bearing file and keep it out of backups or repositories that other people can read.
Hermes prefixes imported tools, so get_revenue_overview appears as mcp_verifiedmrr_get_revenue_overview. You normally ask in plain language and let Hermes choose the tool.
mcp_servers:
verifiedmrr:
url: "https://verifiedmrr.com/mcp"
headers:
Authorization: "Bearer vmrr_mcp_REPLACE_ME"
timeout: 30
FAQ
Before you connect a provider.
Does Hermes support VerifiedMRR OAuth?
Yes. Hermes supports OAuth-authenticated remote HTTP MCP servers, including discovery, dynamic registration, PKCE, token refresh, and remote-host paste-back.
Can Hermes call tools in parallel?
Yes. The VerifiedMRR tools are independent, read-only queries, so supports_parallel_tool_calls can be enabled. The server still scopes every call to the authorized workspace.
How do I reload after changing config?
Use /reload-mcp in Hermes, or start a fresh Hermes session. For the first OAuth login, use hermes mcp login verifiedmrr from a fresh terminal.