WhatsApp Messaging API

io.github.jevil25Published by GitHub account jevil25v1.0.3Updated Oct 24, 2026

Send WhatsApp messages from Claude. No Meta Business approval or WhatsApp Business account.

VerifiedSTDIODesktop onlyProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

A local MCP server that lets an assistant manage WhatsApp sessions and send text, image and file messages through a third-party API, without a Meta Business or

What you can do
List, create and check WhatsApp sessions, and get a QR code or pairing code to authenticate one with a phone number's linked devices. Check whether a phone number is on WhatsApp before messaging. Send text messages, images by URL and files such as PDFs by URL. Sessions stay authenticated between runs, so linking is one-time per number.
When to use it
Useful when you want an assistant to send WhatsApp messages or files from a desktop MCP client without going through Meta Business approval or a WhatsApp Business account.
Requirements
Runs locally over stdio, typically launched with npx, so Node.js is needed. Requires a RapidAPI key supplied in the WHATSAPP_API_KEY environment variable; the server exits on startup if it is missing. Network access to the API host, and a phone with WhatsApp to scan the QR code or enter the pairing code.
Before you install
The WHATSAPP_API_KEY credential is required and sent to the third-party API host. Sending messages, images and files acts on real recipients and cannot be undone. Linking a session gives the service access to that WhatsApp account's messaging, so review the provider's terms and data handling before connecting a personal number.

Installation

In SourceWeft

  1. Open WhatsApp Messaging API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

WhatsApp Messaging API — MCP Server

Send WhatsApp messages from Claude, Cursor, or any MCP client. Create a session, scan a QR code, and send text, images and files — no Meta Business approval and no WhatsApp Business account required.

Wraps the WhatsApp Messaging API.

Quick start

  1. Get a free API key from RapidAPI — no credit card.

  2. Add this to your MCP client config (Claude Desktop: claude_desktop_config.json):

    json
    {  "mcpServers": {    "whatsapp": {      "command": "npx",      "args": ["-y", "whatsapp-messaging-api-mcp"],      "env": {        "WHATSAPP_API_KEY": "your-rapidapi-key"      }    }  }}

  3. Restart the client. Ask it to create a WhatsApp session and show you the QR code.

Nothing to install or build — npx fetches the package on first run.

Tools

ToolDescription
list_sessionsList all sessions on this API key
create_sessionCreate a new session
get_session_statusCheck a session's current status
get_qr_codeGet the QR code to authenticate a session
request_pairing_codeGet an 8-digit pairing code instead of a QR
check_contact_existsCheck if a phone number is on WhatsApp before sending
send_text_messageSend a text message
send_imageSend an image via URL
send_fileSend a file (PDF, document) via URL

Typical flow

  1. create_session → get_qr_code → scan with WhatsApp (Settings → Linked Devices)
  2. get_session_status until it reports WORKING
  3. check_contact_exists, then send_text_message / send_image / send_file

Sessions stay authenticated between runs, so steps 1-2 are one-time per number.

Configuration

VariableRequiredDescription
WHATSAPP_API_KEYyesYour RapidAPI key. The server exits on startup if it is missing.

The key is read from the environment and sent only to the API host. It is never logged.

Local development

bash
git clone https://github.com/jevil25/whatsapp-messaging-api-mcp.gitcd whatsapp-messaging-api-mcpnpm installnpm run dev      # runs src/index.ts directly via tsx, no build stepnpm run build    # compile to dist/npm test         # boots the built server and drives a real MCP handshake

npm test needs no credentials — it passes a dummy key, which gets far enough to list tools because nothing in the handshake makes an API call.

To point an MCP client at your local build, use "command": "node" with "args": ["/absolute/path/to/dist/index.js"].

See DEVELOPING.md for the release process.

Links

License

MIT

Source: README.md at commit 683d8b5

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts