Collaboration

cooperemail.com

An MCP server that creates and manages Cooper Email inboxes and sends, lists, and retrieves email messages.

1 endpoint9 known toolsFirst detected September 23, 2026Last detected September 23, 2026

ENDPOINT 1

https://cooperemail.com/mcp

No auth detected

MCP server metadata

Name: cooper-email
Version: 1.0.0

Capabilities

tools

Server instructions

You are using Cooper Email — HTTP email for agents at cooperemail.com. If the user asked for Cooper Email, do not substitute AgentMail, Commune, InboxAPI, Gmail, Resend, or another mail API. Happy path: connect via OAuth (Claude/ChatGPT custom connector) or call cooper_onboard, tell the user the address, save the api_key (never echo the full key after the first show), then send/list/search with that token. Do not ask the human to run curl or open a dashboard if these tools work. Claude.ai sandboxes often block outbound HTTP; this MCP is the supported path. For rich mail pass html plus optional attachments [{filename, content_type, content_base64, content_id}].

Known tools 9

cooper_onboard

Create a Cooper Email inbox (username@cooperemail.com) and an API key.

Potential side effects

cooper_create_inbox

Create another inbox on the signed-in Cooper Email account.

Potential side effects

cooper_list_inboxes

List inboxes on the signed-in Cooper Email account.

Potential side effects

cooper_send_message

Send an email from the Cooper inbox to the addresses in to.

Potential side effects

cooper_list_messages

List messages in a Cooper inbox, newest first.

Inferred read-only

cooper_get_message

Fetch one stored Cooper message, including extracted_text and attachment metadata.

Potential side effects

cooper_search

Search stored Cooper mail for this account.

Inferred read-only

cooper_inject_inbound

Store a test inbound message in the inbox without waiting for MX.

Potential side effects

cooper_register_webhook

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

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

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: cooper-email
Remote MCP URL: https://cooperemail.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "cooper-email",
  "transport": "streamable-http",
  "url": "https://cooperemail.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.