mailexodus

# mailexodus Landing site, public migration pages, CLI package, MCP server, and agent skill for mailexodus. mailexodus helps teams migrate between email platforms without rebuilding every flow by hand. It reads platform APIs, normalizes contacts, segments, templates, and automations into a portable schema, then renders a destination plan. The project is intentionally platform-agnostic; destination adapters can share the same normalized source model. ## App ```bash pnpm install pnpm dev pnpm build ``` Key routes: - `/` landing page - `/migrations` migration page index - `/migrating-from/klaviyo/to/sequenzy` and the rest of the generated source/destination matrix - `/migrate/klaviyo/sequenzy` compatibility route for the same article - `/alternatives/klaviyo` and the rest of the `21+ best alternatives for X` listicles ## Package The npm package lives in `packages/mailexodus` in this repo. CLI, MCP, and skill source are included here; they are not separate repositories. CLI and MCP implementation source is TypeScript in `packages/mailexodus/src`, compiled to `dist` before packing or publishing. ```bash pnpm --filter mailexodus build pnpm --filter mailexodus pack node packages/mailexodus/bin/mailexodus.js adapters node packages/mailexodus/bin/mailexodus.js coverage node packages/mailexodus/bin/mailexodus.js info klaviyo node packages/mailexodus/bin/mailexodus.js reference --from klaviyo --to mailchimp node packages/mailexodus/bin/mailexodus.js migrate --from klaviyo --to sequenzy --dry-run ``` It exposes: - CLI: `mailexodus` - MCP server: `mailexodus-mcp` - Skill: `packages/mailexodus/skill/SKILL.md` The provider matrix and route references are exposed in the app, CLI, MCP server, and skill. Use `coverage` for every provider, `info <provider>` for provider-level source/destination coverage, and `reference --from <source> --to <destination>` for endpoint-level route details before promising a migration. ## Publish ```bash pnpm --filter mailexodus publish --access public ``` The package name `mailexodus` was available on npm when checked during setup. GitHub Actions can also publish with provenance through `.github/workflows/publish-npm.yml` after `NPM_TOKEN` is configured. ## Deploy ```bash vercel --prod ``` The app is a standard Next App Router project and deploys from the repository root with `vercel.json`. See `docs/deploy.md` for the full release checklist.