Convertway WhatsApp MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PATH | No | MCP endpoint path | /mcp |
| MCP_PORT | No | HTTP server port | 3000 |
| SMTP_HOST | No | SMTP server for email fallback | |
| WEBHOOK_PATH | No | Webhook callback path | /webhooks/convertway |
| MCP_TRANSPORT | No | Transport mode: stdio or http | stdio |
| CONVERTWAY_LICENSE_KEY | Yes | Convertway API license key |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_whatsappB | Send a WhatsApp message via Convertway — supports text, templates, and media messages |
| get_whatsapp_templatesC | List available WhatsApp message templates grouped by module |
| send_smsB | Send an SMS message via Convertway |
| send_emailB | Send an email via Convertway — supports plain text, HTML, CC/BCC, and templates |
| get_delivery_statusB | Check the delivery status of a previously sent message |
| log_conversationB | Log a conversation entry to the conversation history store |
| get_conversation_historyB | Retrieve conversation history for a customer across all channels |
| receive_inboundA | Retrieve inbound messages received via webhook (WhatsApp, SMS, or Email) |
| list_template_modulesA | List all available template modules (e.g. shipment, payment, support, alerts) |
| list_templates_by_moduleA | List all templates for a specific module |
| list_all_templatesA | List all available message templates across all modules and channels |
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 11 tools
Tools generally have distinct purposes, but there is overlap among template listing tools (list_template_modules, get_whatsapp_templates, list_templates_by_module, list_all_templates) which could confuse an agent.
Naming conventions are inconsistent: mix of 'list_', 'get_', 'send_', 'log_', 'receive_' verbs, and some tool names like 'list_template_modules' are not verb_noun consistently.
11 tools is well within the recommended 3-15 range; each tool contributes to the server's messaging and template management scope.
Covers sending, receiving, status checking, conversation history, and template listing across three channels. Minor gaps like template creation or contact management are not critical for the core communication use case.