Samihalawa Whatsapp Go MCP

What samihalawa-whatsapp-go-mcp MCP server does

The samihalawa-whatsapp-go-mcp MCP server provides an MCP entry point for interacting with a WhatsApp account managed by the GoWA application. After connecting an account by scanning a QR code, an MCP-compatible agent can use the WhatsApp connection for supported messaging actions.

The documented feature set includes sending WhatsApp messages, mentioning phone numbers in message text, and publishing WhatsApp Status updates. Media handling includes image and video compression before sending. The application also supports automatic replies, automatic marking of incoming messages as read, and delivery of received-message events to configured webhooks.

How it works

Run the application in MCP mode with the mcp subcommand. The WhatsApp account is connected through a QR-code flow rather than through a separate API credential described in the supplied documentation. The application keeps account data in its configured database, which defaults to a local SQLite-style file URI.

The same application also offers REST mode, but that is separate from the MCP startup path. Command-line flags take precedence over environment variables, and environment variables take precedence over values in a .env file.

Setup and configuration

For the samihalawa-whatsapp-go-mcp MCP server, source builds require Go 1.24 or newer and FFmpeg for media processing. Supported platforms listed by the project are Linux on x86_64 or ARM64, macOS on Intel or Apple Silicon, and Windows on x86_64, with WSL recommended for Windows. Docker images and prebuilt releases are also referenced by the project.

Configuration can be supplied through command-line options, system environment variables, or a .env file. Relevant settings include:

• APP_PORT and APP_DEBUG for the listening port and debug logging.
• APP_BASIC_AUTH for multiple basic-auth credentials.
• APP_BASE_PATH for deployment below a URL subpath.
• DB_URI for the database connection.
• WHATSAPP_AUTO_REPLY and WHATSAPP_AUTO_MARK_READ for incoming-message behavior.
• WHATSAPP_WEBHOOK and WHATSAPP_WEBHOOK_SECRET for event delivery and HMAC validation.

The documented default webhook signing key is secret; change it when configuring webhook validation.

Tools and capabilities

The supplied material identifies MCP support but does not provide a complete list of individual MCP tool names or schemas. At the capability level, the server supports WhatsApp message sending, phone-number mentions, Status publishing, and media compression. It also exposes application behaviors around auto-replies, read marking, chat storage, account validation, and webhook notifications.

Basic authentication can hold multiple username-and-password pairs. The WhatsApp device name can be customized, and the HTTP-facing application port, debug mode, and deployment base path can be changed.

Limitations and notes

The README excerpt does not document exact MCP tool names, argument schemas, return formats, or client-specific setup instructions. It also does not establish that every listed REST feature is exposed as an MCP tool. Review the server's MCP definitions before depending on a particular operation or payload shape.

Media processing depends on FFmpeg. Windows is described as supported but not preferred; the project recommends WSL. Command-line flags override environment and .env configuration, so values in lower-priority sources may not take effect.