Cooper Email

What Cooper Email MCP server does

Cooper Email MCP server gives an AI agent access to email inboxes hosted on cooperemail.com. An onboarding request can create an account, an inbox address, and an API key without requiring a dashboard. The service supports ordinary email workflows, including sending messages, reading received mail, searching, threads, attachments, and retry-safe sends identified by a client ID.

The service also supports human-in-the-loop workflows. An owner can be attached to an inbox after confirming by email. The agent can send progress, request-input, completion, or error updates, then retrieve owner replies as tasks and answer them in the same thread. Incoming replies include authentication results and a verified-owner indicator.

How it works

The hosted MCP endpoint is available at https://cooperemail.com/mcp and uses Streamable HTTP. MCP clients can authenticate with OAuth on first use or send an API key as a bearer token. The repository contains client-side SDKs, framework packages, MCP configuration, skills, and examples; the hosted email service itself is not included in the repository.

Cooper Email MCP server can be used directly by supported clients or through the repository’s Cursor plugin and skills. The plugin registers the hosted endpoint and provides guides for inbox management, checking and sending mail, owner approval, webhooks, idempotent operations, and related workflows.

Separate webhooks can report received messages, sent messages, incoming tasks, and owner replies. Webhook requests use HMAC-SHA256 signatures and can optionally be restricted to a single inbox.

Setup and configuration

For hosted MCP access, add https://cooperemail.com/mcp to the client’s MCP configuration, then complete OAuth sign-in or provide a bearer token containing a coop_live_… API key. The repository links to client-specific configuration examples for Cursor, VS Code, Windsurf, Codex CLI, and Cline. It also documents a Cursor plugin installation path and skills installation through the npx skills command.

An API key can be obtained by posting an agent username to https://cooperemail.com/api/v1/onboard. The returned key is shown once, so it should be stored securely, such as in COOPER_API_KEY, rather than committed to source control.

The repository also lists TypeScript and Python SDKs and packages for several agent frameworks. The README notes that registry releases are still in progress; packages not yet available from npm or PyPI may need to be installed from the repository.

Tools and capabilities

The documented Cooper Email MCP server use cases include:

• Creating individual, batch, or temporary inboxes
• Sending, replying to, forwarding, and scheduling email
• Reading, searching, and triaging messages
• Handling attachments, threads, and read/unread labels
• Creating drafts and using owner-approved sends
• Waiting for mail or owner replies through tasks
• Sending progress updates and daily digests to an owner
• Receiving signed event webhooks
• Retrying creates and sends with idempotency keys
• Managing custom-domain inboxes on supported plans

The repository’s skills also cover bounces, complaints, suppressions, and email threat-model patterns. SMS status is described as coming soon, with email alternatives available now.

Limitations and notes

The repository is the open-source client side rather than the hosted Cooper Email service. The MCP endpoint is remote, so local deployment instructions for the service are not provided. OAuth is available for the hosted endpoint, while API-key authentication is an alternative.

The README names Cursor, VS Code, Windsurf, Codex CLI, Cline, and Goose as supported through configuration, but Goose is not represented in the directory’s client slug list. A Claude connector and Claude Code plugin are also listed. Package publication is incomplete, and the cooper-email npm package is specifically described as not yet published in the hosted MCP setup section.

Owner approval depends on confirmation by email, and webhook consumers must validate the supplied HMAC-SHA256 signature. Custom-domain inboxes are limited to Starter and Pro plans according to the documented skills.