# Cooper Email MCP server

> Give AI agents their own email inboxes to send, receive, search and reply to mail, with webhooks and human owner approval.

- Listing: https://mcp.tc/i/cooper-email
- Connect: use the server's own URL `https://cooperemail.com/mcp` (sign-in optional); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: optional (works without sign-in)
- Category: [Communication & Meetings](https://mcp.tc/c/communication)
- Vendor: Avatar 8 LLC
- Homepage: <https://cooperemail.com>
- Repository: <https://github.com/cooper-email/cooper-email>

## About

Cooper Email gives an AI agent its own real email inboxes. Tools create addresses, send, reply and forward mail, wait for incoming messages and verification codes, search threads, manage drafts, webhooks and custom domains, and keep a human owner in the loop by email.

It runs as a hosted streamable HTTP endpoint at https://cooperemail.com/mcp. Users can sign in with OAuth, or send a Cooper API key (coop\_live\_...) as a Bearer token. The onboarding tool can also create an inbox and key without credentials. Sending delivers real email that cannot be recalled.

## What it can do

- Create single or batch inboxes, including expiring ones
- Send, reply to and forward email with attachments
- Wait for incoming mail or verification codes
- Search messages and read threads across the account
- Register webhooks and instant reply wake-ups
- Add human owners and ask them questions by email
- Add and verify custom domains

## Tools (111)

- `cooper_onboard`: Create an inbox and API key when the connection is not signed in yet. (can modify or delete data)
- `cooper_create_inbox`: Create an additional inbox on the signed-in account. (can modify or delete data)
- `cooper_create_inboxes`: Create several inboxes at once, optionally expiring after a deadline. (can modify or delete data)
- `cooper_list_inboxes`: List inboxes on the account. (read-only)
- `cooper_send_message`: Send an email from a Cooper address. (can modify or delete data)
- `cooper_list_messages`: List recent sent and received messages in an inbox. (read-only)
- `cooper_get_message`: Get the full content of one message. (read-only)
- `cooper_search`: Search mail across the account or one inbox. (read-only)
- `cooper_search_messages`: Search one inbox with highlighted matches. (read-only)
- `cooper_inject_inbound`: Simulate an inbound email for testing.
- `cooper_register_webhook`: Register a webhook to be notified when mail arrives.
- `cooper_enable_instant_replies`: Wake the agent within seconds when an owner message arrives.
- `cooper_billing_status`: Show plan and monthly quota usage. (read-only)
- `cooper_upgrade_link`: Create a Stripe Checkout link to upgrade the plan.
- `cooper_add_owner`: Register a human owner for progress updates. (can modify or delete data)
- `cooper_list_owners`: List an inbox's human owners and confirmation status. (read-only)
- `cooper_notify_owner`: Email the human owners a progress or status update. (can modify or delete data)
- `cooper_ask_owner`: Ask the owner a question by email and wait for the answer.
- `cooper_get_question`: Get the status or answer of an owner question. (read-only)
- `cooper_get_tasks`: List tasks created by owner or allowlisted sender emails. (read-only)
- `cooper_reply_task`: Reply to an owner task in the same email thread. (can modify or delete data)
- `cooper_add_domain`: Add a custom domain and get DNS records to publish. (can modify or delete data)
- `cooper_create_workspace`: Create a sub-account with its own API key and inbox quota.
- `cooper_list_workspaces`: List sub-accounts and their quotas. (read-only)
- `cooper_get_workspace`: Get one sub-account. (read-only)
- `cooper_update_workspace`: Rename a sub-account or change its inbox quota.
- `cooper_delete_workspace`: Delete a sub-account, its key and its mail. (can modify or delete data)
- `cooper_delete_inbox`: Delete an inbox and its messages. (can modify or delete data)
- `cooper_update_inbox`: Pause, resume or change inbox settings. (can modify or delete data)
- `cooper_update_message`: Change labels on a message, including marking it read.
- `cooper_update_messages`: Change labels on several messages at once.
- `cooper_list_domains`: List custom domains and DNS status. (read-only)
- `cooper_verify_domain`: Check a custom domain's DNS immediately.
- `cooper_domain_setup_link`: Create a link for a human to publish DNS records.
- `cooper_reply_message`: Reply to a stored message with threading filled in. (can modify or delete data)
- `cooper_forward_message`: Forward a stored message with its attachments. (can modify or delete data)
- `cooper_wait_for_message`: Wait for a reply or verification code to arrive. (read-only)
- `cooper_list_events`: List the recent account event log. (read-only)
- `cooper_list_threads`: List whole conversations in an inbox. (read-only)
- `cooper_get_thread`: Get every message in one thread. (read-only)
- `cooper_search_threads`: Use this when you need the conversations that contain a keyword, sender, recipient, or subject, instead of each matching message. (read-only)
- `cooper_delete_thread`: Use this when a whole conversation should be removed permanently. (can modify or delete data)
- `cooper_update_thread`: Use this when every message in a conversation should gain or lose the same labels, including marking the thread read, or when the thread should move to inbox, archive, spam, or trash.
- `cooper_move_threads`: Use this when several conversations should move to the same folder in one call, for example archiving finished work or trashing a batch.
- `cooper_assign_thread`: Use this when a triage agent should hand a thread to a named assignee, or a worker should take an exclusive claim so another worker does not reply to the same thread.
- `cooper_unassign_thread`: Use this when the assignee is done with a thread, or a worker should release its claim.
- `cooper_list_list_entries`: Use this when you need the addresses on an allow or block list. (read-only)
- `cooper_get_list_entry`: Use this when you need one address or domain on an allow or block list. (read-only)
- `cooper_create_list_entry`: Use this when an agent should only mail approved recipients, or should ignore unwanted senders. (can modify or delete data)
- `cooper_delete_list_entry`: Use this when an address or domain should leave an allow or block list. (can modify or delete data)
- `cooper_get_inbox`: Use this when you need one inbox's address, display name, metadata, status, client\_id, screening, send\_mode, or plus-address format and you already have its id, username, or email. (read-only)
- `cooper_confirm_owner`: Use this when a human received the 6-digit confirmation code and you need to mark that owner verified so they can receive updates and open tasks.
- `cooper_whoami`: Use this when you need to see which Cooper account this connection is using and whether the API key is limited to one inbox or a permission list.
- `cooper_list_webhooks`: Use this when you need the webhooks on this account, including whether each one is enabled and which inboxes it matches. (read-only)
- `cooper_update_webhook`: Use this when a webhook URL, event list, inbox filter, or enabled flag should change. (can modify or delete data)
- `cooper_delete_webhook`: Use this when a webhook should stop receiving events and be removed. (can modify or delete data)
- `cooper_rotate_webhook_secret`: Use this when a webhook signing secret should change without breaking receivers that still check the old secret. (can modify or delete data)
- `cooper_test_webhook`: Use this when you need to confirm a webhook URL accepts a signed POST right now.
- `cooper_list_suppressions`: Use this when you need the addresses this account will not email after a permanent bounce, a complaint, or a manual add. (read-only)
- `cooper_delete_suppression`: Use this when an address should receive mail again after it was suppressed for a bounce, a complaint, or a manual add. (can modify or delete data)
- `cooper_release_message`: Use this when inbound screening held a message (label held) and a person has decided it should be delivered to the agent. (can modify or delete data)
- `cooper_get_attachment`: Use this when you need the text of one attachment, or its bytes as base64. (read-only)
- `cooper_get_metrics`: Use this when you need counts of mail over time, current usage, or bounce and complaint rates for this account. (read-only)
- `cooper_get_sending_status`: Use this when you need to know whether this account can still send email, or why sending was paused. (read-only)
- `cooper_create_draft`: Use this when you want to prepare a message without sending it yet. (can modify or delete data)
- `cooper_get_draft`: Use this when you need one draft, including its labels, attachments, send\_at, send\_status, and approval\_status. (read-only)
- `cooper_list_drafts`: Use this when you need drafts on one inbox or across the account. (read-only)
- `cooper_update_draft`: Use this when a draft should change before it sends. (can modify or delete data)
- `cooper_delete_draft`: Use this when a draft should be discarded, including a scheduled send you want to cancel. (can modify or delete data)
- `cooper_send_draft`: Use this when a draft should be sent now. (can modify or delete data)
- `cooper_wait_for_code`: Use this when you signed up for a service or triggered a login and need the one-time verification code (OTP) or the confirmation link it emails you, including when several signups share one inbox via plus addresses. (read-only)
- `cooper_get_owner_preferences`: Use this before writing to a human owner (cooper\_notify\_owner) to see how they want Cooper email written. (read-only)
- `cooper_set_owner_preferences`: Use this when the human asks for shorter, longer, or friendlier email from Cooper.
- `cooper_list_oauth_grants`: Use this when you need to see which OAuth apps currently hold access to this account, for example before revoking one. (read-only)
- `cooper_revoke_oauth_grant`: Use this when an OAuth app should lose access to this account. (can modify or delete data)
- `cooper_list_event_subscriptions`: Use this when you need to see which MCP event subscriptions are watching inboxes on this account. (read-only)
- `cooper_delete_event_subscription`: Use this when an MCP event subscription should stop. (can modify or delete data)
- `cooper_set_addons`: Use this when a Starter or Pro account needs more inboxes, custom domains, or monthly emails than the plan includes.
- `cooper_poll_events`: Use this when a scheduled agent needs Cooper events without a public webhook URL and without storing a cursor.
- `cooper_commit_events`: Use this after you have processed a page from cooper\_poll\_events.
- `cooper_list_event_consumers`: Use this to see the durable event consumers on this account. (read-only)
- `cooper_delete_event_consumer`: Use this to remove a durable event consumer and its cursor. (can modify or delete data)
- `cooper_list_rules`: Use this to see the deterministic rules on one inbox, in the order they run. (read-only)
- `cooper_create_rule`: Use this when mail like X should be labeled, filed, forwarded, or acknowledged on the server with no model call, including mail to one plus address.
- `cooper_update_rule`: Use this to change a stored inbox rule.
- `cooper_delete_rule`: Use this to remove one inbox rule and its auto-reply cooldown rows. (can modify or delete data)
- `cooper_test_rule`: Use this to see which rules would match a stored message, and which actions would run or be skipped, without changing mail. (read-only)
- `cooper_get_idempotency_key`: Use this to see whether an Idempotency-Key is in progress, done, or unknown. (read-only)
- `cooper_release_idempotency_key`: Use this after you have confirmed an unknown Idempotency-Key did not send, or you accept the risk of sending again. (can modify or delete data)
- `cooper_resolve_idempotency_key`: Use this when an unknown Idempotency-Key matches a message you found in the sent folder.
- `cooper_list_request_refusals`: Use this when a Cooper call failed and you need to see recent refusals and their error codes. (read-only)
- `cooper_list_forwarding`: Use this to see the external addresses that receive a copy of every inbound email on one inbox. (read-only)
- `cooper_request_forwarding`: Use this when every inbound copy on an inbox should also go to an external address, such as a team mailbox or an archive.
- `cooper_remove_forwarding`: Use this to stop copying inbound mail to one external address. (can modify or delete data)
- `cooper_set_forwarding`: Use this to keep only some already-verified external addresses on an inbox. (can modify or delete data)
- `cooper_contact_history`: Use this when you are about to reply to someone and want every past thread, reply, and attachment with them. (read-only)
- `cooper_security_check`: Use this before an agent inbox sends mail. (read-only)
- `cooper_create_api_key_link`: Use this when the person needs an API key for this account, for example a ChatGPT, Claude, or Grok Bot user who signed in with OAuth and has no key for curl, a script, or another client.
- `cooper_provision_phone_number`: Provision a US local number for an inbox. (can modify or delete data)
- `cooper_get_phone_number`: Read the active phone number on an inbox. (read-only)
- … and 11 more on the listing page.

## Example prompts

- "Create an inbox called research-bot and show me its address."
- "Wait for the verification code sent to my inbox and give it to me."
- "Search my inboxes for emails from billing about invoices."
- "Reply to the latest message in my support inbox after I confirm the text."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http cooper-email https://cooperemail.com/mcp
```

2. Start Claude Code and type `/mcp`. **cooper-email** should show as connected. To sign in for more access, pick it and choose **Authenticate**.

Add `--scope user` to make it available in every project, not just this one. Works without a key. An API key from Avatar 8 LLC raises the limits: send it as `Authorization: Bearer <YOUR_API_KEY>`.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Cooper Email** and paste this URL:

```url
https://cooperemail.com/mcp
```

3. Click **Add**, then **Connect**. Signing in to Avatar 8 LLC is optional.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Cooper%20Email&connectorUrl=https%3A%2F%2Fcooperemail.com%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://cooperemail.com/mcp` and click **Add**.

3. Click **Connect**. Signing in to Avatar 8 LLC is optional.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://cooperemail.com/mcp` as the server URL, then for authentication choose **No authentication**, or **OAuth** to sign in to Avatar 8 LLC for more access.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=cooper-email&config=eyJ1cmwiOiJodHRwczovL2Nvb3BlcmVtYWlsLmNvbS9tY3AifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "cooper-email": {
      "url": "https://cooperemail.com/mcp"
    }
  }
}
```

Works without a key. An API key from Avatar 8 LLC raises the limits: send it as `Authorization: Bearer <YOUR_API_KEY>`.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=cooper-email&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fcooperemail.com%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"cooper-email","type":"http","url":"https://cooperemail.com/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "cooper-email": {
      "type": "http",
      "url": "https://cooperemail.com/mcp"
    }
  }
}
```

