About this integration
WhatsApp for your agent: chats, messages, media, contacts and groups behind MCP tools.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- user-authorization
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.22.0
- Package
- wazap-mcp
- Last compatibility test
- Not independently tested
Connect your agent
wazap-mcpPublisher README and package manifest were reviewed offline. The package and WhatsApp connection were not executed or independently security-audited. The publisher calls the Baileys connection unofficial and warns that automation can result in account bans; write access is sensitive and should remain explicitly controlled.
Capabilities: read and search WhatsApp chats, inspect contacts, groups, messages, and media, draft and confirm outbound messages, wait for messages and deliver webhook events
Connected profiles
Additional details
io.github.razvangirgiz/wazap
Source ↗ · Checked 2026-09-170.22.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17wazap-mcp
Source ↗ · Checked 2026-09-190.23.1
Source ↗ · Checked 2026-09-19A client-started server lives for the client's lifetime; the publisher also documents an optional launchd or systemd user service that starts an HTTP server, survives reboot and logout, and holds the WhatsApp session.
Source ↗ · Checked 2026-09-19The reviewed local stdio mode requires one-time WhatsApp linked-device authorization by QR or pairing code. This device-link mechanism is outside the native authentication taxonomy; separate hosted HTTP OAuth and static-token modes are documented but are not the selected stdio connection.
Source ↗ · Checked 2026-09-19For the existing stdio identity, any MCP client can run npx -y wazap-mcp; account linking is a separate one-time step.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19