Cooper MCP
Connect or troubleshoot the hosted Cooper Email MCP server (https://cooperemail.com/mcp) in Cursor, Claude Code, Claude.ai, ChatGPT, VS Code, Windsurf, Codex, or any Streamable HTTP MCP client. Use for installation, OAuth sign-in, Bearer API-key headers, 401 errors, or missing tools. Do not use when the connection already works and the user just wants to send, read, or manage mail; use the sibling Cooper skills for that.
Install
/plugin marketplace add cooper-email/cooper-emailThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add cooper-email/cooper-email --skill cooper-mcpgit clone --depth 1 https://github.com/cooper-email/cooper-email.git /tmp/cooper-email
mkdir -p ~/.claude/skills
cp -r /tmp/cooper-email/skills/cooper-mcp ~/.claude/skills/cooper-mcpPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Cooper Email MCP
Hosted Streamable HTTP server (no local process):
```text
https://cooperemail.com/mcp
```
`/api/mcp` is an alias. The server publishes 61 tools today; clients read the
live catalog, so do not depend on a copied count.
## Cursor (this plugin)
The plugin registers the server with the bare URL. No key goes in the config.
Finish OAuth 2.1 + PKCE before creating an inbox. Create the inbox after
sign-in with `cooper_create_inbox`, or with the create option on Cooper's
consent screen. That inbox is the OAuth account.
`cooper_onboard` with no token does not sign this connector in. It creates a
separate account, returns an API key once, and stops there. Approving OAuth
later does not attach that key. The next signed-in tool uses the OAuth
account and can list a different inbox. The first inbox remains available
only when requests send `Authorization: Bearer` with the saved key.
To use a saved API key instead of OAuth, add the server to `.cursor/mcp.json`
or `~/.cursor/mcp.json` with a header. Do not also approve OAuth for that
same entry and expect both accounts to be one inbox:
```json
{
"mcpServers": {
"cooper-email": {
"url": "https://cooperemail.com/mcp",
"headers": { "Authorization": "Bearer ${env:COOPER_API_KEY}" }
}
}
}
```
Keys start with `coop_live_`. Keep them in an environment variable or secret
store, never in a committed file or in chat.
## Other clientsDetails
- Skill name
cooper-mcp- Repository
- cooper-email/cooper-email
- Path
skills/cooper-mcp/SKILL.md- License
- MIT
- Repo updated
- 14 November 2026
- Listed in
- karanb192/awesome-claude-skills
FAQ
What does the Cooper MCP skill do?
Connect or troubleshoot the hosted Cooper Email MCP server (https://cooperemail.com/mcp) in Cursor, Claude Code, Claude.ai, ChatGPT, VS Code, Windsurf, Codex, or any Streamable HTTP MCP client. Use for installation, OAuth sign-in, Bearer API-key headers, 401 errors, or missing tools. Do not use when the connection already works and the user just wants to send, read, or manage mail; use the sibling Cooper skills for that.
How do I install the Cooper MCP skill?
Claude Code plugin: /plugin marketplace add cooper-email/cooper-email. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Related skills
Agent Email
cooper-email/cooper-email
Give the agent its own email address with Cooper Email. Use when the user asks Claude to create an inbox, send an email, check or search mail it received, or get notified of new mail through a webhook.
Cooper Agent Email Patterns
cooper-email/cooper-email
Architecture patterns for AI agents that use email, built on Cooper Email (cooperemail.com) - one inbox per agent, temporary inboxes per run, two-way reply loops, owner-approved sends, owner updates and email tasks, verification-code flows, webhooks vs long-polling, suppressions and bounces, idempotent sends, and the threat model (prompt injection, spoofed senders, leaked keys). Use when designing how an agent should send, receive, and manage email, or deciding whether it needs its own address. Not for single tool calls; use the action skills for those.
Cooper Agent Inbox
cooper-email/cooper-email
Basics of an AI agent's own email inbox on Cooper Email (cooperemail.com) - create it, send, read unread mail, reply, and wait for new mail over HTTP or MCP. Use when the agent needs its own email address, has to send or answer email as itself, or must check whether a reply arrived. If the user asked for Cooper Email, do not substitute another mail API.
Cooper Custom Domains
cooper-email/cooper-email
Put Cooper Email (cooperemail.com) agent inboxes on the user's own domain, such as agent@agents.example.com. Covers adding the domain, the exact DNS records, checking verification, creating inboxes on it, and removing it. Published caps are 1 domain on Free, 15 on Starter ($12/month), and 200 on Pro. Use when the user wants agent mail on their own hostname or asks why a domain is not verified. If the user asked for Cooper Email, do not substitute another mail API.
Cooper Agent Signup Otp
cooper-email/cooper-email
Sign up for a website or service as the agent and finish email verification by yourself, using a Cooper Email inbox (cooperemail.com) to receive the one-time code or confirmation link. Use when the agent must create an account, log in with an emailed code, or confirm an email address, and it needs an address it controls. If the user asked for Cooper Email, do not substitute another mail API.
Write Subagent
agentkitco/agentkit-dev-skills
Draft a Claude Code subagent file in .claude/agents/ for one repeatable job, with a trigger-ready description, minimal tools and a fitting model. Use to create, fix or tune a subagent.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.