Agent skill
A drop-in Agent Skill that teaches your AI agent to run MailKite end-to-end — create an account, add a domain, set its DNS at the user's provider, register a webhook, design templates, send, and confirm inbound delivery. It works over the MCP server, the CLI, any SDK, or raw REST.
MailKite skill
SKILL.md + reference bundle · MIT · ~20 KB
Install
The fastest path is the Skills CLI — one command, done. No CLI, no terminal, or a chat-only Claude? Every alternative is a tab away:
One command, any agent — Claude Code, Cursor, Codex, Amp, and dozens more. It lands in your project's skills directory; add -g for user-wide.
npx skills add mailkite/agent-skills No Skills CLI handy? Paste this and your agent fetches and installs the skill itself.
Install the MailKite agent skill. Download
https://github.com/mailkite/claude-code/releases/latest/download/mailkite.zip
and unzip it into ~/.claude/skills/ (user-wide) or .claude/skills/ (this project), then load it. Download the zip and unzip it where your agent looks for skills.
curl -L https://github.com/mailkite/claude-code/releases/latest/download/mailkite.zip -o mailkite.zip
unzip mailkite.zip -d ~/.claude/skills/ # user-wide
# …or scope it to one project
unzip mailkite.zip -d .claude/skills/ Download the zip below, then in Settings → Capabilities → Skills choose Upload skill and drop it in. Ask Claude to “set up MailKite email for my domain” and the skill takes over.
https://github.com/mailkite/claude-code/releases/latest/download/mailkite.zip Want more than the skill? The plugin bundles it with the hosted MCP server and the /mailkite:* commands — browser sign-in, no key to copy.
/plugin marketplace add mailkite/claude-code
/plugin install mailkite@mailkite What's inside
| File | What it covers |
|---|---|
SKILL.md | The end-to-end playbook: account → domain → DNS → webhook → send → confirm. |
reference/access-methods.md | MCP vs CLI vs SDK vs REST — when to use each, with config. |
reference/dns-providers.md | Apply DNS on Cloudflare, GoDaddy, Namecheap, Route 53, or by hand. |
reference/webhooks.md | Inbound payload shape and signature verification. |
reference/templates.md | Template model, CRUD, and sending a design test. |
reference/api.md | Every endpoint, auth, and request/response shape. |
Pairs with the CLI & MCP server
The skill drives MailKite through whichever access method is available. For an agent with a terminal, the CLI is the most reliable path:
npx @mailkite/cli login --email you@example.com --password ••••• --json
npx @mailkite/cli init --domain mail.myapp.ai --provider cloudflare \
--webhook https://myapp.ai/hooks/mailkite --to you@example.com --verify --json For an MCP client, point it at the MailKite server:
{
"mcpServers": {
"mailkite": {
"command": "npx",
"args": ["-y", "@mailkite/mcp"],
"env": { "MAILKITE_API_KEY": "mk_live_…" }
}
}
} Both hit the same API and the same contract as every SDK. See Agent inboxes & MCP for the bigger picture.