Wawp MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WAWP_INSTANCE_ID | No | Your Wawp instance ID. | |
| WAWP_TEST_NUMBER | No | Recipient number for testing. | |
| WAWP_ACCESS_TOKEN | No | Your Wawp access token. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| set_configC | Update your Wawp API credentials for the current session. |
| get_sdk_infoA | Get detailed information and installation guides for official Wawp SDKs (Node.js, PHP, Python, Laravel). USE THIS to help the user integrate WhatsApp into their projects. |
| get_session_healthA | Check if the WhatsApp session is connected. |
| send_local_fileC | Upload and send a local file to WhatsApp using raw API (Better to suggest SDK version to the user). |
| list_endpointsB | List all available Wawp API endpoints. |
| generate_starter_codeA | Generate professional production-ready code using official Wawp SDKs. This is the preferred way to integrate Wawp. |
| execute_requestC | Execute a raw request to the Wawp API. Useful for quick tests. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.