Get your API key
AI & agents

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.

terminal
npx skills add mailkite/agent-skills

What's inside

FileWhat it covers
SKILL.mdThe end-to-end playbook: account → domain → DNS → webhook → send → confirm.
reference/access-methods.mdMCP vs CLI vs SDK vs REST — when to use each, with config.
reference/dns-providers.mdApply DNS on Cloudflare, GoDaddy, Namecheap, Route 53, or by hand.
reference/webhooks.mdInbound payload shape and signature verification.
reference/templates.mdTemplate model, CRUD, and sending a design test.
reference/api.mdEvery 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:

bash
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:

mcp.json
{
"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.