NousResearch/hermes-agent

AgentMail integration for agent-owned email inboxes

Cluster 329 · optional-skills/email. Data as of

Nothing open on GitHub. Fix merged in #330 on 9 Mar 2026. Check it covers your case.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #330. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #330. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items all relate to adding AgentMail support, enabling agents to own and operate email inboxes. The work spans a feature request, a native tool implementation, and a skill addition.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #330 feat: add AgentMail skill for agent-owned email inboxes

    merged to main

    files: skills/email/agentmail/SKILL.md

    Show the diff
    • skills/email/agentmail/SKILL.md
      @@ -0,0 +1,131 @@
      +---
      +name: agentmail
      +description: Give the agent its own dedicated email inbox via AgentMail. Send, receive, and manage email autonomously using agent-owned email addresses (e.g. [redacted:email]).
      +version: 1.0.0
      +metadata:
      +  hermes:
      +    tags: [email, communication, agentmail, mcp]
      +    category: email
      +---
      +
      +# AgentMail — Agent-Owned Email Inboxes
      +
      +## When to Use
      +Use this skill when you need to:
      +- Give the agent its own dedicated email address
      +- Send emails autonomously on behalf of the agent
      +- Receive and read incoming emails
      +- Manage email threads and conversations
      +- Sign up for services or authenticate via email
      +- Communicate with other agents or humans via email
      +
      +This is NOT for reading the user's personal email (use himalaya or Gmail for that).
      +AgentMail gives the agent its own identity and inbox.
      +
      +## Setup
      +
      +### 1. Get an API Key
      +- Go to https://console.agentmail.to
      +- Create an account (free tier: 3 inboxes, 3,000 emails/month)
      +- Generate an API key (starts with `am_`)
      +
      +### 2. Configure Hermes
      +Add to `~/.hermes/.env`:
      +```
      +AGENTMAIL_API_KEY=[redacted:secret-assignment]
      +```
      +
      +Add to `~/.hermes/config.yaml`:
      +```yaml
      +mcp_servers:
      +  agentmail:
      +    command: "npx"
      +    args: ["-y", "agentmail-mcp"]
      +    env:
      +      AGENTMAIL_API_KEY: "[redacted:secret-assignment]"
      +```
      +
      +### 3. Verify Node.js is installed
      +```bash
      +node --version  # Should be 18+
      +```
      +
      +### 4. Restart Hermes
      +```bash
      +hermes
      +```
      +All 11 AgentMail tools are now available automatically.
      +
      +## Available Tools (via MCP)
      +
      +| Tool | Description |
      +|------|-------------|
      +| `list_inboxes` | List all agent inboxes |
      +| `get_inbox` | Get details of a specific inbox |
      +| `create_inbox` | Create a new inbox (gets a real email address) |
      +| `delete_inbox` | Delete an inbox |
      +| `list_threads` | List email threads in an inbox |
      +| `get_thread` | Get a specific email thread |
      +| `send_message` | Send a new email |
      +| `reply_to_message` | Reply to an existing email |
      +| `forward_message` | Forward an email |
      +| `update_message` | Update message labels/status |
      +| `get_attachment` | Download an email attachment |
      +
      +## Procedure
      +
      +### Create an inbox and send an email
      +1. Create a dedicated inbox:
      +   - Use `create_inbox` with a username (e.g. `hermes-agent`)
      +   - The agent gets address: `[redacted:email]`
      +2. Send an email:
      +   - Use `send_message` with `inbox_id`, `to`, `subject`, `text`
      +3. Check for replies:
      +   - Use `list_threads` to see incoming conversations
      +   - Use `get_thread` to read a specific thread
      +
      +### Check incoming email
      +1. Use `list_inboxes` to find your inbox ID
      +2. Use `list_threads` with the inbox ID to see conversations
      +3. Use `get_thread` to read a thread and its messages
      +
      +### Reply to an email
      +1. Get the thread with `get_thread`
      +2. Use `reply_to_message` with the message ID and your reply text
      +
      +## Example Workflows
      +
      +**Sign up for a service:**
      +```
      +1. create_inbox (username: "signup-bot")
      +2. Use the inbox address to register on the service
      +3. list_threads to check for verification email
      +4. get_thread to read the verification code
      +```
      +
      +**Agent-to-human outreach:**
      +```
      +1. create_inbox (username: "hermes-outreach")
      +2. send_message (to: [redacted:email], subject: "Hello", text: "...")
      +3. list_threads to check for replies
      +```
      +
      +## Pitfalls
      +- Free tier limited to 3 inboxes and 3,000 emails/month
      +- Emails come from `@agentmail.to` domain on free tier (custom domains on paid plans)
      +- Node.js (18+) is required for the MCP server (`npx -y agentmail-mcp`)
      +- The `mcp` Python package must be installed: `pip install mcp`
      +- Real-time inbound email (webhooks) requires a public server — use `list_threads` polling via cronjob instead for personal use
      +
      +## Verification
      +After setup, test with:
      +```
      +hermes --toolsets mcp -q "Create an AgentMail inbox called test-agent and tell me its email address"
      +```
      +You should see the new inbox address returned.
      +
      +## References
      +- AgentMail docs: https://docs.agentmail.to/
      +- AgentMail console: https://console.agentmail.to
      +- AgentMail MCP repo: https://github.com/agentmail-to/agentmail-mcp
      +- Pricing: https://www.agentmail.to/pricing

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #398 feat(agentmail): native AgentMail tool for agent-owned email inboxes · superseded by another PR → #330, #329
Closed issues · 1
  • Closed#329Feature: AgentMail Integration — Agent-Owned Email Inboxes
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
optional-skills/email
Merged PRs
#330
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
9 Mar 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.

For your agent

The same facts, typed.