uni-msg WhatsApp

com.uni-msgPublished by uni-msg.comOfficial publisherv0.3.1Updated Oct 24, 2026

Drive WhatsApp from any MCP client: pair devices, send text and media, manage contacts and groups.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Lets an MCP client drive WhatsApp: pair devices, send text and media messages, and manage contacts and groups.

What you can do
  • Pair and manage WhatsApp devices linked to the account
  • Send text messages and media through WhatsApp
  • Manage contacts
  • Manage groups
When to use it
Useful when an assistant should send WhatsApp messages or keep contacts and groups in order from within an MCP client, rather than only drafting text for a person to send.
Requirements
A uni-msg account and an API key from the uni-msg dashboard, supplied as UNIMSG_API_KEY or as a bearer token in the Authorization header. Available as a remote endpoint at uni-msg.com or as the local npm package uni-msg-mcp-server over stdio; network access is needed either way.
Before you install
The API key is a secret that grants access to the WhatsApp account; keep it out of logs and shared configs. Sending messages and changing contacts or groups act on real people and real chats, so review before letting an assistant do it unattended. Messages and account data pass through the uni-msg service.

Installation

In SourceWeft

  1. Open uni-msg WhatsApp in the dashboard and add it to a workspace.
  2. Connect Authorization token 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.uni-msg%2Fwhatsapp/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.

{
  "mcpServers": {
    "uni-msg-whatsapp": {
      "type": "http",
      "url": "https://uni-msg.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.3.1LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.