Wawp MCP Server
# Wawp MCP Server 🤖
The Model Context Protocol (MCP) server for the Wawp WhatsApp API. This tool allows AI models (like Cursor, Windsurf, or Claude Desktop) to interact directly with your WhatsApp instances.
## 🚀 Quick Start
You don't need to install anything manually. You can run the server directly using `npx`.
### 🖱️ Cursor / Windsurf
Add a new MCP server with the following settings:
- **Type:** `command`
- **Command:** `npx`
- **Args:** `["-y", "@wawp/mcp-server@latest"]`
### 🤖 Claude Desktop
Add this to your `claude_desktop_config.json`:
```json
{
"mcpServers": {
"wawp": {
"command": "npx",
"args": ["-y", "@wawp/mcp-server@latest"]
}
}
}
```
## 🔑 Configuration
Once the server is connected, you can set your credentials using the `set_config` tool or by creating a `.env` file in your project root:
```env
WAWP_INSTANCE_ID=your_instance_id
WAWP_ACCESS_TOKEN=your_access_token
WAWP_TEST_NUMBER=recipient_number
```
## 🛠️ Available Tools
- `set_config`: Update credentials for the current session.
- `get_session_health`: Check WhatsApp connection status.
- `send_local_file`: Send images, PDFs, videos, or audio files from your local machine.
- `execute_request`: Make any raw request to the Wawp API.
- `install_agent_config`: Auto-install `.cursorrules` and Wawp AI Skills into your project.
- `generate_starter_code`: Get ready-to-use Node.js or Python snippets.
- `list_endpoints` / `get_endpoint_details`: Explore the API documentation.
## 📄 License
MIT
---
Built with ❤️ by [Wawp Team](https://wawp.net)
TDQS
Scored across 7 tools
Each tool has a distinct action: sending files, listing endpoints, generating code, executing raw requests, setting config, getting SDK info, and checking health. The potential overlap between send_local_file and execute_request is minor since one is specific and the other generic.
All tool names follow a consistent snake_case verb_noun pattern, e.g., send_local_file, list_endpoints, get_session_health. The verbs vary but are clear and stylistically consistent.
With 7 tools, the set is well-scoped for an integration helper server. Each tool serves a clear purpose, and the count is within the optimal range.
The server covers configuration, session health, file sending, and API introspection, but lacks dedicated tools for common WhatsApp operations like sending text messages. However, execute_request and SDK code generation can partially compensate, so there are minor gaps.