# How to connect AgentMail to OpenClaw

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

- Page: https://www.agent200.com/connectors/agentmail/framework/openclaw/
- Connector: [AgentMail](https://www.agent200.com/connectors/agentmail.md)
- Framework: OpenClaw
- Updated: 2026-11-18

## Instructions for AI agents

Goal: connect AgentMail to OpenClaw with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/agentmail/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 AgentMail 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. 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, OpenClaw 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.

## Overview

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

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

- **Connector:** [AgentMail](https://www.agent200.com/connectors/agentmail/)
- **Works with:** OpenClaw · Agent app, through MCP
- **Authentication:** Your Agent200 API key
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [7 tools](https://www.agent200.com/connectors/agentmail/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.
- **AgentMail enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **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 AgentMail to OpenClaw

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

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

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

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
```

## Test your connection

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, OpenClaw calls `agentmail_list_inboxes`.

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

## AgentMail tools OpenClaw can call

- **Create an inbox** (`agentmail_create_inbox`, write): Create a new email inbox for the agent.
- **List inboxes** (`agentmail_list_inboxes`, read): List the agent's inboxes.
- **Send a message** (`agentmail_send_message`, write): Send an email from an inbox.
- **List messages** (`agentmail_list_messages`, read): List the messages in an inbox.
- **Read a message** (`agentmail_get_message`, read): Read a message and its content.
- **Reply to a message** (`agentmail_reply_to_message`, write): Reply to a message in its thread.
- **List threads** (`agentmail_list_threads`, read): List the email threads in an inbox.

## How it works

1. **You ask OpenClaw.** In your own words, for something in AgentMail.
2. **OpenClaw picks a tool.** It sees the AgentMail tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** It reaches AgentMail with your Agent200 API key, within the endpoints 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.

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

## Troubleshooting

### The connection fails right after adding the server

Check the transport is `streamable-http`: when it is missing OpenClaw uses SSE, which Agent200 does not serve.

### Authentication refused (401)

Check `headers.Authorization` is `Bearer ${AGENT200_API_KEY}` and that `AGENT200_API_KEY` is set for the process running OpenClaw.

### The doctor warns about a literal header value

Replace the pasted key with `${AGENT200_API_KEY}` and move the key to `~/.openclaw/.env`.

### Changes do not reach your agent

A Gateway or agent running elsewhere needs its own reload or a restart.

### 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](https://agent200.com/platform/apikeys/), replace it in OpenClaw's MCP settings, and stop using the old one. Paste the key only into OpenClaw's settings, never into a chat.

## Use AgentMail with another framework

- [AgentMail + Claude](https://www.agent200.com/connectors/agentmail/framework/claude.md)
- [AgentMail + ChatGPT](https://www.agent200.com/connectors/agentmail/framework/chatgpt.md)
- [AgentMail + Claude Code](https://www.agent200.com/connectors/agentmail/framework/claude-code.md)
- [AgentMail + Muse](https://www.agent200.com/connectors/agentmail/framework/muse.md)
- [AgentMail + Grok Bot](https://www.agent200.com/connectors/agentmail/framework/grok-bot.md)
- [AgentMail + OpenAI Dots](https://www.agent200.com/connectors/agentmail/framework/openai-dots.md)
- [AgentMail + Claude Duet](https://www.agent200.com/connectors/agentmail/framework/claude-duet.md)
- [AgentMail + Hermes Agent](https://www.agent200.com/connectors/agentmail/framework/hermes-agent.md)

---

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