Works without a key. An API key from Avatar 8 LLC raises the limits: send it as `Authorization: Bearer <YOUR_API_KEY>`.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "cooper-email": {
      "serverUrl": "https://cooperemail.com/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. Works without a key. An API key from Avatar 8 LLC raises the limits: send it as `Authorization: Bearer <YOUR_API_KEY>`.

### Codex

```bash
codex mcp add cooper-email --url https://cooperemail.com/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.cooper-email]
url = "https://cooperemail.com/mcp"
```

Works without a key. An API key from Avatar 8 LLC raises the limits: send it as `Authorization: Bearer <YOUR_API_KEY>`.

### Gemini CLI

```bash
gemini mcp add --transport http cooper-email https://cooperemail.com/mcp
```

Then, inside Gemini CLI, run `/mcp auth cooper-email` to sign in (optional).

This adds it to the current project. Add `-s user` to use it everywhere. Works without a key. An API key from Avatar 8 LLC raises the limits: send it as `Authorization: Bearer <YOUR_API_KEY>`.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "cooper-email": {
      "type": "http",
      "url": "https://cooperemail.com/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://cooperemail.com/mcp`.

Works without a key. An API key from Avatar 8 LLC raises the limits: send it as `Authorization: Bearer <YOUR_API_KEY>`.

## Recent changes

- 2026-11-18 05:54 UTC: 1 tool added. Source: automatic check. Added: cooper\_create\_api\_key\_link.
- 2026-11-16 05:57 UTC: 1 tool changed. Source: automatic check. Changed: cooper\_list\_messages.
- 2026-11-14 14:51 UTC: 1 tool added. Source: automatic check. Added: cooper\_security\_check.
- 2026-11-12 20:22 UTC: Tracking started: 109 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/cooper-email#history (Atom feed: https://mcp.tc/i/cooper-email/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.11.0
- MCP protocol version: 2026-07-28
- Last checked: 2026-11-18 (reachable)
- Listed: 2026-11-12
- Updated: 2026-11-18

---
Source: https://mcp.tc/i/cooper-email (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
