Wassenger Whatsapp Connector

Created By
Wassengera year ago
🚀 Supercharge your WhatsApp automation driven by AI! Send messages, summarize conversations, and manage chats using natural language from your favorite AI assistant like ChatGPT, Claude, or custom AI agents. ✨ Easily integrate Wassenger WhatsApp API with any MCP-powered AI client including ChatGPT, VS Code Copilot, Claude Desktop, Cursor, Windsurf and many more! 💬 Transform how you communicate - automate responses, analyze chat patterns, and manage customer conversations at scale, manage WhatsApp chats and groups, everything through simple conversational text or voice commands with your AI assistant.
Overview

MCP Wassenger WhatsApp API Connector NPM Version 🚀 Supercharge your WhatsApp automation driven by AI! Send messages, summarize conversations, and manage chats using natural language from your favorite AI assistant like ChatGPT, Claude, or custom AI agents.

✨ Easily integrate Wassenger WhatsApp API with any MCP-powered AI client including ChatGPT, VS Code Copilot, Claude Desktop, Cursor, Windsurf and many more!

💬 Transform how you communicate - automate responses, analyze chat patterns, and manage customer conversations at scale, manage WhatsApp chats and groups, everything through simple conversational text or voice commands with your AI assistant.

👉 Read the blog post introducing Wassenger MCP server

⚠️ Note: You only need to use this package if your MCP client does not support HTTP streaming (previously known as SSE connection). To use a remote HTTP connection read these instructions.

Server Config

{
  "mcpServers": {
    "wassenger": {
      "command": "npx",
      "args": [
        "mcp-wassenger",
        "$API_KEY"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Wassenger
Star
-
Language
-
License
-
Category

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)

6 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago