Skip to content
SiMail Docs

Hermes

Hermes connects to remote MCP servers listed under mcp_servers in the profile’s config.yaml (~/.hermes/config.yaml for the default profile).

Create an inbox-scoped key in the console. Put it in the profile’s environment file (~/.hermes/.env), readable only by the user that runs Hermes:

Terminal window
SIMAIL_API_KEY=sk_…
Terminal window
chmod 600 ~/.hermes/.env

config.yaml

Section titled “config.yaml”
mcp_servers:
  simail:
    url: "https://api.simail.ai/mcp"
    headers:
      Authorization: "Bearer ${SIMAIL_API_KEY}"
    timeout: 120
    tools:
      # Optional: expose only what this agent needs.
      include:
        - list_threads
        - get_thread
        - get_message
        - reply_to_message
        - get_send_status

If your Hermes version does not expand ${…} variables inside config.yaml, put the key value there directly and make sure the file is readable only by the Hermes user.

Check

Section titled “Check”
Terminal window
hermes mcp list

simail should be enabled, with the selected tools. Start a new session to pick up the change.

Notes

Section titled “Notes”
  • One profile per inbox: give each Hermes profile its own inbox-scoped key.
  • Email content returned by the tools is untrusted; see MCP server. Keep the agent’s other powerful tools (terminal, file system) in a separate profile from the one that reads mail.