Skip to content

Email Local MCP v0.2.0

Choose a tag to compare

@MarcinWalendowski MarcinWalendowski released this 01 Aug 15:29
· 9 commits to main since this release

Highlights

  • Your accounts come across on their own. If you used this project under a previous name (anymail-mcp, or gmail-mcp before that), the first start of v0.2.0 carries your account registry, App Passwords and OAuth refresh tokens forward. Nothing to run.

    v0.1.0 shipped deliberately without this, on the reasoning that the install base was small enough that re-adding accounts was cheaper. That got the comparison backwards: the maintainer pays a compatibility path once, but every user pays "re-add everything" individually, on opening a working app and finding it empty with nothing saying their data is still on disk. Fixed.

Changes

Added

  • Automatic import from a previous install. The registry with its default / read-only / provider flags, App Passwords, and OAuth refresh tokens plus client secrets. email-local-mcp import-legacy [--force] is the explicit form.

    Four rules, because every failure mode of a migration looks like success:

    • Copied, never moved. ~/.anymail-mcp/ and the old Keychain items are left exactly as they were. Delete them by hand once you are satisfied.
    • Merge, never overwrite. An account already configured under the new name wins, including its credential and its default flag.
    • Once, then never again. A marker at ~/.email-local-mcp/legacy-import.json means an account you delete later stays deleted.
    • Never fatal, never half-marked. A locked Keychain cannot stop the server starting, and does not write the marker either, so the next start retries. An account imported without its credential would look configured and fail on first connect.

Fixed

  • The CLI could never report failure to a script. process.exit(0) in the command branch overwrote process.exitCode, so a subcommand signalling partial failure exited 0 anyway.

Install

Download Email-Local-MCP-0.2.0-universal.dmg below (one universal build for Apple Silicon and Intel, Node is bundled, no prerequisites). Open it and drag Email Local MCP to Applications. The build is ad-hoc signed and not yet notarized, so the first launch is blocked: open System Settings > Privacy & Security, scroll to the "Email Local MCP was blocked" notice, and click Open Anyway.

Already running v0.1.0? The app checks for updates on launch and every 6 hours and installs them itself.

CLI only: npx -y email-local-mcp — or claude mcp add email-local -- npx -y email-local-mcp.

Known limitations

  • Not notarized yet, so the first launch needs the Gatekeeper "Open Anyway" step.
  • macOS re-shows the Keychain "Always Allow" prompt after each app update while builds are ad-hoc signed.
  • On a macOS beta/seed build, brew install of the formula can be blocked by Homebrew demanding an Xcode version Apple has only shipped as a Beta. Use the cask or npx until a stable Xcode for your macOS ships.