Skip to main content
Glama
Convertway WhatsApp MCP Server

Convertway WhatsApp MCP Server

by QalaLabs

Convertway WhatsApp MCP Server

MCP Server for WhatsApp Business API via Convertway by Unicommerce — omnichannel communication layer for WhatsApp, SMS, and Email. Built for AI coding tools (Claude Code, Cursor, etc.).

Features

  • 3 Channels — WhatsApp (text/template/media), SMS, Email (CC/BCC)

  • 11 MCP Tools — send, receive, list templates, check delivery, log conversations

  • 15 Message Templates — across 7 modules: shipment, payment, mis, support, alerts, b2b, escalation

  • Dual Transport — stdio (local CLI) or HTTP (remote server)

  • Inbound Webhooks — receive and process incoming messages

  • Conversation Store — file-based persistence

Related MCP server: WhatsApp Cloud API MCP Server

Quick Start

npm install
cp .env.example .env
# Edit .env: set CONVERTWAY_LICENSE_KEY
npm run dev          # stdio mode (local)
npm run dev:http     # HTTP mode (remote)

Remote Server Mode

Run as a remote MCP server for Claude Code, Cursor, or any MCP client:

npm run start:http

The server exposes a unified Express app on a single port:

Endpoint

Method

Purpose

/mcp

POST / GET

MCP Streamable HTTP endpoint

/webhooks/convertway

POST

Convertway webhook callbacks

/health

GET

Health check

MCP Client Config

{
  "mcpServers": {
    "convertway": {
      "url": "http://localhost:3000/mcp"
    }
  }
}

Tools

Tool

Description

send_whatsapp

Send WhatsApp text, template, or media messages

get_whatsapp_templates

List approved WhatsApp templates

send_sms

Send SMS with sender ID

send_email

Send email with CC/BCC

get_delivery_status

Check delivery status by message ID

receive_inbound

Pull inbound messages from webhook queue

log_conversation

Log a conversation record

get_conversation_history

Retrieve conversation history

list_template_modules

List all template modules

list_templates_by_module

List templates for a specific module

list_all_templates

List all templates across modules

Environment

Variable

Default

Description

CONVERTWAY_LICENSE_KEY

—

Convertway API license key

MCP_TRANSPORT

stdio

Transport mode: stdio or http

MCP_PORT

3000

HTTP server port

MCP_PATH

/mcp

MCP endpoint path

WEBHOOK_PATH

/webhooks/convertway

Webhook callback path

SMTP_HOST

—

SMTP server for email fallback

Architecture

src/
├── config.ts              # Env-based configuration
├── server.ts              # McpServer setup (stdio + HTTP)
├── index.ts               # Entry point
├── convertway/
│   ├── client.ts          # Convertway API client (Axios, Basic Auth)
│   └── types.ts           # TypeScript types
├── templates/
│   └── index.ts           # 15 templates with variable interpolation
├── tools/
│   ├── index.ts           # Tool registry (11 tools)
│   ├── whatsapp.ts        # WhatsApp send + template listing
│   ├── sms.ts             # SMS send
│   ├── email.ts           # Email send
│   ├── delivery.ts        # Delivery status
│   └── conversations.ts   # Conversation CRUD
├── webhooks/
│   ├── handler.ts         # Inbound message queue
│   ├── router.ts          # Express webhook routes
│   └── server.ts          # Standalone webhook server
└── storage/
    └── conversations.ts   # File-based conversation store

Docker

docker build -t convertway-mcp .
docker run -e CONVERTWAY_LICENSE_KEY=cw_your_key -e MCP_TRANSPORT=http -p 3000:3000 convertway-mcp

Available Tools

11 tools
get_conversation_historyB

Retrieve conversation history for a customer across all channels

Inputs: customerId (required), limit.

get_delivery_statusB

Check the delivery status of a previously sent message

Inputs: messageId (required), channel.

get_whatsapp_templatesC

List available WhatsApp message templates grouped by module

Inputs: module.

list_all_templatesA

List all available message templates across all modules and channels

Inputs: channel (required).

list_template_modulesA

List all available template modules (e.g. shipment, payment, support, alerts)

Inputs: no named parameters.

list_templates_by_moduleA

List all templates for a specific module

Inputs: module (required).

log_conversationB

Log a conversation entry to the conversation history store

Inputs: status (required), channel (required), content (required), direction (required), +3 more.

receive_inboundA

Retrieve inbound messages received via webhook (WhatsApp, SMS, or Email)

Inputs: limit, channel, markAsProcessed.

send_emailB

Send an email via Convertway — supports plain text, HTML, CC/BCC, and templates

Inputs: to (required), body (required), subject (required), cc, +3 more.

send_smsB

Send an SMS message via Convertway

Inputs: to (required), message (required), senderId.

send_whatsappB

Send a WhatsApp message via Convertway — supports text, templates, and media messages

Inputs: to (required), message, mediaUrl, mediaType, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 11 tools

    Disambiguation3/5

    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 Consistency2/5

    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.

    Tool Count5/5

    11 tools is well within the recommended 3-15 range; each tool contributes to the server's messaging and template management scope.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      Enables WhatsApp Business messaging through Evolution API with support for creating instances, sending messages using dynamic templates, and managing contacts and groups. Includes 10+ predefined message templates for common business scenarios like order confirmations, appointment reminders, and promotional messages.
      25
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables any MCP-compatible AI agent to send WhatsApp messages, SMS, OTP codes, and email through a single REST API.
      18
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Enables AI agents to send WhatsApp messages and templates, manage CRM data like contacts, leads, cases, and campaigns, and perform marketing and onboarding operations through the Gambot WhatsApp Business API.
      78
      198 npm
      2
      MIT