loginwa
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOGINWA_API_KEY | No | LoginWA API key. Create one in the dashboard under Apps. | |
| LOGINWA_BASE_URL | No | Optional API base URL. Defaults to https://api.loginwa.com/api/v1. |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| device_statusA | List LoginWA WhatsApp devices (or one device by id) and report online/offline honestly. If a device is not online, instruct the user to open https://loginwa.com/welcome to pair. Does not start in-chat QR/pairing races. |
| otp_startA | Start a LoginWA OTP session: send a one-time code to a WhatsApp phone number via a connected device. |
| otp_verifyA | Verify an OTP code against a LoginWA session_id returned by otp_start. |
| send_messageC | Send a WhatsApp text or media message from a connected LoginWA device. Media types require a public https media_url. |
| list_campaignsB | List LoginWA broadcast campaigns (paginated). |
| get_campaignA | Get details for a LoginWA broadcast campaign by id. |
| create_campaignA | Create a LoginWA broadcast campaign with an inline contact list. Starts as draft (or queued if schedule_at is set). Call send_campaign to begin. |
| send_campaignA | Queue a draft/queued/paused LoginWA campaign for sending. Requires at least one online device; otherwise direct the user to https://loginwa.com/welcome |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| loginwa-overview | What this unofficial MCP server can do and where to pair devices |
TDQS
Scored across 8 tools
Every tool has a clearly distinct purpose: device status, OTP start/verify, message sending, and campaign management (list, get, create, send). No two tools overlap in function, so an agent can confidently select the right one based on the action needed.
Most tools follow the verb_noun pattern (get_campaign, send_message, list_campaigns, etc.), but device_status breaks the pattern by using a noun_noun form instead of something like get_device_status. This is a minor deviation from an otherwise consistent style.
With 8 tools, the set is well-scoped for a WhatsApp service covering messaging, OTP, and campaigns. Each tool earns its place without bloat or excess, staying comfortably within the ideal 3-15 range.
The core workflows are covered: send messages, handle OTP, and manage campaigns. However, campaign management lacks update/delete operations, and device management is limited to status only. These are minor gaps that agents can work around but might require external fallback.