# How to connect Zoho Mail to OpenClaw

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

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

## Instructions for AI agents

Goal: connect Zoho Mail to OpenClaw with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/zoho-mail/framework/openclaw/

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 OpenClaw'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 OpenClaw: 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 OpenClaw'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

Saving an Agent200 server configuration is the first check. Confirm tool discovery, then read one email message the connected user can access. The returned source record verifies the Zoho Mail path; a saved setting alone does not.

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

References: [OpenClaw documentation](https://docs.openclaw.ai/cli/mcp/registry) 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:** OpenClaw · 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/openclaw/#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.
- **OpenClaw, with custom MCP servers allowed.** OpenClaw is open source and self-hosted: anyone running it can add MCP servers, from the CLI, the config file or the Control UI.

## Connect Zoho Mail to OpenClaw

### Step 1: Create your Agent200 API key

Create a key on the [API keys page](https://agent200.com/platform/apikeys/). Enable the Zoho Mail read operations your task needs. Store the key securely.

File `.env`:

```bash
# Keep the key out of your code, prompts and chats.
export AGENT200_API_KEY="paste-your-key-here"
```

(Conceptual example of the Agent200 SDK.)

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

OpenClaw fills `${AGENT200_API_KEY}` in its config from `~/.openclaw/.env`, so the key never sits in the config itself.

File `~/.openclaw/.env`:

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

### Step 3: Save the server

`openclaw mcp set` takes one JSON object. Always set the transport to `streamable-http`: without it OpenClaw uses SSE. Keep the single quotes so your shell leaves `${AGENT200_API_KEY}` for OpenClaw. In the Control UI, add it under **Settings > MCP**, then put the header in the config editor on the same page.

Stop the Gateway before CLI changes or live probes against its state. Use the Control UI for supported changes while it is running.

File `Terminal`:

```bash
openclaw mcp set agent200 '{"url":"https://api.agent200.com/mcp/","transport":"streamable-http","headers":{"Authorization":"Bearer ${AGENT200_API_KEY}"}}'
```

### Step 4: Probe the server

Open a live connection and list the tools Agent200 offers. If a Gateway runs elsewhere, reload or restart it.

File `Terminal`:

```bash
openclaw mcp doctor agent200 --probe
openclaw mcp status --verbose
```

### Step 5: Authorize the intended Zoho Mail account

Complete the authorization flow for the intended user. Confirm access to the selected email message before running the test.

## 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 OpenClaw 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 OpenClaw.** In your own words, for something in Zoho Mail.
2. **OpenClaw 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. **OpenClaw 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.

### Does saving the MCP configuration prove the read works?

No. Verify tool discovery and then perform the selected source read. Check both the active server configuration and the connected user if discovery succeeds but access fails.

## 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 + Hermes Agent](https://www.agent200.com/connectors/zoho-mail/framework/hermes-agent.md)

---

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