MCP.Market

WhatsApp Messaging API MCP server

by jevil25·io.github.jevil25/whatsapp-messaging-api-mcp·v1.0.3
No reviews yet

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

B78/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
New

0 stars33 downloads/wk

Reviews

Write one

Nobody has reviewed WhatsApp Messaging API yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

WhatsApp Messaging API tools (9, 4 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • check_contact_exists

    Check whether a phone number is registered on WhatsApp before sending to it.

  • create_sessionwrite action

    Create a new WhatsApp session. Returns a session name and STARTING status — pair it with get_qr_code next.

  • get_qr_code

    Get the QR code to authenticate a session by scanning with WhatsApp (Settings > Linked Devices).

  • get_session_status

    Get the current status of a session (STARTING, SCAN_QR_CODE, WORKING, FAILED, STOPPED).

  • list_sessions

    List all WhatsApp sessions belonging to this API key.

  • request_pairing_code

    Request an 8-digit pairing code as an alternative to scanning a QR code.

  • send_filewrite action

    Send a file (PDF, document, etc.) to a contact, group, or channel via a public URL.

  • send_imagewrite action

    Send an image to a contact, group, or channel via a public URL.

  • send_text_messagewrite action

    Send a WhatsApp text message to a contact, group, or channel.

Public scan report

scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it

no findings
  • Code scan2 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 41 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How WhatsApp Messaging API compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 48,243 servers
Tools
9
the typical server has 7
Tools that change things
44%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
33
more than 21% of 12,306 servers with a package

What its tools let an agent do: 5 read · 1 create · 3 send or post

Install WhatsApp Messaging API in Claude Code, Cursor or VS Code

Runs npx -y whatsapp-messaging-api-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add whatsapp-messaging-api-mcp -- npx -y whatsapp-messaging-api-mcp
Add to Cursor

What the publisher says

From the WhatsApp Messaging API repository's README, as published. We do not edit it. Read it on GitHub

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: claudedesktopconfig.json):
{
     "mcpServers": {
       "whatsapp": {
         "command": "npx",
         "args": ["-y", "whatsapp-messaging-api-mcp"],
         "env": {
           "WHATSAPP_API_KEY": "your-rapidapi-key"
         }
       }
     }
   }
  1. 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

Typical flow

  1. createsession → getqr_code → scan with WhatsApp (Settings → Linked Devices)
  2. getsessionstatus until it reports WORKING
  3. checkcontactexists, then sendtextmessage / sendimage / sendfile

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

Configuration

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

Local development

git clone https://github.com/jevil25/whatsapp-messaging-api-mcp.git
cd whatsapp-messaging-api-mcp
npm install
npm run dev      # runs src/index.ts directly via tsx, no build step
npm 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

  • npm package
  • MCP registry entry — io.github.jevil25/whatsapp-messaging-api-mcp
  • WhatsApp Messaging API docs

License

MIT

Nothing above is checked by us. What we check is on the safety report.

WhatsApp Messaging API: common questions

Is WhatsApp Messaging API MCP server safe?
Mostly: it is graded B (78/100). Read the WhatsApp Messaging API safety report
How do I install WhatsApp Messaging API?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does WhatsApp Messaging API need an API key?
Yes. The registry entry asks for WHATSAPP_API_KEY.
Is WhatsApp Messaging API maintained?
The last commit was 61 days ago (2026-09-05). The latest release is v1.0.3.
How does WhatsApp Messaging API compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,243 servers); tools 9 (the typical server has 7); tools that change things 44% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.