AgentMail + Hermes Agent

How to connect AgentMail to Hermes Agent

Connect AgentMail to Hermes Agent through Agent200's MCP server: no separate key, ready-made tools and one API key.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. AgentMail tools
  7. How it works
  8. Troubleshooting

Overview

This guide connects AgentMail to Hermes Agent through Agent200's MCP server. When you finish, Hermes Agent can search, read and act in AgentMail with the tools Agent200 provides, whenever a request needs them.

You add one MCP server to Hermes Agent with your Agent200 API key. AgentMail is reached with that key, so there is no separate AgentMail key to manage.

Connector
AgentMail
Works with
Hermes Agent ยท Agent app, through MCP
Authentication
Your Agent200 API key
Tools
7 tools
MCP server
https://api.agent200.com/mcp/

Before you start

  • An Agent200 API key. Create one on the API keys page of the dashboard.
  • AgentMail enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
  • Hermes Agent, with custom MCP servers allowed. Hermes Agent is open source and self-hosted: anyone running it can add MCP servers in its config file.

Connect AgentMail to Hermes Agent

  1. 1

    Step 1: Create your Agent200 API key

    Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Hermes Agent in the next step, as "Authorization: Bearer <your key>". One key covers AgentMail and every other connector enabled for your project. Keep it out of chats and source control.

  2. 2

    Step 2: Store your key in ~/.hermes/.env

    Keep the key out of config.yaml: Hermes reads it from ~/.hermes/.env.

    ~/.hermes/.env
    MCP: Hermes Agent key in ~/.hermes/.env
    AGENT200_API_KEY=your-agent200-api-key
  3. 3

    Step 3: Add the server to ~/.hermes/config.yaml

    Add an entry under mcp_servers with the URL and the Authorization header. Do not set transport: sse: Agent200 serves streamable HTTP.

    ~/.hermes/config.yaml
    MCP: Hermes Agent config.yaml entry
    mcp_servers:
      agent200:
        url: "https://api.agent200.com/mcp/"
        headers:
          Authorization: "Bearer ${AGENT200_API_KEY}"
  4. 4

    Step 4: Reload and test

    In a running session, run /reload-mcp, or restart Hermes. Then check what the server returned from a terminal.

    Terminal
    MCP: Hermes Agent reload and test
    # In a running Hermes session: /reload-mcp
    hermes mcp test agent200
    hermes mcp list

Test your connection

Run one request to check everything is wired up.

Ask

Check the support inbox for new messages

What should come back

  • A result from AgentMail, returned through your Agent200 API key.
  • Behind the scenes, Hermes Agent calls agentmail_list_inboxes.

If a tool is refused, check that AgentMail is switched on for your project in the Agent200 dashboard.

Get your API key

Create a key in the Agent200 dashboard. It reaches AgentMail and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect AgentMail to Hermes Agent.

Agent brief
Goal: connect AgentMail to Hermes Agent with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/agentmail/framework/hermes-agent/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Hermes Agent's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure AgentMail is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Hermes Agent: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Hermes Agent's exact menus or commands.
4. Check it works with this request: "Check the support inbox for new messages"
   What should come back:
   - A result from AgentMail, returned through your Agent200 API key.
   - Behind the scenes, Hermes Agent calls `agentmail_list_inboxes`.
5. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.

The whole guide is also available as Markdown, for agents and LLMs: /connectors/agentmail/framework/hermes-agent.md

AgentMail tools Hermes Agent can call

  • Create an inbox

    Write
    agentmail_create_inbox

    Create a new email inbox for the agent.

  • List inboxes

    Read
    agentmail_list_inboxes

    List the agent's inboxes.

  • Send a message

    Write
    agentmail_send_message

    Send an email from an inbox.

  • List messages

    Read
    agentmail_list_messages

    List the messages in an inbox.

  • Read a message

    Read
    agentmail_get_message

    Read a message and its content.

  • Reply to a message

    Write
    agentmail_reply_to_message

    Reply to a message in its thread.

  • List threads

    Read
    agentmail_list_threads

    List the email threads in an inbox.

How it works

  1. 01

    You ask Hermes Agent

    In your own words, for something in AgentMail.

  2. 02

    Hermes Agent picks a tool

    It sees the AgentMail tools on the Agent200 MCP server and calls the one the request needs.

  3. 03

    Agent200 runs the call

    It reaches AgentMail with your Agent200 API key, within the endpoints your project allows.

  4. 04

    Hermes Agent answers

    It gets the result back from the MCP server and uses it in its reply or its next step.

Permissions at every level. Your project settings decide which services and endpoints the agent may use.

Troubleshooting

The connection fails and names a missing variable

Add AGENT200_API_KEY to ~/.hermes/.env and run /reload-mcp.

The server answers 401 or 403

Check the key in ~/.hermes/.env and that the header reads exactly Bearer ${AGENT200_API_KEY}.

The initialize request fails with 400 or 405

That points to an SSE setting. Remove any transport: sse line from the entry and check the URL is exactly the Agent200 MCP server address.

The AgentMail tools do not appear

Run hermes mcp test agent200, check the entry is not disabled and no tools filter hides them, then /reload-mcp. Hermes names them mcp_agent200_....

A tool call is refused or returns less than expected

Agent200 runs only what your project allows. Check that AgentMail and the tools you need are enabled in the dashboard's Connectors settings.

The API key was pasted into a chat or committed

Create a new key on the API keys page, replace it in Hermes Agent's MCP settings, and stop using the old one. Paste the key only into Hermes Agent's settings, never into a chat.

Use AgentMail with another framework

200 OK

AgentMail, connected to Hermes Agent.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)