Overview

MCP (Model Context Protocol) is an open standard that lets AI assistants connect to external tools and services. Instead of writing API calls, you describe the outcome in plain English. Your AI assistant picks the right tool, and the MCP server handles validation, the API request, and the response.

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

Getting Started

To use Netcore CPaaS MCP servers, you need an active CPaaS account.

1. Sign up for a Netcore CPaaS account, or log in to your existing account.
2. Ensure the channels you want to use (Email, SMS, RCS, WhatsApp) are activated. Contact the Netcore helpdesk if you need a channel enabled.
3. Retrieve your authentication credentials for each channel. View Authentication.
4. Add the MCP server configuration to your AI client. View Available Endpoints.
5. Restart your MCP server. The Netcore tools will be available in your next session.

Authentication

Each Netcore CPaaS MCP server uses a different authentication mechanism depending on the channel. All credentials are passed as HTTP headers in your MCP client configuration.

📘

Important Note

Keep your credentials secure. Never hardcode them in source code or commit them to version control. Use environment variables or a secrets manager.

Email Bearer Token

Authorization: Bearer <your-email-api-key>

Retrieve your Email API key from the CPaaS dashboard under Settings → API Keys.

WhatsApp Bearer Token

Authorization: <your-whatsapp-api-token>

Retrieve your WhatsApp API token from the CPaaS dashboard.

RCS Base URL

X-Netcore-Api-Key: <your-rcs-api-key>
X-Netcore-Base-Url: <https://your-rcs-api-endpoint>

Retrieve your RCS base URL from your CPaaS dashboard.

SMS Username + Password + Feed ID

X-BulkSMS-Username: <your-username>
X-BulkSMS-Password: <your-password>
X-BulkSMS-FeedID: <your-feed-id>

All values are required. These credentials are available from the SMS section of your CPaaS dashboard. Contact the Netcore helpdesk if you cannot locate your Feed ID.

Available Endpoints

Configuration Examples

Use the JSON snippets below to configure each channel in your MCP client (e.g., Claude Desktop, Cursor, or any MCP-compatible AI agent).

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

{
  "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"
      }
    }
  }
}

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

{
  "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"
      }
    }
  }
}

Transport Options

Agent Permission and Access Control

When managing AI agent permissions, it is important to implement stricter controls for sensitive tasks, such as sending messages. Granting permanent, unrestricted access can create significant security and operational risks. AI agents with persistent permissions can:

• Send messages without human oversight during unexpected behaviour or prompt injection attacks.
• Generate substantial costs through automated message campaigns that bypass approval workflows.
• Create compliance violations by sending messages that don't meet regulatory requirements.
• Damage customer relationships through inappropriate, mistimed, or excessive communications.

Refer to the MCP implementation guidelines for more details.

⭐

Best practice

Configure agent permissions following the principle of least privilege. Grant only the minimum access necessary for the specific task at hand, for the shortest duration required.

Built-in Safety Controls

Netcore CPaaS MCP servers include several controls to reduce operational risk:

• Preview-before-send for SMS: preview_sms and preview_bulk_smsCreate an explicit human approval step before any message is dispatched. Use these in workflows where blast mistakes would be costly.
• Input validation runs before every outbound API call. Missing or malformed parameters return a guided error rather than a silent failed send.
• Per-client credential isolation — credentials are scoped per session and never exposed in model-visible content.
• HTTPS and timeouts protect all upstream communication.
• Rate limiting is configurable per server.

Use Cases

Email

The Email MCP server wraps Netcore Email API v6 and covers sending, delivery analytics, and suppression management.

Available Tools

Top Use Cases

SMS

Preview-first workflow: Always run preview_sms or preview_bulk_sms before the corresponding send tool. This adds an explicit approval step and prevents costly blast mistakes.

Available Tools

Top Use Cases

WhatsApp

The WhatsApp MCP server is the most comprehensive in the suite. It covers outbound messaging, template lifecycle management, media, flows, consent, analytics, and payments on top of the Netcore WhatsApp Business API.

Available Tools

Messaging

Template Management

Additional tools are available for media handling, flows, consent management, analytics, and payments.

Top Use Cases

RCS

Available Tools

Top Use Cases

Read this blog to know more about CpaaS MCP servers.