MCP.Market

Whatsapp Cloud MCP server

by codespar·io.github.codespar/mcp-whatsapp-cloud·v0.2.2·271 stars
No reviews yet

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

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

full report

Adoption
Growing

271 stars

Reviews

Write one

Nobody has reviewed Whatsapp Cloud yet.

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

Whatsapp Cloud tools (22, 16 write)

write = sends, deletes, buys or posts

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

  • create_templatewrite action

    Submit a new template for Meta review. Templates become usable only after approval (usually minutes to hours).

  • delete_mediawrite action

    Delete an uploaded media asset by id.

  • delete_templatewrite action

    Delete a message template from the WABA by name. Optionally scope by hsm_id when two templates share a name across languages.

  • get_business_profile

    Read the WhatsApp business profile (about, description, email, websites, vertical, address) for the configured phone number.

  • list_phone_numbers

    List all phone numbers registered under the WhatsApp Business Account, including display name, quality rating, and verification status.

  • list_templates

    List message templates on the WhatsApp Business Account. Supports optional paging and name filter.

  • mark_message_as_read

    Mark an incoming message as read so the sender sees the blue double-check. Uses the wamid from the inbound webhook.

  • request_verification_code

    Request Meta to send a verification code to the configured phone number via SMS or voice. Use before verify_code.

  • retrieve_media_url

    Resolve a media_id to a short-lived downloadable URL. The URL itself still requires the Bearer token to fetch.

  • send_contacts_messagewrite action

    Send one or more contact cards (vCard-like). Each contact includes name and at least one of phones, emails, addresses, urls, or org.

  • send_interactive_cta_urlwrite action

    Send an interactive message with a single CTA URL button. Opens the URL when the recipient taps it. Available without template approval inside the 24h window.

  • send_interactive_flowwrite action

    Send a WhatsApp Flow message. Flows are Meta's structured UI experiences (forms, appointment booking, etc.) rendered inside WhatsApp.

  • send_interactive_messagewrite action

    Send an interactive message (reply buttons or list). Supply a fully-formed `interactive` object per Cloud API spec.

  • send_location_messagewrite action

    Send a location pin with latitude/longitude and optional name/address.

  • send_media_messagewrite action

    Send an image, video, document, or audio. Supply either `link` (public URL) or `id` (media_id from upload_media).

  • send_reaction_messagewrite action

    Send an emoji reaction on a previously received/sent message. Pass empty string for `emoji` to clear a reaction.

  • send_template_messagewrite action

    Send an approved message template. Required for business-initiated conversations. Templates must be pre-approved by Meta via create_template.

  • send_text_messagewrite action

    Send a plain text message. For business-initiated conversations outside the 24h customer-service window, use send_template_message instead.

  • send_typing_indicatorwrite action

    Show a typing indicator on a received message. Also marks the message as read. Indicator auto-clears after ~25s or when you reply.

  • update_business_profilewrite action

    Update the business profile on the configured phone number. Supply only the fields you want to change.

  • upload_mediawrite action

    Upload a media file and get back a media_id reusable in send_media_message. Multipart POST to /{phone_number_id}/media.

  • verify_codewrite action

    Submit the verification code received via SMS/voice after request_verification_code. Completes registration.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan5 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 29 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Whatsapp Cloud compares

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

Safety score
82/100
higher than 63% of 48,255 servers
Tools
22
the typical server has 7
Tools that change things
73%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
271
more than 95% of 28,688 servers

What its tools let an agent do: 5 read · 2 create · 3 change · 2 delete · 10 send or post

Install Whatsapp Cloud in Claude Code, Cursor or VS Code

Runs npx -y @codespar/mcp-whatsapp-cloud on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-whatsapp-cloud -- npx -y @codespar/mcp-whatsapp-cloud
Add to Cursor

What the publisher says

From the Whatsapp Cloud repository's README, as published. We do not edit it. Read it on GitHub

MCP Dev LATAM 🌎 Every commerce API your AI agent needs to run a business in Latin America. Brazil 🇧🇷 · Mexico 🇲🇽 · Argentina 🇦🇷 · Colombia 🇨🇴 · Chile 🇨🇱 · Peru 🇵🇪 · plus 4 agentic payment protocols. MCP servers for LATAM commerce · live in the official MCP Registry · MIT License Machine-readable catalog: codespar.dev/api/servers Catalog · Quick Start · Agentic Protocols · All Servers · Contribute

The Problem

AI agents can write code, analyze data, and chat. But they can't operate a business — collect payments, issue invoices, ship products, or notify customers. Especially not in Latin America, where every service has its own API, auth pattern, and quirks (mTLS for BACEN Pix v2, JWT-RSA for STP-SPEI, AFIP web services, contract-gated developer portals, and on).

Meanwhile, four agentic payment protocols are shipping in parallel — checkout protocols (Stripe ACP, Google UCP), authorization layers (AP2), and micropayment rails (x402) — and none of them compose cleanly with each other or with the regional rails businesses actually run on.

MCP Dev LATAM bridges both gaps. Traditional LATAM services + the new agentic payment protocols, all accessible through a single MCP interface.

The Solution

Each MCP server in this repo wraps a real provider — payments, fiscal, logistics, messaging, banking, ERP, identity, fraud, crypto, and the agentic protocols — so your agent can operate a complete business workflow.

🛒 Customer places order
  → 💳 Agent charges via Pix (Asaas / Mercado Pago / Zoop)
  → 📄 Agent issues NFe (Nuvem Fiscal / Focus NFe / NFe.io)
  → 📦 Agent generates shipping label (Melhor Envio / Skydropx)
  → 📱 Agent sends tracking via WhatsApp (Z-API / WhatsApp Cloud)
  → 📊 Agent records in ERP (Omie / Bling / Tiny)
  → 🏦 Agent reconciles balance (Stark Bank / Itaú / BTG)

Six systems. Zero human intervention. One agent.

Agentic Payment Protocols

Four servers for the emerging agentic payment stack:

Shortened. The full README is on GitHub.

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

Whatsapp Cloud: common questions

Is Whatsapp Cloud MCP server safe?
Mostly: it is graded B (82/100). Read the Whatsapp Cloud safety report
How do I install Whatsapp Cloud?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Whatsapp Cloud need an API key?
Yes. The registry entry asks for WHATSAPP_ACCESS_TOKEN.
Is Whatsapp Cloud maintained?
The last commit was 67 days ago (2026-08-29). The latest release is v0.2.2.
How does Whatsapp Cloud compare with other MCP servers?
safety score 82/100 (higher than 63% of 48,255 servers); tools 22 (the typical server has 7); tools that change things 73% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from codespar →