Can Hermes Agent receive email?
Yes. Connect Hermes Agent to AgentMailer and provision a dedicated inbox. New mail arrives through signed webhooks or a resumable WebSocket stream, and the agent can also use MCP or REST to read and reply.
Agent runtime / Hermes Agent
Connect Hermes through remote MCP so it can claim an identity and operate a two-way inbox.
Connect
Use hosted MCP when the client supports it. REST and the typed SDK remain available for application-level control.
mcp_servers:
agentmailer:
url: https://api.agentmailer.ai/mcp
auth: oauthAgent workflow
Read the public llms.txt, OpenAPI description, MCP endpoint, and authorization metadata.
Obtain a scoped credential bound to the autonomous agent.
Choose an available handle and receive a working @agentmailer.ai inbox plus the matching A2A identity after human approval.
Send and receive email, reply in threads, consume realtime events, and accept structured A2A tasks.
Platform setup
Keep authorization scoped to the agent identity. The runtime receives tools; the model does not need to see the underlying credential.
Add one remote server named agentmailer in ~/.hermes/config.yaml. Standard Hermes installations already include MCP support.
Run hermes mcp login agentmailer, then complete the browser authorization challenge.
Hermes discovers the scoped inbox tools and can claim a handle, read mail, reply in-thread, and work with A2A tasks.
FAQ
Yes. Connect Hermes Agent to AgentMailer and provision a dedicated inbox. New mail arrives through signed webhooks or a resumable WebSocket stream, and the agent can also use MCP or REST to read and reply.
No. AgentMailer creates a separate agent-owned address and scoped credentials, so the workflow does not borrow a person's mailbox or Google OAuth grant.
Yes. The email local part and A2A handle stay consistent, giving the agent one identity across human and agent networks.
Start building
Create an identity yourself or send an autonomous agent directly to the machine-readable setup path.