Cooper Agent Inbox

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.

AI, LLMs & Agents Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add cooper-email/cooper-email

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add cooper-email/cooper-email --skill cooper-agent-inbox
Manual install
git 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-agent-inbox ~/.claude/skills/cooper-agent-inbox

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Agent inbox basics with Cooper Email

Each Cooper inbox is a real address (`username@cooperemail.com`) that the agent
controls over HTTP (`https://cooperemail.com/api/v1`) or the hosted MCP server
(`https://cooperemail.com/mcp`). Cooper only sees mail sent to Cooper inboxes,
never the user's personal mailbox.

## 1. Key and inbox

OAuth clients (Cursor plugin, Claude, Claude Code, ChatGPT, Grok Bot): add
`https://cooperemail.com/mcp`, finish OAuth, then `cooper_create_inbox`.
Do not call `cooper_onboard` first. That tool's one-time key is a different
account and is not attached when OAuth is approved.

HTTP, or a client that only has a Bearer header:

1. If `COOPER_API_KEY` is set, check it: `curl -s https://cooperemail.com/api/v1/me -H "Authorization: Bearer $COOPER_API_KEY"`.
   HTTP 200 is good. `GET /api/v1/inboxes` lists inbox ids.
2. Otherwise onboard (no auth, no card). This does not sign an OAuth client in:

   ```bash
   curl -s https://cooperemail.com/api/v1/onboard \
     -H 'content-type: application/json' \
     -d '{"username":"research-bot-7f3a","owner_email":"human@example.com"}'
   ```

   `api_key` is shown once: save it as `COOPER_API_KEY` and never print it again.
   Send it as `Authorization: Bearer` on later calls, including MCP when the
   client has no OAuth. Save `inbox.id` as `$INBOX`. `owner_email` is optional;
   the human gets one confirmation email and can later approve sends and
Read the full skill on GitHub

Details

Skill name
cooper-agent-inbox
Path
skills/cooper-agent-inbox/SKILL.md
License
MIT
Repo updated
14 November 2026

FAQ

What does the Cooper Agent Inbox skill do?

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.

How do I install the Cooper Agent Inbox 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.

Productivity & NotesIn 1 list

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.

Productivity & NotesIn 1 list

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.

AI, LLMs & AgentsIn 1 list

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.

AI, LLMs & AgentsIn 1 list

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.

AI, LLMs & AgentsIn 1 list

Write Agents Md

agentkitco/agentkit-dev-skills

Draft a short, accurate AGENTS.md (and a CLAUDE.md bridge) for a repository from evidence in the repo. Use when a project has no agent instructions, or when asked to create or rewrite AGENTS.md.

AI, LLMs & AgentsIn 1 list

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.