MojaWave MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MOJAWAVE_API_KEY | Yes | Your MojaWave API key. Get it from the MojaWave dashboard under Settings → API Keys. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_smsA | Send a single SMS message, optionally scheduled for future delivery. Confirm recipient, message, and sender_id with the user first — this spends real credits. Args: to: Recipient phone number in E.164 format (e.g. +255712345678). message: SMS text content (max 1600 characters). sender_id: Sender ID shown to the recipient (1-11 alphanumeric chars, e.g. MYAPP). Use list_sms_sender_ids to find approved IDs. If none exist, use 'MojaWave' as the default shared sender ID. schedule_at: Optional future delivery time in ISO-8601 UTC (e.g. 2026-06-15T09:00:00Z). Leave empty to send immediately. |
| send_bulk_smsA | Send the same SMS to up to 10,000 recipients. Processed asynchronously — returns a job_id immediately; use get_bulk_sms_job to track progress. Confirm the recipient list size, message, and sender_id with the user first — this spends real credits. Args: recipients: List of phone numbers in E.164 format (1-10,000). message: SMS text content (max 1600 characters). sender_id: Sender ID (1-11 alphanumeric chars). Use list_sms_sender_ids to find approved IDs, or 'MojaWave' as the default fallback. name: Optional campaign name for your reference (e.g. "June Promo"). |
| list_sms_sender_idsA | List approved SMS sender IDs available on your account. Returns IDs with status "approved". If the list is empty, the user has no custom sender IDs yet — use 'MojaWave' as the default shared sender ID, which is always available as a fallback. Call this before sending to pick the correct sender ID. |
| get_bulk_sms_jobA | Get the status and progress of a bulk SMS job. Args: job_id: The job UUID returned by send_bulk_sms. |
| get_messageA | Get full details and delivery status (timeline) for a single message. Args: message_id: The UUID of the message returned when it was sent. |
| get_credit_balanceA | Get current SMS and email credit balances for your organization. |
| verify_webhook_signatureA | Verify a MojaWave webhook's HMAC-SHA256 signature. Pass the RAW request body (exactly as received), the value of the X-MojaWave-Signature header, and your webhook signing secret. Returns whether the signature is valid — only act on webhook events that verify as valid. Args: payload: The raw webhook request body (do not re-serialize it). signature: The X-MojaWave-Signature header value. secret: Your webhook signing secret (whsec_...). |
| list_email_domainsA | List all email sending domains registered on your account. Call this before send_email to confirm which domains are verified and available. Only domains with status "verified" can send mail. |
| list_email_sendersA | List all registered sender addresses available for sending email. Returns the email addresses you can use in the from_email field of send_email. Each sender belongs to a verified domain. |
| send_emailA | Send a transactional email from a registered sender address. Costs 1 credit per recipient (to + each cc + each bcc). At least one of body (plain text) or html is required. Call list_email_senders first to confirm from_email is registered. ALWAYS confirm to, subject, from_email, and body/html with the user before sending — this spends real credits and delivers a real email. Args: to: Recipient email address (e.g. customer@example.com). from_email: Registered sender address on a verified domain (e.g. noreply@yourdomain.com). Use list_email_senders to find valid values. subject: Email subject line (max 500 chars). body: Plain-text body. At least one of body or html is required. html: Optional HTML body (e.g. "Hello"). Provide alongside body as a fallback for clients that don't render HTML. from_name: Optional display name shown in the recipient's inbox (e.g. "Duka Masta Billing"). cc: Optional list of CC addresses. Each costs 1 credit. bcc: Optional list of BCC addresses. Each costs 1 credit. reply_to: Optional reply-to address if different from from_email. schedule_at: Optional future delivery time in ISO-8601 (e.g. 2026-06-15T09:00:00Z). Naive datetimes (no Z/offset) are treated as EAT (Africa/Dar_es_Salaam, UTC+3). Leave empty to send immediately. tags: Optional string labels for filtering in message history (max 10). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mojawave/mojawave-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server