Name: Cooper Email
Author: com.cooperemail

Tools observed via MCP handshake

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. Creat
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 (option
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
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
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. Inp
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; req
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 (
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 (requ
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
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 en
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
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;
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 th
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 confirma
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
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 eve
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
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
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 recor
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
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; n
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. Inp
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;
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 (opti
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. Inp
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 dur
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
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
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_i
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 store
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 a
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;
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
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; req
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
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. Inpu
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
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. In
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;
cooper_get_list_entry — Use this when you need one address or domain on an allow or block list. Read-only; requires auth. Inputs: direction (required; send, receive, or reply), type (r
cooper_create_list_entry — Use this when an agent should only mail approved recipients, or should ignore unwanted senders. Requires auth. Inputs: direction (required; send, receive, or re
cooper_delete_list_entry — Use this when an address or domain should leave an allow or block list. Requires auth. Deletes that one entry. Inputs: direction (required; send, receive, or re
cooper_get_inbox — Use this when you need one inbox's address, display name, metadata, status, client_id, screening, or send_mode and you already have its id, username, or email.
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. Requires auth.
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. Read-only; req
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; requires auth. No inputs. Re
cooper_update_webhook — Use this when a webhook URL, event list, inbox filter, or enabled flag should change. Requires auth. Inputs: webhook_id (required), url (optional http(s) URL),
cooper_delete_webhook — Use this when a webhook should stop receiving events and be removed. Requires auth. Inputs: webhook_id (required). Returns {id, deleted:true}. This removes the
cooper_test_webhook — Use this when you need to confirm a webhook URL accepts a signed POST right now. Requires auth. Inputs: webhook_id (required). Sends {type:"webhook.test", data:
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; requires auth. Inputs: none.
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. Requires auth. Deletes that one account-w
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. Requires auth. Removes the held label,
cooper_get_attachment — Use this when you need the text of one attachment, or its bytes as base64. Read-only; requires auth. Inputs: inbox_id (required; inbox id, username, or email),
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; requires auth and message_read. Input
cooper_create_draft — Use this when you want to prepare a message without sending it yet. Requires auth. Inputs: inbox_id (required; inbox id, username, or email), to, cc, bcc, reply
cooper_get_draft — Use this when you need one draft, including its labels, attachments, send_at, send_status, and approval_status. Read-only; requires auth. Inputs: inbox_id (requ
cooper_list_drafts — Use this when you need drafts on one inbox or across the account. Read-only; requires auth. Inputs: inbox_id (optional; omit for every inbox this key can see),
cooper_update_draft — Use this when a draft should change before it sends. Requires auth. Inputs: inbox_id (required), draft_id (required), and any of to, cc, bcc, reply_to, subject,
cooper_delete_draft — Use this when a draft should be discarded, including a scheduled send you want to cancel. Requires auth. Inputs: inbox_id (required), draft_id (required). Delet
cooper_send_draft — Use this when a draft should be sent now. Requires auth. Inputs: inbox_id (required), draft_id (required), add_labels, remove_labels, idempotency_key (optional

when	check	result	http	latency	detail
2 h ago	mcp initialize	ok	200	149 ms	server cooper-email 1.1.0 · protocol 2025-03-26 · 60 tools
9 h ago	mcp initialize	ok	200	1496 ms	server cooper-email 1.1.0 · protocol 2025-03-26 · 60 tools
15 h ago	mcp initialize	ok	200	318 ms	server cooper-email 1.1.0 · protocol 2025-03-26 · 51 tools
22 h ago	mcp initialize	ok	200	150 ms	server cooper-email 1.1.0 · protocol 2025-03-26 · 46 tools
29 h ago	mcp initialize	ok	200	182 ms	server cooper-email 1.1.0 · protocol 2025-03-26 · 22 tools
35 h ago	mcp initialize	ok	200	158 ms	server cooper-email 1.1.0 · protocol 2025-03-26 · 22 tools
2 d ago	mcp initialize	ok	200	140 ms	server cooper-email 1.1.0 · protocol 2025-03-26 · 21 tools
2 d ago	mcp initialize	ok	200	166 ms	server cooper-email 1.1.0 · protocol 2025-03-26 · 21 tools
2 d ago	mcp initialize	ok	200	204 ms	server cooper-email 1.1.0 · protocol 2025-03-26 · 21 tools
3 d ago	mcp initialize	ok	200	130 ms	server cooper-email 1.1.0 · protocol 2025-03-26 · 16 tools

Cooper Email

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from