Home > engineering > Introducing NetcoreCloud CPaaS MCP Servers for Email, SMS, WhatsApp, and RCS

Introducing NetcoreCloud CPaaS MCP Servers for Email, SMS, WhatsApp, and RCS

raj shinde

Software Engineer

Manage your communication stack through plain-English prompts instead of hand-writing API calls. One interface, four channels, and 64 production-ready tools.

What is MCP, and why does it matter?

MCP (Model Context Protocol) is an open standard that lets AI assistants connect to external tools and services in a consistent way.

Before MCP, every AI client needed its own custom integration. You had to rebuild the same connector logic for each platform, with different auth methods, schemas, and edge cases.

With MCP, you build once and run anywhere MCP is supported: Claude Desktop, Cursor, n8n, and more.

The flow is simple:

You (plain English) → AI Assistant → MCP Protocol → MCP Server → NetcoreCloud API

You describe the outcome. The assistant chooses the right tool. The MCP server handles validation, API calls, and structured responses.

Why use MCP when APIs already exist?

Your APIs are still the source of truth. MCP improves how humans interact with them.

APIs are built for machines: endpoints, payload schemas, auth headers, and response parsing. MCP is built for people: intent-first requests in natural language.

That difference unlocks practical benefits:

Discoverability - Ask for the result you want instead of remembering endpoint names.
Guided error handling - Missing inputs trigger follow-up questions, not dead-end 400s.
Cross-channel orchestration - Multi-step workflows become single prompts.
Team accessibility - Product, ops, and support teams can safely run communication tasks.
Built-in safety - SMS preview-before-send helps prevent accidental blasts.
Depth of coverage - 64 tools across Email, SMS, WhatsApp, and RCS.

The four MCP servers at a glance

email-api – Email – 7 tools
Send emails, inspect delivery and bounce events, manage suppressions

sms-api – SMS – 6 tools
Preview/send single and bulk SMS, check delivery, validate numbers

whatsapp-api – WhatsApp – 39 tools
Send messages, manage templates/media/flows, track analytics, handle payments

rcs-api – RCS – 12 tools
Send rich cards/carousels/files, manage templates, preview and dispatch

All four follow the same operating model: describe intent, let the assistant pick tools, and let the server execute safely.

Email API MCP server

The Email MCP server wraps NetcoreCloud Email API v6 into seven tools across sending, analytics, and suppression management.

Send emails without payload plumbing

Use plain prompts for HTML, text, or AMP emails, including CC/BCC/reply-to and tags.

Example prompts:

“Send a welcome email to priya@example.com from hello@myapp.com with subject Welcome aboard.”
“Send a plain text OTP to user@example.com: Your code is 483921.”

The server validates required fields and configuration before calling upstream APIs.

Troubleshoot deliverability conversationally

Instead of switching dashboards and filters, ask directly:

“What is my email delivery rate for the last 7 days?”
“Show all bounce events from yesterday.”
“Did the password reset email to raj@company.com get delivered?”

Use get_email_stats for aggregate metrics and get_event_logs for recipient-level event tracing.

Manage suppression lists quickly

Common suppression tasks become one-liners:

“Add spam-reporter@example.com to suppression.”
“Is user@example.com blocked?”
“Remove test@example.com from suppression.”

Email tools summary

send_email – Send transactional or promotional email (HTML, text, AMP)
get_email_stats – View aggregate delivery, open, click, and bounce metrics
get_event_logs – Inspect per-email events for debugging
add_suppression – Add an address to suppression
list_suppressions – List suppressed addresses
get_suppression_status – Check suppression status for one address
remove_suppression – Remove an address from suppression

SMS API MCP server

The SMS MCP server focuses on safe execution, delivery visibility, and fast validation.

Send single or bulk SMS

Single SMS: Provide number, message, optional sender ID, and optional schedule (yyyymmddhhmm).
Bulk SMS: Send personalized messages in one job using the JsonBulkApi format.

Example prompts:

“Send ‘Your order #4521 has shipped’ to 9876543210.”
“Schedule an SMS to 9123456789 for tomorrow 10:00 AM: Do not forget your appointment.”

The preview-first flow (preview_sms / preview_bulk_sms) adds an explicit approval step before dispatch.

Check delivery and number quality

“What is the delivery status for request ID abc123?”
“Validate these numbers before campaign send: 9876543210, 1234567890, 98765.”

validate_numbers runs locally and checks Indian mobile format rules, helping avoid wasted credits.

SMS tools summary

preview_sms – Preview a single SMS (recipient, message, character count)
send_sms – Send a single SMS after approval
preview_bulk_sms – Preview a bulk SMS job
send_bulk_sms – Send a bulk SMS job after approval
check_delivery_status – Retrieve delivery status by request ID
validate_numbers – Validate numbers locally (no API call)

WhatsApp MCP server

With 39 tools, the WhatsApp MCP server is the most comprehensive in the suite. It covers messaging, templates, media, consent, flows, analytics, and payments on top of NetcoreCloud WhatsApp APIs.

