Cloud MCP relay for WhatsApp — lets AI assistants (Claude, ChatGPT, Cursor, etc.) interact with your WhatsApp conversations through the Model Context Protocol.
Setup guide:kaptionai.com/mcp — connect WhatsApp to Claude, ChatGPT or Cursor.
Use WhatsApp from AI apps through the Kaption extension. OAuth 2.1 relay that cannot read messages.
2026-11-09
ดาว
—
เครื่องมือ
—
อัปไทม์
—
Live at:mcp.kaptionai.com (canonical) and
mcp-ext.kaptionai.com (backward-compatible alias for existing connections)
The relay cannot read your messages. It forwards MCP tool calls between the AI client and the Kaption browser extension, which processes everything locally in your browser. Its source code is public (BUSL-1.1), so you can verify it yourself.
Download image/video/audio/document from a message
manage_chat
Archive, pin, mute, mark read/unread, set/clear draft
manage_reminders
Create/list/complete/delete personal reminders
manage_scheduled_messages
Schedule messages for future delivery — from Kaption's number (bot, default) or from your own number on this computer (mode: "local", also to groups)
manage_lists
Manage personal chat lists (custom categories)
list_contacts, get_contact, get_contact_groups
Read contacts and their group memberships
list_groups, get_group
Read cached or live group metadata
export_contacts
Export contacts as CSV or JSON
get_analytics
Analyze WhatsApp activity, rankings, response times, and exports
get_api_info is local-only and is deliberately excluded from the cloud
surface because it returns private REST connection credentials.
Deployment Security
Every deployment is cryptographically signed and recorded in a tamper-evident transparency chain. See SECURITY.md for full details.
Pipeline
GitHub Actions (push to main)
│
├─ 1. Run tests
├─ 2. Build worker (OpenNext + wrap)
├─ 3. SHA-256 manifest every generated code and asset file
├─ 4. Pre-deploy: Sigstore sign the manifest → Rekor log
├─ 5. Deploy to Cloudflare
├─ 6. Post-deploy: verify hash unchanged, sign attestation → Rekor
└─ 7. Append to transparency chain (hash-linked)
Daily heartbeat redeploys (6am UTC) ensure the chain stays active even without code changes.
Deploys are gated — do NOT run wrangler deploy locally
All production deploys go through GitHub Actions. Multiple layers enforce this:
wrangler.jsonc is gitignored; scripts/build-config.mjs renders it from wrangler.template.jsonc and refuses to run unless GITHUB_ACTIONS=true + GITHUB_RUN_ID are set (or KAPTIONAI_LOCAL_DEV=1 for dev).
npm run predeploy aborts unless those same CI env vars are present.
main is branch-protected: requires a reviewed PR + green test, deploy, and verify checks.
CODEOWNERS routes every PR through @kshmir.
To ship a change: open a PR → review + CI green → merge to main → Actions builds, signs (Sigstore), deploys, and appends to the transparency chain. npx wrangler deploy from a laptop will fail at step 1 because there is no wrangler.jsonc to deploy.
# Full chain history (paginated)
GET /transparency?limit=50&offset=0
# Latest deployment
GET /transparency/latest
# Verify chain integrity
GET /transparency/verify
MCP (OAuth-protected)
# SSE transport (for Claude Code, Cursor)
GET /sse
# Streamable HTTP transport
POST /mcp
Development
# Install dependencies
npm install
# Run tests
npm test
# Dev server (Next.js only — no Worker routing)
npm run dev
# Build the full worker (OpenNext + custom wrapper)
npm run build:worker
Shared JWT signing secret (same as rest-api, schedule, metadata workers)
PHONE_REF_SECRET
HMAC secret used to derive opaque durable account references from phone numbers
EPHEMERAL_STATE_SECRET
Encryption secret for short-lived login hints, verify tickets, and encrypted session phone payloads
OPENAI_APPS_CHALLENGE_TOKEN
Exact domain-verification token issued by the OpenAI plugin portal
OPENAI_REVIEW_PASSWORD_SHA256
Lowercase SHA-256 hex digest of the high-entropy reviewer password
OPENAI_REVIEW_PHONE
Phone number used as the dedicated review username and to derive the synthetic account's opaque reference
The three OPENAI_* values are also configured as GitHub Actions repository
secrets. Add all three together, then run the manual Test, Build & Deploy
workflow. CI writes them to an ephemeral mode-0600 file and passes that file
to wrangler deploy --secrets-file, so the review configuration ships in the
same signed, attested Worker version as the code. The workflow fails closed if
only part of the three-value set is present and deletes the temporary file
immediately after deployment. Existing Worker secrets not listed in that file
are preserved.
Related Projects
Kaption Extension — Chrome/Edge/Firefox browser extension (the other side of the relay)
create_attachment_upload({name,mime,size,target_session?}) is forwarded to the selected
Rust core, which checks the owner-only MCP_LOCAL_SEND flag and uses its Kaption JWT to
create a same-user upload slot on the schedule Worker. PUT raw bytes to uploadUrl
within 15 minutes, then send attachment:{ref:attachmentRef} within one hour. The core
consumes the ref once and stores bytes locally for immediate or future scheduled sends.
Maximum 8 MiB; existing consent/ask-first limits apply. The relay never reads local files
or fetches third-party URLs, and rejects path and url attachment fields.