# wapiworld [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://app.wapiworld.com/developers#mcp  
**npm Downloads (last month):** 219  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/wapiworld

## Description
Inspect Wapiworld sender and webhook health, and send one explicitly confirmed WhatsApp text.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "wapiworld": {
    "command": "npx",
    "args": ["-y","wapiworld"]
  }
}
```

## Documentation

## What the wapiworld MCP server does

The wapiworld MCP server exposes a focused set of operations for Wapiworld messaging infrastructure. It can inspect the health of a sender and the health of webhooks, giving an agent a way to check whether those parts of the system are functioning. It can also send a WhatsApp text, but the action is explicitly confirmed rather than treated as an unrestricted send operation.

This makes the server relevant to workflows that need a health check before messaging or that require a deliberate confirmation step before a WhatsApp message is sent. The available description does not identify additional messaging channels, contact-management functions, message-history queries, or administrative operations.

## Tools and capabilities

The documented capabilities are:

- Inspect Wapiworld sender health.
- Inspect Wapiworld webhook health.
- Send one WhatsApp text after explicit confirmation.

The material does not provide formal tool names, argument schemas, response formats, or details about how confirmation is represented. Developers should consult the Wapiworld developer page for those implementation details before building an automation around the server.

## Setup and configuration

The supplied material does not include installation commands, transport details, configuration examples, authentication requirements, environment variables, or client-specific setup instructions. The source is Wapiworld’s developer page at `https://app.wapiworld.com/developers#mcp`.

Because the setup contract is not available here, do not assume a package name, command, credential variable, or connection mode. Use the developer documentation to determine how an MCP client should launch or connect to the wapiworld MCP server and how Wapiworld access is authorized.

## Limitations and notes

The wapiworld MCP server is described as a narrow interface rather than a general WhatsApp automation layer. Its documented sending capability covers one explicitly confirmed WhatsApp text. The available information does not establish support for bulk delivery, scheduled messages, media, templates, replies, conversation retrieval, or recipient lookup.

Health inspection is specified for the Wapiworld sender and webhooks. No other components or external services are identified. Client compatibility is also not stated in the supplied material, so verify support in the target MCP client and follow Wapiworld’s current developer instructions.

The explicit-confirmation requirement matters for unattended workflows: an agent should not be assumed to have permission to send merely because it can call the server. Confirm the action according to the server’s documented protocol before relying on it in production.

_Full upstream README: https://allmcps.com/mcp/wapiworld/readme_