Send outbound and in-window messages

WhatsApp supports two primary send modes:

send_whatsapp_message for template-led outbound initiation.
send_whatsapp_conversation_message for replies inside the 24-hour conversation window.

Manage the full template lifecycle

Template operations that usually require multiple dashboard steps are available by prompt:

“List all approved WhatsApp templates.”
“Create appointment_reminder template with a text body.”
“Check approval status for summer_sale template.”
“Preview diwali_offer template.”

Key template tools include:

get_template_list, create_whatsapp_template, edit_whatsapp_template, delete_whatsapp_template
get_template_preview, get_template_status
get_template_category_list, get_template_language_list, edit_whatsapp_template_category
get_display_number_details, get_template_profile_details

Additional tools are available for media handling, flows, and advanced account operations.

RCS API MCP server

RCS adds rich, app-like messaging in the native inbox: cards, carousels, media, and actions. The RCS MCP server wraps the Netcore RCS API with 12 tools.

Send rich experiences, not just text

Example prompts:

“Send a rich card to +919876543210 with image, title, description, and Buy Now button.”
“Send a carousel of three product cards to +919123456789.”
“Send Holi template to +919876543210 with personalized attributes.”

Core send tools:

rcs_send_rich_card
rcs_send_rich_card_carousel
rcs_send_rich_card_file
rcs_send_template_message (includes fallback chain handling)

Create and maintain templates by conversation

Manage template lifecycle without leaving chat:

Create: rcs_create_template_text, rcs_create_template_rich_card
Edit: rcs_edit_template_rich_card, rcs_edit_template_carousel, rcs_update_template
Discover: rcs_fetch_template, rcs_preview_template, rcs_fetch_bot_info

RCS tools summary

rcs_send_rich_card – Send one rich card
rcs_send_rich_card_carousel – Send a rich card carousel
rcs_send_rich_card_file – Send a rich card with file attachment
rcs_send_template_message – Send template message with attribute substitution
rcs_create_template_text – Create text template
rcs_create_template_rich_card – Create rich card template
rcs_edit_template_rich_card – Edit rich card template
rcs_edit_template_carousel – Edit carousel template
rcs_update_template – Update template metadata/content
rcs_preview_template – Preview template by ID or name
rcs_fetch_template – List and filter templates
rcs_fetch_bot_info – Get bot/client configuration metadata

Multi-channel workflows in one conversation

The biggest win is orchestration across channels without custom glue code.

Example prompts:

“Check if raj@example.com is suppressed. If not, send a welcome email. Also send order confirmation on WhatsApp.”
“Run Diwali campaign on WhatsApp for opted-in users. Fall back to RCS where possible, then SMS for the rest.”
“Find hard bounces from this month, suppress those emails, then send a WhatsApp request to update contact details.”

No scripts. No manual orchestration. Just intent.

Security and operational controls

Per-client credentials are isolated per session.
Key injection keeps secrets out of model-visible content.
Input validation runs before outbound API calls.
Rate limiting is configurable per server.
HTTPS + timeouts protect upstream communication.
Stdio mode removes external network attack surface.
SMS hardening supports MCP endpoint auth (AUTH_ENABLED=true) plus separate BulkSMS credentials.
WhatsApp raw responses are returned without transformation/caching for current-state accuracy.

Quick setup examples

Email (Streamable HTTP)

{
  "mcpServers": {
    "netcore-email": {
      "type": "streamableHttp",
      "url": "https://cpaasmcp.netcorecloud.net/email-api/v1/mcp",
      "headers": {
        "Authorization": "Bearer your-email-api-key"
      }
    }
  }
}

SMS (Streamable HTTP)

{
  "mcpServers": {
    "netcore-sms": {
      "type": "streamableHttp",
      "url": "https://cpaasmcp.netcorecloud.net/sms-api/v1/mcp",
      "headers": {
        "X-API-Key": "your-mcp-access-key",
        "X-BulkSMS-Username": "your-username",
        "X-BulkSMS-Password": "your-password",
        "X-BulkSMS-FeedID": "your-feed-id"
      }
    }
  }
}

WhatsApp (Streamable HTTP)

{
  "mcpServers": {
    "netcore-whatsapp": {
      "type": "streamableHttp",
      "url": "https://cpaasmcp.netcorecloud.net/v1/mcp/whatsapp",
      "headers": {
        "Authorization": "your-whatsapp-api-token"
      }
    }
  }
}

RCS (Streamable HTTP)

{
  "mcpServers": {
    "netcore-rcs": {
      "type": "streamableHttp",
      "url": "https://cpaasmcp.netcorecloud.net/rcs-api/v1/mcp",
      "headers": {
        "X-Netcore-Api-Key": "your-rcs-api-key",
        "X-Netcore-Base-Url": "https://your-rcs-api-endpoint"
      }
    }
  }
}