Highlights
- The app is now published under its author's name. The macOS bundle identifier
changed fromcom.lokilabs.EmailLocalMCPtopl.marcinwalendowski.EmailLocalMCP.
This one needs a manual reinstall. Sparkle identifies an app by its bundle
identifier, so an installed 0.2.0 will not see this update and will keep reporting
itself up to date. Download the DMG below and drag it over your existing copy — your
accounts and credentials survive, because neither~/.email-local-mcp/accounts.json
nor the Keychain entries are keyed on the bundle id. Verified on a real install.
Auto-update resumes normally from 0.3.0 onward. - Three security advisories patched, including one high (
fast-urihost confusion).
npm auditreports zero. list_accountsnow answers where your mail is handled, per account, so an agent
asked the question replies from data rather than from the README.
Changes
See the 0.3.0 section of the changelog.
Notable non-change: Composio support was built as a third way to connect a mailbox and
is deliberately not in this build. Composio never releases the OAuth token, so such
an account's mail would be fetched and sent by their servers — and this app is sold on
the promise that your mail never leaves your machine. The code lives in src/hosted/,
excluded from the build, for a hosted deployment where that is what a user signed up
for. A guard now fails the build if anything shipped ever imports it.
Install
Download Email-Local-MCP-0.3.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.
CLI only: npx -y email-local-mcp or brew install marcinwalendowski/tap/email-local-mcp
Known limitations
- Upgrading from 0.2.0 is manual, once, because of the bundle identifier change above.
- 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 (a Developer ID signature will end that).