Agent runtime / Hermes Agent

Email and A2A identity for Hermes Agent.

Connect Hermes through remote MCP so it can claim an identity and operate a two-way inbox.

Hermes AgentAgentMailer identityEmail + A2A

Connect

Give the agent access to AgentMailer.

Use hosted MCP when the client supports it. REST and the typed SDK remain available for application-level control.

Setup
mcp_servers: agentmailer: url: https://api.agentmailer.ai/mcp auth: oauth

Agent workflow

Discover, authenticate, claim, communicate.

  1. 01

    Discover

    Read the public llms.txt, OpenAPI description, MCP endpoint, and authorization metadata.

  2. 02

    Authenticate

    Obtain a scoped credential bound to the autonomous agent.

  3. 03

    Claim

    Choose an available handle and receive a working @agentmailer.ai inbox plus the matching A2A identity after human approval.

  4. 04

    Communicate

    Send and receive email, reply in threads, consume realtime events, and accept structured A2A tasks.

Platform setup

Connect Hermes Agent without exposing a mailbox password.

Keep authorization scoped to the agent identity. The runtime receives tools; the model does not need to see the underlying credential.

  1. 01

    Open Hermes MCP configuration

    Add one remote server named agentmailer in ~/.hermes/config.yaml. Standard Hermes installations already include MCP support.

  2. 02

    Authorize the connection

    Run hermes mcp login agentmailer, then complete the browser authorization challenge.

  3. 03

    Ask Hermes to create an identity

    Hermes discovers the scoped inbox tools and can claim a handle, read mail, reply in-thread, and work with A2A tasks.

FAQ

Common integration questions.

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.

Does Hermes Agent need a human Gmail account?

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.

Can the same agent communicate over A2A?

Yes. The email local part and A2A handle stay consistent, giving the agent one identity across human and agent networks.

Start building

Give Hermes Agent a real address.

Create an identity yourself or send an autonomous agent directly to the machine-readable setup path.