Personal WhatsApp MCP server with a Go bridge and Python MCP server for searching contacts and chats, reading messages, sending messages, sending media, and downloading WhatsApp media.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
63
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
No reviewed flag detected in metadata.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 24/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
No review metadata found; increase manual validation.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Missing required evidence: Metadata review. Risk score 31.
Source repository/provenance is listed.
Required in this preset
Review metadata is missing.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required gaps: Metadata review
Decision timeline
Blocking gaps: Check metadata review status. Risk 28.
triage
Source/provenance metadata is available.
triage
Review metadata is missing.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
Blockers: Check metadata review status
Prerequisite readiness
5 prerequisites to line up before setup.
Safety & privacy surface
5 safety and 3 privacy notes across 5 risk areas. Review closely: credentials & tokens, network access, third-party handling.
{
"mcpServers": {
"whatsapp": {
"command": "uv",
"args": [
"--directory",
"PATH_TO_REPO/whatsapp-mcp-server",
"run",
"main.py"
]
}
}
}WhatsApp MCP Server connects MCP clients to a personal WhatsApp account through a local Go bridge and Python MCP server. It can search contacts, list chats, read messages, retrieve context, send messages, send media files, send audio messages, and download media from WhatsApp messages.
The Go bridge authenticates through WhatsApp's linked-device flow and stores message history in local SQLite databases. The Python MCP server exposes the tools to Claude Desktop, Cursor, or other MCP clients.
These sources were reviewed on 2026-06-05. Prefer the live repository for current bridge setup, Python server requirements, Windows compatibility notes, media behavior, and troubleshooting.
Clone the repository and start the WhatsApp bridge:
git clone https://github.com/lharries/whatsapp-mcp.git
cd whatsapp-mcp/whatsapp-bridge
go run main.go
Scan the QR code with WhatsApp to authenticate, then configure your MCP client to run the Python server:
{
"mcpServers": {
"whatsapp": {
"command": "uv",
"args": [
"--directory",
"PATH_TO_REPO/whatsapp-mcp-server",
"run",
"main.py"
]
}
}
}
Install FFmpeg if you need automatic conversion for playable WhatsApp voice messages.
WhatsApp messages are deeply personal and often include other people's private data. Do not let an agent send messages or files without explicit review. Treat all message content, media, contacts, group names, and phone numbers as sensitive.
The project README warns that prompt injection can lead to private data exfiltration. Keep high-trust chats out of automated workflows and avoid asking the model to process untrusted messages alongside tools that can send data out.
No lharries/whatsapp-mcp entry or source URL was found in content/mcp. This
entry is separate from general browser, messaging, or filesystem MCP servers
because it targets a personal WhatsApp account through a local bridge.
Show that WhatsApp MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/whatsapp-mcp-server)WhatsApp MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Personal WhatsApp MCP server with a Go bridge and Python MCP server for searching contacts and chats, reading messages, sending messages, sending media, and downloading WhatsApp media. Open dossier | Browser automation MCP server and Chrome extension that lets AI applications control a connected tab in the user's existing browser profile. Open dossier | Chrome extension-based MCP server that exposes an existing Chrome browser profile to AI assistants for tab management, page content, screenshots, interaction, history, bookmarks, and network inspection. Open dossier | Source-install MCP server for controlling a local ComfyUI instance so Claude can generate, view, regenerate, manage, and publish image, audio, and video assets through workflow-backed tools. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | Not reviewed | Not reviewed | Not reviewed | Not reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| Submitter | oktofeesh1 | oktofeesh1 | oktofeesh1 | oktofeesh1 |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | — | |
| Category | mcp | mcp | mcp | mcp |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | Luke Harries | BrowserMCP | hangwin | Joe Norton |
| Added | 2026-06-05 | 2026-06-05 | 2026-06-05 | 2026-06-06 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓WhatsApp MCP can search and read personal messages, contacts, chats, media metadata, and message context. Tools can send messages and files to individuals or groups; require human approval before every send action. Prompt injection in messages or media metadata can attempt to exfiltrate private chat data through the agent. Use only with accounts you control and understand the risks of linking third-party automation to WhatsApp. Re-authentication may be required when WhatsApp linked-device sessions expire. | ✓BrowserMCP can navigate pages, click controls, type text, submit forms, capture screenshots, inspect accessibility snapshots, read console logs, and automate the connected tab. Because it uses the user's real browser profile, logged-in sessions and account permissions may be available to the agent. Require human approval before purchases, messages, account changes, destructive actions, or actions that violate a site's terms. Use a test profile or non-production account for end-to-end testing and repetitive automation. | ✓This server controls the user's existing Chrome browser profile and can reuse logged-in sessions. Tools can navigate pages, click elements, fill forms, inspect tabs, capture screenshots, inspect network traffic, read history, manage bookmarks, and inject scripts. Use a dedicated browser profile for agent work and avoid sensitive accounts unless the workflow explicitly requires them. Do not allow agents to submit forms, make purchases, change account settings, or perform irreversible actions without human approval. The project describes itself as early-stage and under active development; test carefully before relying on it for critical workflows. | ✓ComfyUI MCP Server can submit prompts and workflows to a local ComfyUI instance, create generated media, poll jobs, cancel jobs, and publish assets into project directories. Generated images, audio, and video can contain unsafe, infringing, biased, misleading, or policy-sensitive content depending on prompts, models, LoRAs, and workflows. Publishing tools can copy, compress, convert, overwrite, and update manifest entries for assets, so verify target filenames and directories before use. Custom workflows can expose arbitrary parameters and may run heavy GPU workloads or fail if nodes, models, or paths are missing. Keep the server bound to local trusted clients unless you have added appropriate authentication and network controls. |
| Privacy notes | ✓Personal and group messages, contacts, phone numbers, group identifiers, media metadata, downloaded media paths, attachments, and outgoing message drafts may be exposed to the MCP client and model. Message history is stored locally in SQLite databases under the bridge directory, and media can be downloaded locally on demand. Chat content may include other people's personal data, confidential business information, authentication codes, health data, financial data, or private media. | ✓Connected tab content, screenshots, form fields, console logs, and page state may be exposed to the MCP client and model. Logged-in pages can contain personal data, customer information, credentials, tokens, internal URLs, or private documents. Although the project describes local automation, prompts and tool results still flow through the chosen AI application and model provider. | ✓Open tabs, page content, screenshots, browsing history, bookmarks, cookies/session-derived page state, and network request metadata may be exposed to the MCP client and model. Screenshots and network responses can contain credentials, personal data, customer data, tokens, and private documents. Browser automation prompts may reveal personal browsing habits, internal applications, and authenticated service access. | ✓Prompts, negative prompts, generated media, workflow parameters, model names, job IDs, asset metadata, and publish paths can appear in MCP responses, logs, and model transcripts. Generated assets may be stored in ComfyUI output folders, the MCP asset registry, project publish directories, or manifests. Do not feed private images, brand assets, customer materials, or regulated media into workflows unless the local model environment is approved for that data. Review model and workflow licenses before publishing or redistributing generated assets. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Automate real browser tabs from Claude, Cursor, VS Code, Windsurf, and other MCP clients through BrowserMCP.
Let MCP clients control and inspect a local Chrome browser through the mcp-chrome extension and bridge.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.