WhatsApp MCP Assistant (Client-Server)

Created By
Nirsisra year ago
WhatsApp MCP Assistant (Client-Server)
Overview

What is WhatsApp MCP Assistant?

WhatsApp MCP Assistant is a client-server application that allows users to send and schedule WhatsApp messages using natural language processing. The server interprets user intent with Mistral's LLM and utilizes Twilio's API for messaging.

How to use WhatsApp MCP Assistant?

To use the assistant, install the required dependencies, configure your API keys in config.py, run the server and client scripts, and then interact with the client by typing commands like "Send a message to Nir".

Key features of WhatsApp MCP Assistant?

  • Natural language processing for message scheduling and sending.
  • Client-server architecture for efficient message handling.
  • Integration with Twilio for WhatsApp messaging.

Use cases of WhatsApp MCP Assistant?

  1. Sending automated reminders via WhatsApp.
  2. Scheduling messages for future delivery.
  3. Interacting with users through natural language commands.

FAQ from WhatsApp MCP Assistant?

  • Can I send messages outside the 24-hour window?

No, freeform messages can only be sent within a 24-hour window after the last user message. Use pre-approved Message Templates for messages sent after this period.

  • Is there a way to test the application locally?

Yes, ensure you have sent a message to the Twilio number from your WhatsApp to reset the 24-hour window for testing.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Nirsisr
Star
1
Language
Python
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)

21 hours ago