# How to connect Zoho Mail to Hermes Agent

> Read email messages with Hermes Agent and Agent200. Prepare a mailbox briefing using the connected user’s own Zoho Mail account.

- Page: https://www.agent200.com/connectors/zoho-mail/framework/hermes-agent/
- Connector: [Zoho Mail](https://www.agent200.com/connectors/zoho-mail.md)
- Framework: Hermes Agent
- Updated: 2026-11-17

## Instructions for AI agents

Goal: connect Zoho Mail to Hermes Agent with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/zoho-mail/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 Zoho Mail 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. The first Zoho Mail request returns an authorization link if the user has not connected Zoho Mail yet: show it to them and continue once they have approved access on Zoho Mail's own page.
5. Check it works with this request: "Read the Zoho Mail message I select from my connected mailbox. Summarize its sender, subject and the requested action stated in the body. Ask for missing account, folder or message context. Do not send, move, delete or change any message."
   What should come back:
   - The selected email message is identified clearly.
   - The answer includes only returned message identity, sender, subject and requested details from the body.
   - Missing information and access failures are reported; no source data is changed.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Zoho Mail, then retry.

## Overview

Inspect the Agent200 tools exposed in Hermes after configuration. Use the advertised schemas and names for the email message read; server prefixes and argument mappings should come from discovery, not from guessed catalogue names.

Start with one identified email message. Preserve the returned details, report missing information and keep the workflow read-only.

References: [Hermes Agent documentation](https://hermes-agent.nousresearch.com/docs/user-guide/features/mcp/) and [Zoho Mail provider reference](https://www.zoho.com/mail/help/api/get-email-content.html).

- **Connector:** [Zoho Mail](https://www.agent200.com/connectors/zoho-mail/)
- **Works with:** Hermes Agent · Agent app, through MCP
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [5 tools](https://www.agent200.com/connectors/zoho-mail/framework/hermes-agent/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **Zoho Mail enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a Zoho Mail account.** They approve access once, on Zoho Mail's own page.
- **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 Zoho Mail to Hermes Agent

### 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 Zoho Mail and every other connector enabled for your project. Keep it out of chats and source control.

Create an API key: https://agent200.com/platform/apikeys/

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

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

File `~/.hermes/.env`:

```bash
AGENT200_API_KEY=your-agent200-api-key
```

### 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.

File `~/.hermes/config.yaml`:

```text
mcp_servers:
  agent200:
    url: "https://api.agent200.com/mcp/"
    headers:
      Authorization: "Bearer ${AGENT200_API_KEY}"
```

### Step 4: Reload and test

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

File `Terminal`:

```bash
# In a running Hermes session: /reload-mcp
hermes mcp test agent200
hermes mcp list
```

### Step 5: Connect your Zoho Mail account

The first time you ask Hermes Agent for something in Zoho Mail, Agent200 returns an authorization link. Open it and approve access on Zoho Mail's own page. Agent200 stores the connection and keeps it working; your password never reaches Hermes Agent or Agent200.

## Test your connection

Ask: "Read the Zoho Mail message I select from my connected mailbox. Summarize its sender, subject and the requested action stated in the body. Ask for missing account, folder or message context. Do not send, move, delete or change any message."

What should come back:

- The selected email message is identified clearly.
- The answer includes only returned message identity, sender, subject and requested details from the body.
- Missing information and access failures are reported; no source data is changed.

Confirm the intended account, folder and message. Inspect the available tools and read permissions. Do not turn a missing body or access error into an invented email summary.

## Zoho Mail tools Hermes Agent can call

- **List mail accounts** (`zoho_mail_list_accounts`, read): Identify the mail accounts available to the authenticated user.
- **List folders** (`zoho_mail_list_folders`, read): Find folders within the mail account selected for the request.
- **List messages** (`zoho_mail_list_messages`, read): Read a scoped list of messages from the selected account and folder.
- **Search messages** (`zoho_mail_search_messages`, read): Find messages matching the requested search criteria in the selected account.
- **Read message content** (`zoho_mail_get_message_content`, read): Retrieve the body of one selected message using its account, folder and message context.

## How it works

1. **You ask Hermes Agent.** In your own words, for something in Zoho Mail.
2. **Hermes Agent picks a tool.** It sees the Zoho Mail tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** With your own Zoho Mail connection, within the tools and scopes your project allows.
4. **Hermes Agent answers.** It gets the result back from the MCP server and uses it in its reply or its next step.

**Each user's own connection.** Connections belong to individual end users. A request for one user never reaches another user's Zoho Mail account.

**Permissions at every level.** Your project settings decide what the agent may request, the end user decides what they authorize, and Zoho Mail enforces what its API grants.

## Troubleshooting

### The source cannot be read

Confirm the intended account, folder and message. Inspect the available tools and read permissions. Do not turn a missing body or access error into an invented email summary.

### The answer claims more than the tool returned

Compare the answer with the retrieved data. Limit conclusions to the selected source and result scope, and say what was unavailable.

## FAQ

### Does preparing a reply send an email?

No. Show proposed reply text in the conversation for review. This read-only guide does not configure sending, saving a provider-side draft or changing mailbox state.

### Which tool name should Hermes call?

Use the name and input schema advertised by the live MCP connection. The site’s catalogue identifiers describe operations, but server-prefixed names and actual arguments come from discovery.

## Use Zoho Mail with another framework

- [Zoho Mail + Claude](https://www.agent200.com/connectors/zoho-mail/framework/claude.md)
- [Zoho Mail + ChatGPT](https://www.agent200.com/connectors/zoho-mail/framework/chatgpt.md)
- [Zoho Mail + Claude Code](https://www.agent200.com/connectors/zoho-mail/framework/claude-code.md)
- [Zoho Mail + Muse](https://www.agent200.com/connectors/zoho-mail/framework/muse.md)
- [Zoho Mail + Grok Bot](https://www.agent200.com/connectors/zoho-mail/framework/grok-bot.md)
- [Zoho Mail + OpenAI Dots](https://www.agent200.com/connectors/zoho-mail/framework/openai-dots.md)
- [Zoho Mail + Claude Duet](https://www.agent200.com/connectors/zoho-mail/framework/claude-duet.md)
- [Zoho Mail + OpenClaw](https://www.agent200.com/connectors/zoho-mail/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
