Whatsmcp

com.whatsmcpPublished by whatsmcp.comOfficial publisherv0.1.195Updated Nov 6, 2026

WhatsApp for AI agents — your own number or the official Cloud API: messages, media, templates.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Remote MCP endpoint that lets an AI assistant send and manage WhatsApp messages, media and templates via your own number or the official Cloud API.

What you can do
  • Send and receive WhatsApp messages through an assistant
  • Work with media attachments in conversations
  • Use message templates, including on the official Cloud API
  • Operate either with your own WhatsApp number or the official Cloud API
When to use it
Useful when you want an assistant to handle WhatsApp conversations directly — drafting and sending messages, sharing media, or working with approved templates — without building your own integration.
Requirements
A remote MCP endpoint at api.whatsmcp.com over streamable HTTP; OAuth authentication is required. Either your own WhatsApp number or an official WhatsApp Cloud API account is needed, depending on the mode used. No environment variables or headers are declared.
Before you install
The server can send messages and media on your behalf, so review what an assistant does before granting access. It requires OAuth authorization and access to a WhatsApp number or Cloud API account; message content and media pass through a third-party service.

Installation

In SourceWeft

  1. Open Whatsmcp in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.whatsmcp%2Fwhatsmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "whatsmcp": {
      "type": "http",
      "url": "https://api.whatsmcp.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

5
  1. v0.1.195LatestNov 6, 2026
  2. v0.1.194Oct 29, 2026
  3. v0.1.193Oct 25, 2026
  4. v0.1.192Oct 5, 2026
  5. v0.1.154Sep 27, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.