Kapso Whatsapp

io.github.magurelabsPublished by GitHub account magurelabsv2.0.0Updated Nov 14, 2026

Send WhatsApp text, media and template messages, and read conversations.

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant send WhatsApp text, media and template messages and read conversations, run locally as a Docker-based MCP service.

What you can do
  • Send WhatsApp text messages
  • Send media and template messages
  • Read WhatsApp conversations
  • No tool list is published, so exact operations beyond these are unconfirmed.
When to use it
When you want an assistant to draft and send WhatsApp messages or review existing conversations from your own machine, for example for customer replies or notifications.
Requirements
Runs as a local process from a Docker image (streamable-http transport). Requires the MCP_MODE environment variable (defaults to platform in the image; hosted and local modes need extra settings) and the MCP_SERVICE_TOKEN secret, which callers send as the X-Service-Token header in platform mode. Desktop only.
Before you install
Sending messages writes to real WhatsApp conversations and is visible to recipients, so review outbound content before it goes out. The MCP_SERVICE_TOKEN shared secret must be kept private. No authentication is declared in the manifest, and the tool list is not published, so verify behavior before use.

Installation

In SourceWeft

  1. Open Kapso Whatsapp 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

This repository has no README.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

1
  1. v2.0.0LatestNov 14, 2026

Score

35% 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

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

  • License10 pts