WhatsApp MCP Platform

A Bun-workspace monorepo for the three independently deployed applications defined by ADR 0002:

• apps/web: the Next.js product UI on Vercel

• apps/api: the public Cloudflare API Worker

• apps/provider-control: the private Cloudflare Worker reachable only through an API service binding

Shared modules have explicit subpath exports and no catch-all barrel:

• packages/domain: pure domain rules

• packages/contracts: product and MCP schemas

• packages/db: database configuration, migrations, and tenant repositories

• packages/wasender: separate session, control, and webhook-normalization boundaries

Local verification

bun install --frozen-lockfile
bun run format:check
bun run lint
bun run typecheck
bun run validate:infra
bun run test
bun run build
bun run manifests:validate
bun run infra:validate

Run a deployable locally with Turbo filtering, for example:

bun run dev --filter=@whatsapp-mcp/web

Production and test Effect roots are separate modules. Runtime configuration cannot select a test Layer, and the production build inspection fails if a test Layer marker enters a deployable artifact.

See deployment configuration and the deployment runbook.

The OpenTofu compute topology in infra/compute uses separate state and authority for development, preview, and production. It declares the Vercel web project, the public API Worker custom-domain route, and the private provider-control Worker service binding.

Related MCP server: WhatsApp MCP Server

Sandcastle

Sandcastle runs issue agents in isolated Docker worktrees. After authenticating Docker, GitHub CLI, and Codex:

bun run sandcastle:build-image
bun run sandcastle