WhatsApp MCP Server with Wati API

Created By
wati-ioa year ago
Overview

What is WhatsApp MCP Server with Wati API?

The WhatsApp MCP Server is a Model Context Protocol (MCP) server that allows users to interact with their WhatsApp messages and contacts through the Wati API. It enables functionalities such as sending messages, searching contacts, and handling media files.

How to use WhatsApp MCP Server?

To use the WhatsApp MCP Server, you need to install it via Smithery, configure it with your Wati API credentials, and connect it to your Claude or Cursor application. Once set up, you can interact with WhatsApp through these platforms.

Key features of WhatsApp MCP Server?

  • Search and read WhatsApp messages.
  • Send messages and media files (images, videos, documents, audio).
  • Integration with Claude for enhanced AI capabilities.
  • Support for interactive buttons in messages.

Use cases of WhatsApp MCP Server?

  1. Automating customer support through WhatsApp.
  2. Sending promotional messages with interactive options.
  3. Managing personal WhatsApp communications through AI.

FAQ from WhatsApp MCP Server?

  • What is required to run the server?

    You need Python 3.6+, Wati API access, and either Claude or Cursor applications.

  • Can I send media files?

    Yes, you can send images, videos, documents, and audio files.

  • How do I troubleshoot connection issues?

    Ensure your Wati API credentials are correct and check for permission issues with the UV executable.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
wati-io
Star
0
Language
Python
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