# Compatibility Source: My WhatsApp is available as source code. Docker and managed remote access are in preview. There is no downloadable desktop app or published container image yet. ## Installation | Option | Current support | | --- | --- | | [Local app](https://devshiftteam.github.io/my-whatsapp-mcp/install/desktop.html) | Build from source on macOS ARM64. No signed installer or clean-machine installation test yet. | | [Docker Compose](https://devshiftteam.github.io/my-whatsapp-mcp/install/docker-compose.html) or [Docker](https://devshiftteam.github.io/my-whatsapp-mcp/install/docker.html) | Build the image from source. Public CI for commit `401c4ba` passed synthetic native Linux ARM64 and AMD64 container checks ([workflow run](https://github.com/DevShiftTeam/my-whatsapp-mcp/actions/runs/38373960272)). No published image; real-account, live-provider, and end-user client tests are pending. | | Native Windows | Not supported. | | Other native platforms | No packaged installation or confirmed desktop support. | | Documentation website | Hosted on GitHub Pages. The archive runs on your own machine. | ## Search, history, and media | Feature | What to expect | | --- | --- | | Keyword search | Hebrew and English search over messages received and retained by your archive. No model required. | | WhatsApp history | Limited to what WhatsApp sends to a linked device. Older messages, edits, deletions, and media may be missing. | | Attachments | Search filenames, types, captions, and nearby messages. Document contents are not indexed. | | Voice transcripts | Optional local faster-whisper service. Accuracy and speed depend on the recording, language, model, and hardware. | | Semantic search, OCR, and image descriptions | Experimental. A supported native bundle and default model profile are not available yet. | | Memory use | No confirmed 8 GiB requirement or published archive-scale benchmark. Native model memory and output checks are still incomplete. | | [Backup and restore](https://devshiftteam.github.io/my-whatsapp-mcp/maintenance/backups.html) | Manual backup of the complete stopped archive. Restore testing for the current Docker setup and real WhatsApp accounts is still pending. | ## Remote access and AI clients | Connection | Current limitation | | --- | --- | | [Tailscale Serve](https://devshiftteam.github.io/my-whatsapp-mcp/remote/tailscale-serve.html), [Funnel](https://devshiftteam.github.io/my-whatsapp-mcp/remote/tailscale-funnel.html), [ngrok](https://devshiftteam.github.io/my-whatsapp-mcp/remote/ngrok.html) | Setup is included, but a complete connection through a live provider and AI client has not been confirmed. | | [Cloudflare Tunnel](https://devshiftteam.github.io/my-whatsapp-mcp/remote/cloudflare.html) | You must configure the hostname route in Cloudflare. Starting the helper does not confirm that the public route works. | | [Phone access](https://devshiftteam.github.io/my-whatsapp-mcp/remote/phone-access.html) | Password-protected browser access is included. Testing on a physical phone through a live provider is still pending. | | [Codex](https://devshiftteam.github.io/my-whatsapp-mcp/clients/codex.html) and [Claude Code](https://devshiftteam.github.io/my-whatsapp-mcp/clients/claude-code.html) | Configuration examples are provided. Successful tool calls in the actual client applications have not yet been confirmed. | | [Claude remote connectors](https://devshiftteam.github.io/my-whatsapp-mcp/clients/claude-connectors.html) | Requires an account that supports custom request headers. The managed setup does not issue Claude connector credentials. | | [Composio](https://devshiftteam.github.io/my-whatsapp-mcp/clients/composio.html) | Uses the experimental Custom MCP API. Registration and authenticated tool calls still need testing in an actual Composio project. | | OAuth | Not supplied by the remote setup. Use a supported bearer-token connection. | The setup instructions have been reviewed. The synthetic native Docker checks cover the source build, the acceptance flows, and normal serve behavior: offline startup without a helper process, remote access off by default, and same-volume recreation. They do not use real WhatsApp accounts, live providers, end-user AI clients, or physical phones. Real-account import and restore, live-provider connections, and actual AI-client calls remain untested for these setup options. Tests using sample data cannot establish WhatsApp delivery, complete history, or recognition quality. The Docker timings and sizes have no matched performance baseline, so they are not performance claims. After connecting, [check access](https://devshiftteam.github.io/my-whatsapp-mcp/clients/remote-access.html#check-your-connection) with a harmless query and confirm that excluded chats stay hidden. Keep new connections read-only until you need [sending](https://devshiftteam.github.io/my-whatsapp-mcp/clients/outbound-messaging.html).