Mailkube CLI

What it does

The mailkube CLI is a single binary that sends email, manages scheduled sends, and receives webhook events on your machine. It speaks to the same REST API and the same submission host your application does, so what works from the terminal works from your code.

It covers the send path and the local development loop, on purpose. Domain setup, API keys, webhook endpoints, templates, suppressed recipients, and audience management stay in the dashboard at app.mailkube.com. Run mailkube dashboard and it prints the right page for anything it doesn’t handle itself.

Key benefits

• One command, two transports. mailkube emails send builds a message from flags, a JSON payload, or a saved template, then delivers it over the REST API or over SMTP with a single --transport flag. Same message shape either way, so switching transports is a one-word change, not a rewrite.
• Webhooks without deploying anything. mailkube webhooks listen receives real events on your machine while you write the handler that will consume them, and forwards or records them as you go. --exit-after and --exit-timeout turn a listener into an assertion a CI job can make.
• Built for coding agents, not just humans. mailkube skill install writes an embedded skill file, by default to .claude/skills, that tells a coding assistant the things --help cannot: branch on exit code rather than message text, run --dry-run before every real send, and which commands do not exist on purpose (there is no emails get, emails list, or --wait, because mailkube does not serve past state).
• Scriptable by default. Output is human-readable on a terminal and JSON everywhere else, with no flag to remember either way, and the exit codes are a stable contract you can branch on.

Getting started

1. Install with Homebrew, Scoop, the shell installer, go install, or a container image
2. Run mailkube auth login (or mailkube init for guided setup)
3. Send a first message with mailkube emails send --dry-run to see exactly what would go out before it is real
4. Run mailkube webhooks listen to watch delivery events arrive locally
5. If a coding agent drives your terminal, run mailkube skill install so it gets the CLI’s rules instead of guessing at them

The CLI is early: v1.0.0 has shipped, but the command surface is still growing. See the quickstart for the full walkthrough.