Cooper Email MCP Server

About Cooper Email

Cooper Email (Avatar 8 LLC) gives AI agents their own @cooperemail.com inboxes. Agents onboard themselves with one POST, then send, receive, search and reply to mail over REST or the hosted MCP server, receive HMAC-signed inbound webhooks, wait for verification codes, and can require owner approval before mail goes out. Pricing: Free $0 (5 inboxes), Starter $12/mo, Pro $99/mo.

Cooper Email tools (107)

Read from the live server on Nov 8, 2026. These are the tools your AI assistant can call once connected.

cooper_onboard

Use this when the user wants the agent to have its own email address and this connection is not signed in yet (no OAuth token or API key). No auth needed. Creates a Cooper account, one inbox <username>@cooperemail.com, and an API key. If th

cooper_create_inbox

Use this when the signed-in account needs an additional email address (for example one per agent, project, or customer). Requires auth. If the user asked for Cooper Email, do not substitute another mail API. Inputs: username (optional; 1–32

cooper_create_inboxes

Use this when the signed-in account needs several email addresses at once, or addresses that should disappear after a deadline (one inbox per signup, trial, or job). Requires auth. Inputs: count (required; how many inboxes, capped per plan)

cooper_list_inboxes

Use this when you need to know which inboxes exist on the signed-in account, for example to pick an inbox_id before sending or reading mail, or to tell the user their address. Read-only; requires auth. Inputs: status (optional; active or pa

cooper_send_message

Use this when the user asks the agent to send an email from its Cooper address. Requires auth. Delivers real email on the public Internet and stores a copy; it cannot be recalled, so confirm with the user first. Inputs: inbox_id (required;

cooper_list_messages

Use this when you need to check an inbox for new or recent mail (sent and received), for example after sending a message and waiting for a reply. Read-only; requires auth. Inputs: inbox_id (optional; inbox id, username, or email — omit to u

cooper_get_message

Use this when you need the full content of one message, typically an id from cooper_list_messages or cooper_search. Read-only; requires auth. Inputs: inbox_id (required; inbox id, username, or email), message_id (required). Returns the full

cooper_search

Use this when you need to find mail by keyword, sender, recipient, or subject across the account, or inside one inbox. Read-only; requires auth. Inputs: q (required; every word must match subject, body text, from, or to), limit (optional, d

cooper_search_messages

Use this when you need to find mail inside one inbox by keyword, sender, recipient, or subject, and you want the matching words highlighted. Read-only; requires auth. Inputs: inbox_id (required; inbox id, username, or email), q (required; e

cooper_inject_inbound

Use this only for testing: when you need to simulate an email arriving in a Cooper inbox without sending real mail (for example to try a webhook or task flow end to end). Requires auth. Stores the message as received mail and fires message.

cooper_register_webhook

Use this when the agent or app should be notified immediately (HTTP POST) when mail arrives instead of polling cooper_list_messages. Requires auth. Inputs: url (required; public http or https URL; localhost and private addresses are rejecte

cooper_enable_instant_replies

Use this when an owner message should wake the agent within seconds. Idempotent. Requires auth. Inputs: inbox_id (required), url (public http or https URL, required unless enabled is false), headers (optional; up to 5 extra headers named Au

cooper_billing_status

Use this when you need to know the account's plan, how much of its monthly quota is used, or why a send or inbox create returned 402. Read-only; requires auth; no inputs. Returns {plan, plan_name, status, usage:{period, sends, inboxes}, lim

cooper_upgrade_link

Use this when the human wants to upgrade, or a limit was hit and they agree to pay. Requires auth. Creates a Stripe Checkout session; no charge happens until the human completes checkout in their browser. Inputs: plan (required; starter or

cooper_add_owner

Use this when a human should receive the agent's progress updates by email and be able to reply with instructions. Requires auth. Sends that person one confirmation email with a link and code; they receive nothing else until they confirm. I

cooper_list_owners

Use this when you need to check who the human owners of an inbox are and whether they have confirmed, before relying on cooper_notify_owner. Read-only; requires auth. Inputs: inbox_id (required). Returns {data:[{id, email, status (pending|v

cooper_notify_owner

Use this when the agent should tell its human owner(s) about progress, completion, a blocker, or a question by email. Requires auth. Sends a status email to every verified owner of the inbox (daily-digest owners get it in the next digest).

cooper_ask_owner

Use this when the agent needs a human decision and should wait for a typed answer. Requires auth. Sends a question email to every verified owner of the inbox. kind approve offers Approve and Deny (optional approve_label and deny_label). kin

cooper_get_question

Use this when you already have a question id from cooper_ask_owner and need its status or answer. Read-only; requires auth. Inputs: question_id (required), wait (optional long-poll seconds, 0 to 25, default 0). Returns the question with sta

cooper_get_tasks

Use this when you are waiting for a human's instructions or answer by email: it lists tasks created when a verified owner or allowlisted sender emails the inbox and the mail passes DMARC (or DKIM aligned with From). Read-only; requires auth

cooper_reply_task

Use this when you have an answer or result for a task from cooper_get_tasks and want to reply to the human in the same email thread. Requires auth. Sends a real email to the task's sender. Inputs: task_id (required), text (required; the rep

cooper_add_domain

Use this when the user wants to add a custom domain. Free includes 1. Requires auth. One call returns the SPF, DKIM, DMARC, and MX records to publish, plus a verify TXT. Inputs: domain (required hostname, such as agents.example.com), client

cooper_create_workspace

Use this when the signed-in parent account should give a project or another agent its own API key and a fixed inbox quota. Requires auth. Inputs: name (required; 1–64 characters), inbox_quota (required integer; how many inboxes that sub-acc

cooper_list_workspaces

Use this when you need the sub-accounts created by the signed-in parent, including each inbox quota and how many inboxes are in use. Read-only; requires auth; no inputs. Returns {data:[{id, name, inbox_quota, account_id, api_key_prefix, inb

cooper_get_workspace

Use this when you need one sub-account created by the signed-in parent, including its inbox quota and how many inboxes are in use. Read-only; requires auth. Inputs: workspace_id (required). Returns {id, name, inbox_quota, inboxes_used, acco

cooper_update_workspace

Use this when a parent should rename a sub-account or change how many live inboxes it may hold. Requires auth. Inputs: workspace_id (required), name (optional; 1–64 characters), inbox_quota (optional integer, at least 1). Returns the worksp

cooper_delete_workspace

Use this when a parent should remove a sub-account, its API key, and its mail. Requires auth. Destructive. Inputs: workspace_id (required), delete_inboxes (optional boolean). Returns {id, deleted:true, inboxes_deleted}. When the workspace s

cooper_delete_inbox

Use this when an inbox should be removed so its slot is free on the plan and on a workspace inbox quota. Requires auth. Deletes that inbox and its messages. Inputs: inbox_id (required; inbox id, username, or email). Returns {id, deleted:tru

cooper_update_inbox

Use this when an inbox should pause (stop sending and accepting new mail without deleting the address, threads, or history) or resume, or when you need to change its display name, metadata, signature, inbound screening, sender authenticatio

cooper_update_message

Use this when you need to change labels on a stored message, including marking it read. Requires auth. Works on a paused inbox, because this is triage and not a send. Inputs: inbox_id (required; inbox id, username, or email), message_id (re

cooper_update_messages

Use this when several stored messages should gain or lose the same labels, including marking a batch read. Requires auth. Works on a paused inbox, because this is triage and not a send. Inputs: inbox_id (required; inbox id, username, or ema

cooper_list_domains

Use this when you need the custom domains on the signed-in account, including DNS status. Read-only; requires auth; no inputs. Returns {object:"list", data:[{id, domain, status, status_detail, mail, records, warnings, dns}]}. Each record ha

cooper_verify_domain

Use this when DNS for a custom domain may have been published and you should check it now instead of waiting for the daily cron. Requires auth. Inputs: domain_id (required; the dom_… id from cooper_add_domain or cooper_list_domains). At mos

cooper_reply_message

Use this when you need to answer a message already in a Cooper inbox, with recipients and threading filled in for you. Requires auth. Sends real email and stores the copy on the same thread. Inputs: inbox_id (required; inbox id, username, o

cooper_forward_message

Use this when you need to forward a stored message to someone else, including a forwarded header block and the original attachments, on a new thread. Requires auth. Sends real email. Inputs: inbox_id (required; inbox id, username, or email)

cooper_wait_for_message

Use this when you are waiting for a reply or a verification code and you have no public URL for a webhook. Read-only; requires auth. Inputs: inbox_id (required; inbox id, username, or email), after (optional cursor or ISO-8601 timestamp; de

cooper_list_events

Use this when you need the recent event log for this account (message.received, message.held, message.sent, message.blocked, message.bounced, message.complained, task.received, owner.reply, domain.verified, draft.created, draft.approved, dr

cooper_list_threads

Use this when you need whole conversations instead of individual messages, for example to see who is in a thread and when the last reply arrived. Read-only; requires auth. Inputs: inbox_id (optional; inbox id, username, or email — omit to l

cooper_get_thread

Use this when you need every message in one conversation, oldest first, including extracted_text. Read-only; requires auth. Inputs: inbox_id (required; inbox id, username, or email), thread_id (required, thr_…), limit (optional, default 100

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; requires auth. Inputs: inbox_id (required; inbox id, username, or email), q (required; every word m

How to connect Cooper Email to Claude, Cursor or VS Code

Cooper Email runs as a hosted remote MCP server at https://cooperemail.com/mcp. Add that URL to your MCP client's config (Claude Code, Cursor, Windsurf or VS Code) and the tools appear immediately, no install required.

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

Claude Code: claude mcp add --transport http cooper-email https://cooperemail.com/mcp. VS Code's .vscode/mcp.json uses a servers key instead of mcpServers (see how). Servers that require OAuth or an API key will prompt on first use.