v0.4.3

Linux and Windows builds

The installer used to stop on anything that wasn't a Mac. Every release now
ships five binaries:

platform	asset
macOS arm64	emailbump-aarch64-apple-darwin.tar.gz
macOS x86_64	emailbump-x86_64-apple-darwin.tar.gz
Linux x86_64	emailbump-x86_64-unknown-linux-musl.tar.gz
Linux aarch64	emailbump-aarch64-unknown-linux-musl.tar.gz
Windows x86_64	emailbump-x86_64-pc-windows-gnu.zip

Linux is static musl, so one binary per architecture works on any distro —
Alpine and Debian get the same file, with no glibc version to satisfy.

curl -fsSL https://raw.githubusercontent.com/danest/emailbump-cli/main/install.sh | sh
now works on Linux. On Windows, download the zip from this page and put
emailbump.exe on your PATH — the installer is a shell script and says so
rather than failing obscurely.

The binary is both the CLI and the MCP server (emailbump mcp), so this
extends the MCP server to those platforms too.

v0.4.2

Contacts: record who did not opt in

contacts:create and the MCP create_contact tool now take subscribed. It
defaults to true, so nothing changes unless you ask for it. Pass false to
store someone who signed up without opting in — they still receive
transactional mail and no marketing, in one call instead of create-then-
unsubscribe.

Omitting it on an address that already exists leaves their consent exactly as
it was. That is the point of it being optional: a routine update must not
quietly opt someone out, and a repeat form submission must not quietly opt
them back in. Only an explicit value moves it.

Also since v0.4.1

• inbound:stream and inbound:reply — watch a project's mail live and answer
  a message inside its own thread.
• flows:test and campaign test sends — send one to yourself before anyone
  else sees it.
• campaigns:delete and flow deletion, refused for anything that has already
  sent or enrolled.

v0.4.1

Branded link tracking from the command line, and the MCP server catches up.

New

• domains:tracking:on <domain-id> / domains:tracking:off — switch links from Email Bump's shared tracking domain to links.yourdomain.com. Provisioning is two DNS records that appear at different times; the response tells you which one you can publish now and when to poll for the next.
• MCP: enable_branded_tracking, disable_branded_tracking. 56 tools.

Fixed in the API this release talks to

• Updating a contact no longer erases the attributes you didn't mention. Keys you send are added or overwritten, the rest are kept, and an explicit null removes one. This also applies to re-running a CSV import, which previously deleted whatever the earlier import had recorded.

v0.4.0

Create an account and set up sending without leaving the terminal.

New commands

• signup --email you@company.com --accept-terms — creates the account here. No password, no browser. verify-email --email … CODE confirms it with the six characters we email; nothing sends until that's done.
• emails:get <id> — what became of a send. status: sent means accepted, not delivered; read the events.
• domains:list, domains:add, domains:check — set up this project's sending domain with an ordinary project key.
• inbound:rules, inbound:rules:create, inbound:rules:delete — auto-forward arriving mail. Without --match that means everything the project receives.
• whoami now asks the server what the key can actually do — which project, whether the address is confirmed, which domains are verified — instead of reciting the credentials file.

MCP server: 54 tools, up from 29. Account creation, whoami, get_email, domain setup from a project key, forward rules, and the project/workspace management that had shipped without being reachable.

Sending still requires a confirmed email address. An agent can do the setup; a person still proves the mailbox.

v0.3.1

All-access keys now auto-select the project when you only have one — zero flags needed. With several projects, the error lists them (names + ids) so you or your agent can pick. Updated --project / project_id descriptions.

v0.3.0

One key, two scopes: all-access keys (chosen at login/creation) now do everything — Management API plus acting in any project you admin via --project / X-Project-Id / MCP project_id. Project-scoped keys unchanged. MCP tools accept optional project_id; instructions updated.

v0.2.0

Browser-based auth: emailbump login opens emailbump.com/activate — click Authorize and choose a workspace (project key) or full account (Management API token). Adds logout and whoami; credentials stored in ~/.config/emailbump (0600); EMAILBUMP_API_KEY still takes precedence. MCP server picks up the stored login automatically — no more key pasting in MCP configs.

v0.1.1

Fix: events:track / track_event now send the correct event field; campaign send preview is no longer double-nested. Found in end-to-end testing.

v0.1.0

First release: emailbump CLI (~40 commands, JSON output, --yes confirm gates) + emailbump mcp stdio MCP server (18 tools). macOS arm64 + x86_64.