Whatsapp

Created By
lharriesa year ago
Overview

What is WhatsApp MCP?

WhatsApp MCP is a Model Context Protocol (MCP) server that allows users to interact with their personal WhatsApp messages, search contacts, and send messages to individuals or groups through an AI interface.

How to use WhatsApp MCP?

To use WhatsApp MCP, clone the repository, run the WhatsApp bridge application, authenticate via QR code, and connect to the MCP server to start interacting with your WhatsApp account through AI tools.

Key features of WhatsApp MCP?

  • Direct connection to personal WhatsApp account via WhatsApp web multidevice API.
  • Local storage of messages in a SQLite database for efficient searching.
  • Integration with AI tools like Claude for enhanced messaging capabilities.

Use cases of WhatsApp MCP?

  1. Searching for specific contacts or messages within WhatsApp.
  2. Sending messages to contacts using AI assistance.
  3. Managing and retrieving chat history efficiently.

FAQ from WhatsApp MCP?

  • Can I use WhatsApp MCP with any WhatsApp account?

Yes! It connects directly to your personal WhatsApp account.

  • Is my data secure with WhatsApp MCP?

Yes! All messages are stored locally and only accessed when needed.

  • What do I need to run WhatsApp MCP?

You need Go, Python 3.6+, and the Anthropic Claude Desktop app or Cursor.

Server Config

{
  "mcpServers": {
    "whatsapp": {
      "command": "{{PATH}}/.local/bin/uv",
      "args": [
        "--directory",
        "{{PATH}}/whatsapp-mcp/whatsapp-mcp-server",
        "run",
        "main.py"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
lharries
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

4 hours ago
Gpt Scrambler

a day ago