79trust / 100

Cooper Email

by cooperemail.com in Email & messaging

MCP serverPassing, checked 3 h ago

Email inboxes for AI agents: send, receive, search, drafts with owner approval, and webhooks.

https://cooperemail.com/mcp

Last 30 days

All checks passedSome failedAll failedNot checked
Uptime
100%
Response time
687 ms typical, 687 ms slowest 5%
Last check
3 h ago
Next check
in 4 h

How to call it

Add it to any MCP client that supports remote servers.

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

64 tools

  • 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. Inputs: username (required; 1–32 characters:

  • 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. Inputs: username (optional; 1–32 characters; becomes <username>@cooperemail.com; omit it and Cooper picks box plus 8 hex characters, the same ge

  • 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), prefix (optional; addresses become pre

  • 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 paused; omit to list every inbox), q (opti

  • 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. Inputs: inbox_id (required; inbox id, username, or email), to (required; array of recipient addresses), subject (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 use the account's newest inbox), limit (o

  • 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 message: from, to, cc, subject, text, h

  • 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, default 25, max 100), inbox_id (optional;

  • 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; every word must match subject, body text,

  • 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.received webhooks, like real inbound mai

  • 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 rejected), events (optional; any of message.rec

  • 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}, limits:{inboxes, emails_per_month, custom_d

  • 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 pro), email (optional receipt email), cl

  • 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. Inputs: inbox_id (required), email (requi

  • 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|verified|unsubscribed), digest, created_a

  • 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). Send a short title of 5-8 plain words th

  • 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. Inputs: inbox_id (optional; omit for a

  • 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 reply body), status (optional; pending, in_

  • cooper_add_domain

    Use this when the user wants mail on their own hostname and the account is on Starter or Pro. 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_id (optional id

  • 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-account may hold), client_id (optional idem

  • 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, inboxes_used, created_at}]}. Does not retur

  • 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, account_id, api_key_prefix, created_at}. Doe

  • 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 workspace {id, name, inbox_quota, inboxes_used

  • 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 still has inboxes and delete_inboxes is n

  • 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:true}. An approval inbox returns HTTP 202 a

  • cooper_update_inbox

    Use this when an inbox should stop sending and accepting new mail without deleting the address, threads, or history (for example while a human reviews it or during an incident), when it should start again, when you need to set its display name or metadata, when you need to change

  • 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 (required), add_labels (optional strings),

  • 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 email), message_ids (required; 1 to 50 uniq

  • 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, dns}]}. Each record has status valid, missing, or invalid and found from

  • 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). Runs the same DNS check as the cron, stores pe

  • 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, or email), message_id (required), text an

  • 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), message_id (required), to (required; r

  • 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; default is the time of this call, so only

  • 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, draft.rejected, draft.sent) without waitin

  • 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 list every inbox on the account), limit (

  • 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, max 200). Returns the thread plus mess

  • 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 must match subject, body text, from, or t

  • cooper_delete_thread

    Use this when a whole conversation should be removed. Requires auth. Deletes every message in the thread, plus attachment bytes and search rows. Owner tasks and updates are left in place. Inputs: inbox_id (required; inbox id, username, or email), thread_id (required). Returns {id

  • cooper_update_thread

    Use this when every message in a conversation should gain or lose the same labels, including marking the thread read. Requires auth. Works on a paused inbox. Inputs: inbox_id (required; inbox id, username, or email), thread_id (required), add_labels (optional strings), remove_lab

  • cooper_list_list_entries

    Use this when you need the addresses on an allow or block list. Read-only; requires auth. Inputs: direction (required; send, receive, or reply), type (required; allow or block), inbox_id (optional; inbox id, username, or email; omit for the account-wide list). Returns {data:[{obj

Security scan

  • Unusually long description in tool:cooper_add_domain
    cooper_add_domain Use this when the user wants mail on their own hostname and th…
  • Unusually long description in tool:cooper_update_inbox
    cooper_update_inbox Use this when an inbox should stop sending and accepting new…

Recent checks

WhenResultHTTPTime
3 h agoPassed200687 ms
12 h agoPassed200848 ms
21 h agoPassed200429 ms