List your agent

Cooper Email

MCP server● Hosted · onlinev1.4.0

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

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: automate business workflows.
All AI agents to automate business workflows, ranked →

Similar tools

Listed for the same task: automate business workflows

Reviews

No review yet. Used Cooper Email? Be the first to help others choose.

What it does

Cooper Email is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: api integration. That makes it a candidate for tasks such as automate business workflows or build an internal tool.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.4.0
PriceNot in the registry
First seen27 Sept 2026
Last checked1d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)

Hosted endpoint

  • https://cooperemail.com/mcp streamable-http

In Claude Code: claude mcp add --transport http cooper-email https://cooperemail.com/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

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

Live check

Electra Index connected to the hosted endpoint 1d ago

ONLINE Cooper Email answered an MCP connection on 15 Nov 2026 and introduced itself as cooper-email 1.11.0 (MCP protocol 2025-03-26).

110 tools offered to AI assistants

  • 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, or mail to one plus address such as agent+orders@. Read-only; requires auth. Inputs: inbox_id
  • 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
Show 88 more
  • 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_domain_setup_link · Use this when a human must publish the DNS records for a custom domain. Requires auth. Inputs: domain_id (required; the dom_… id from cooper_add_domain or cooper_list_domains), expires_in_hours (optional integer from 1 to 168, default 72).
  • 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, including mail to one plus address. Read-only; requires auth. Inputs: inbox_id (required; inbox id, username, or email), after (optio
  • 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
  • cooper_delete_thread · Use this when a whole conversation should be removed permanently. Requires auth. Deletes every message in the thread, plus attachment bytes, search rows, the assignment, and the folder row. Owner tasks and updates are left in place. This ca
  • 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. Requires auth. Works on a paused inbox. Inputs: inbox_id
  • 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. Requires auth. Same permission as updating thread labels. Inputs: inbox_id (required; inbox id, usernam
  • 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. Requires auth. Same permission as updating thread labels. Inputs: inbox_i
  • cooper_unassign_thread · Use this when the assignee is done with a thread, or a worker should release its claim. Requires auth. Same permission as updating thread labels. Inputs: inbox_id (required; inbox id, username, or email), thread_id (required), assignee (opt
  • 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
  • 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 (required; allow or block), entry (required; email or domain), inbox_id (optional;
  • 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 reply), type (required; allow or block), entry (required; email or domain), inbox_
  • 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 reply), type (required; allow or block), entry (required; email or domain), inbox_
  • 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; requires auth. Inputs: inbox_id (required; inbox
  • 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. Inputs: inbox_id (required; inbox id, username, or email), owner_id (required),
  • 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. Requires auth. Optional input lifecycle_emails is on or off and sets whether this account rece
  • 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. Returns {object:"list", data:[{id, url, events, inbox_id, inbox_ids, client_id, en
  • 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), events (optional array), enabled (optional boolean; true re-enables and resets c
  • 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 hook. Fails with 404 webhook_not_found when the id is missing or belongs to anot
  • cooper_rotate_webhook_secret · Use this when a webhook signing secret should change without breaking receivers that still check the old secret. Requires auth. Inputs: webhook_id (required). Mints a new secret (whsec_…), stores it as the current secret, and keeps the prev
  • 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:{webhook_id}} and waits for the response. Returns {delivery:{id, status, respons
  • 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. Returns {object:"list", data:[{object:"suppression", address, reason, source_me
  • 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-wide row. Inputs: address (required; email). Returns the suppression with deleted
  • 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, then fires message.received and creates a task when the sender is a verified ow
  • 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), message_id (required), attachment_id (required), format (optional; text or base6
  • 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. Inputs: kind (required; events, usage, or rates), inbox_id (optional; inbox id, usern
  • 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; requires auth and message_read. No inputs. The pause is account-wide, so an inbox-scoped key returns the same account status. Re
  • cooper_create_draft · Use this when you want to prepare a message without sending it yet. Requires auth and message_send or draft_write. draft_write does not send mail. Scheduling a draft (send_at) counts as sending and needs message_send or draft_send. HTTP 403
  • 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 and message_read. Inputs: inbox_id (required), draft_id (required). Returns the draft. Another account'
  • cooper_list_drafts · Use this when you need drafts on one inbox or across the account. Read-only; requires auth and message_read. Inputs: inbox_id (optional; omit for every inbox this key can see), labels (optional; every listed label must match), limit (option
  • cooper_update_draft · Use this when a draft should change before it sends. Requires auth and message_send or draft_write. A key with only draft_send can set send_at and cannot edit other fields. This call does not send the draft. Inputs: inbox_id (required), dra
  • cooper_delete_draft · Use this when a draft should be discarded, including a scheduled send you want to cancel. Requires auth and message_delete, message_send, or draft_write. Inputs: inbox_id (required), draft_id (required). Deletes the draft and its attachment
  • cooper_send_draft · Use this when a draft should be sent now. Requires auth and message_send or draft_send. draft_write alone cannot send. Inputs: inbox_id (required), draft_id (required), add_labels, remove_labels, idempotency_key (optional Idempotency-Key).
  • 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; requires auth
  • 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; requires auth. Inputs: inbox_id and owner_id (optional; both together return that owner's effective style). Returns {accoun
  • cooper_set_owner_preferences · Use this when the human asks for shorter, longer, or friendlier email from Cooper. Requires auth. Sets the account default (omit owner_id; needs an unscoped key with owner_manage) or one owner's style (inbox_id and owner_id). Inputs: style
  • 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; requires auth. No inputs. Returns {object:"list", data:[{object:"oauth_grant", id, client_id, client_name, red
  • cooper_revoke_oauth_grant · Use this when an OAuth app should lose access to this account. Requires auth. Destructive. Inputs: client_id (required; the OAuth client id from cooper_list_oauth_grants). Deletes every access and refresh token for that client on this accou
  • cooper_list_event_subscriptions · Use this when you need to see which MCP event subscriptions are watching inboxes on this account. Read-only. Requires auth. Inputs: none. Returns {object:"list", data:[{object:"event_subscription", id, name, inbox_id, inbox, callback_host,
  • cooper_delete_event_subscription · Use this when an MCP event subscription should stop. Requires auth. Inputs: id (required, mes_… from cooper_list_event_subscriptions). Keeps the row for audit and returns it with status ended and retained true. An ended row does not deliver
  • cooper_set_addons · Use this when a Starter or Pro account needs more inboxes, custom domains, or monthly emails than the plan includes. Requires auth. A sub-account key returns HTTP 403 workspace_billing_forbidden. Free, a grandfathered account, and an accoun
  • cooper_poll_events · Use this when a scheduled agent needs Cooper events without a public webhook URL and without storing a cursor. Requires auth and message_read (a full-access key or OAuth token can call it). Creates a durable event consumer for client_id on
  • cooper_commit_events · Use this after you have processed a page from cooper_poll_events. Requires auth and message_read. Inputs: client_id (the consumer id or client_id) and cursor (the commit_cursor you received, an evc1 cursor). Returns the consumer. cursor on
  • cooper_list_event_consumers · Use this to see the durable event consumers on this account. Read-only; requires auth and message_read. No inputs. Returns {object:"list", data:[{object:"event_consumer", id, client_id, inbox_id, types, cursor, created_at, updated_at, last_
  • cooper_delete_event_consumer · Use this to remove a durable event consumer and its cursor. Requires auth and message_read. Input: client_id (consumer id evcon_… or the client_id). Returns {id, client_id, deleted:true}. Another account's consumer, or a consumer pinned to
  • cooper_list_rules · Use this to see the deterministic rules on one inbox, in the order they run. Read-only; requires auth and message_read. Input: inbox_id (required; inbox id, username, or email). Returns {object:"list", data:[inbox_rule]}. Each rule has id,
  • 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. Requires auth and message_update. Creating a rule with forward_to or auto_reply also needs
  • cooper_update_rule · Use this to change a stored inbox rule. Requires auth and message_update. Replacing actions with forward_to or auto_reply, or enabling a disabled rule that has them, also needs message_send. HTTP 403 permission_denied with param actions oth
  • cooper_delete_rule · Use this to remove one inbox rule and its auto-reply cooldown rows. Requires auth and message_update. Inputs: inbox_id (required), rule_id (required). Returns {id, deleted:true}. An unknown rule is HTTP 404 rule_not_found. Another account's
  • 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; requires auth and message_read. Inputs: inbox_id (required), message_id (required), and optional name, co
  • cooper_get_idempotency_key · Use this to see whether an Idempotency-Key is in progress, done, or unknown. Read-only; requires auth and message_read. Inputs: key (required; the Idempotency-Key value). Returns {key, state, endpoint, inbox_id, message_id, created_at, expi
  • 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. Requires auth and message_send. Inputs: key (required). Deletes an unknown key, including a stale in_progress row older than
  • cooper_resolve_idempotency_key · Use this when an unknown Idempotency-Key matches a message you found in the sent folder. Requires auth and message_send. Inputs: key (required), message_id (required). Marks the key done and links that message so a later retry replays it an
  • cooper_list_request_refusals · Use this when a Cooper call failed and you need to see recent refusals and their error codes. Read-only; requires auth. Inputs: status (optional HTTP 4xx code), code (optional error code), api_key_id (optional), inbox_id (optional inbox id)
  • cooper_list_forwarding · Use this to see the external addresses that receive a copy of every inbound email on one inbox. Read-only; requires auth and message_read. Input: inbox_id (required; inbox id, username, or email). Returns {object:"inbox_forwarding", destina
  • 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. Requires auth and inbox_update. Inputs: inbox_id (required), email (required), client_id (optional, 1–128 characters).
  • cooper_remove_forwarding · Use this to stop copying inbound mail to one external address. Requires auth and inbox_update. Inputs: inbox_id (required), destination_id (required; ifd_ id or the email). Returns {id, email, deleted:true}. An unknown destination is HTTP 4
  • cooper_set_forwarding · Use this to keep only some already-verified external addresses on an inbox. Requires auth and inbox_update. Inputs: inbox_id (required), emails (required array). Each address must already be verified on this inbox. Pending addresses are lef
  • 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; requires auth. Inputs: inbox_id (optional; inbox id, username, or email; omit to read the whole account), address (requi
  • cooper_security_check · Use this before an agent inbox sends mail. Read-only; requires auth and inbox_read. Input: inbox_id (optional; inbox id, username, or email). Omit inbox_id when the key is limited to one inbox and Cooper grades that inbox. An account-wide k
  • cooper_provision_phone_number · Provision a US local number for an inbox. Requires auth. Free includes no numbers (HTTP 402). Starter caps at 3. Pro includes 3 and caps at 25. Each billable number is $3/month with 100 segments. With COOPER_SMS_BILLING=stripe the number is
  • cooper_get_phone_number · Read the active phone number on an inbox. Requires auth. Input: inbox_id.
  • cooper_release_phone_number · Release the inbox phone number at the provider and on Cooper. Requires auth. Input: inbox_id and confirm true. The same account cannot provision that E.164 again for 30 days. With COOPER_SMS_BILLING=stripe, releasing a billable number lower

The first 100 are shown.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://cooperemail.com/mcpDECLAREDSRC-001 Official MCP Registry1d ago
Version1.4.0DECLAREDSRC-001 Official MCP Registry1d ago
Repositoryhttps://github.com/cooper-email/cooper-emailDECLAREDSRC-001 Official MCP Registry1d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry1d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry1d ago
Websitehttps://cooperemail.comDECLAREDSRC-001 Official MCP Registry1d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry1d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry1d ago

Change history

  • VERSION11 Oct 2026
    1.2.0 → 1.4.0
  • VERSION10 Oct 2026
    1.0.2 → 1.2.0
  • VERSION29 Sept 2026
    1.0.1 → 1.0.2
  • VERSION29 Sept 2026
    1.0.0 → 1.0.1
  • NEW27 Sept 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Cooper Email? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor Cooper EmailLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Cooper Email?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/cooper-email?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/cooper-email/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about Cooper Email

How do I connect Cooper Email?

Use the hosted endpoint https://cooperemail.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does Cooper Email offer?

When Electra Index connected on 15 Nov 2026, it listed 110 tools: cooper_onboard, cooper_create_inbox, cooper_create_inboxes, cooper_list_inboxes, cooper_send_message, cooper_list_messages, cooper_get_message, cooper_search and more. The full list is in "Live check" above.

Is Cooper Email online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.

What can I use Cooper Email for?

Based on its description, it is most relevant to: automate business workflows, build an internal tool, integrate two APIs, build data pipelines.