📱 WhatsApp MCP Server

Created By
Mtumish1a year ago
This server bridges WhatsApp messages with large language models, allowing for intelligent summarization, response generation, scheduling, and personal assistant tasks using the MCP specification.
Overview

What is WhatsApp MCP Server?

The WhatsApp MCP Server is a bridge that connects WhatsApp messages with large language models (LLMs), enabling intelligent summarization, response generation, scheduling, and personal assistant tasks using the Model Context Protocol (MCP).

How to use WhatsApp MCP Server?

To use the WhatsApp MCP Server, integrate it with your WhatsApp Business API or set up a local bridge. Once connected, it allows LLMs to read and respond to WhatsApp messages securely.

Key features of WhatsApp MCP Server?

  • Secure ingestion of WhatsApp chats via the WhatsApp Business API or local bridge.
  • JSON-based context delivery for LLMs.
  • Action endpoint for generating suggested replies or initiating workflows.
  • Compatibility with MCP clients and orchestration frameworks.
  • Focus on user privacy and scoped data access.

Use cases of WhatsApp MCP Server?

  1. Automating responses to customer inquiries on WhatsApp.
  2. Summarizing chat conversations for quick insights.
  3. Scheduling appointments or reminders based on WhatsApp messages.
  4. Enhancing personal assistant capabilities through WhatsApp integration.

FAQ from WhatsApp MCP Server?

  • Can I use this server with any LLM?

Yes! The server is designed to work with various LLMs, including Claude and GPT-4.

  • Is the WhatsApp MCP Server secure?

Yes! It emphasizes user privacy and provides scoped data access.

  • How can I contribute to the project?

Contributions are welcome! You can contribute code, ideas, or help with testing.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Mtumish1
Star
0
Language
TypeScript
License
MIT license
Tags

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)

a day ago