MCP Integration - Connect AI Assistants to RCS Messaging

Open Standard

What is MCP?

MCP (Model Context Protocol) is an open standard created by Anthropic that lets AI assistants connect to external tools and services. Instead of writing code or using a REST API, you simply tell your AI assistant what you want in plain language — and it handles the rest.

With the SendRCS MCP integration, your AI assistant becomes a full RCS messaging operator. It can send messages, design rich cards, schedule campaigns — all from a single conversation.

MCP

Model Context Protocol

Open standard by Anthropic

Compatibility

Works With Your Favourite AI Tools

The SendRCS MCP server works with any MCP-compatible client.

Claude Desktop

OAuth & API key

Claude Code

CLI — API key or OAuth

Cursor

AI code editor

ChatGPT Desktop

MCP support

Manus

MCP configuration

Any MCP Client

Open standard

3 Steps

Get Started in Minutes

1

Connect

Add the SendRCS MCP server to your AI client. Just enter the URL and authenticate — no SDK, no code, no setup.

2

Talk

Tell your AI assistant what you want in plain language: “Send a rich card with our summer offer to all Danish customers.”

3

Done

The AI assistant sends the message, schedules the campaign, or pulls the analytics — and confirms the result.

Authentication

Two Ways to Connect

Recommended

OAuth 2.0

Log in securely through your browser — no API key copying needed. Your AI client handles everything automatically.

Setup

In your AI client’s MCP server settings, add a new Streamable HTTP server:

Name:  SendRCS
URL:   https://api.sendrcs.eu/api/mcp

How the OAuth flow works

Your AI client opens a browser window to SendRCS login
Enter your email and password
Enter your 2FA verification code
Done — the client receives a secure token (valid 30 days)

Security

PKCE (Proof Key for Code Exchange)
Two-factor authentication (2FA)
Tokens can be revoked any time
30-day automatic expiration

For Developers

API Key

Connect using an API key from your SendRCS account. Simpler setup, ideal for automated systems.

Configuration

{
  "mcpServers": {
    "sendrcs": {
      "url": "https://api.sendrcs.eu/api/mcp",
      "headers": {
        "X-API-Key": "rk_your_api_key_here"
      }
    }
  }
}

API keys are found in the SendRCS app under Settings → API Keys.

Feature	OAuth	API Key
Setup	Login via browser	Copy-paste key
Expiration	30 days (auto)	Never (manual revocation)
2FA support	Yes	No
Best for	End users in AI clients	Automated systems, developers

MCP Tools

17 Powerful Tools at Your Command

Everything you need to manage RCS messaging through your AI assistant.

Sending

2 tools

rcs_send — Send a single RCS message (text, rich card, carousel, media). Supports SMS fallback, scheduling, and merge fields
rcs_send_batch — Send to up to 10,000 recipients. Messages are queued for background processing

Preview & Approval

1 tool

rcs_preview — Create a visual preview of your message before sending. Returns a preview link for review and a preview_id required by rcs_send

Validation

2 tools

rcs_validate — Validate message structure without sending. Returns errors, warnings, and suggestion limits
rcs_validate_schedule_time — Check if a scheduled send time is valid and in the future

Composing

3 tools

rcs_limits — Get all message limits & constraints: character limits, max cards, media sizes, suggestion limits
rcs_button_guidelines — Guidelines for card actions vs chip suggestions, with best practices and examples
rcs_workflow_guide — Recommended workflows and step-by-step guides for common messaging tasks

Monitoring

3 tools

rcs_batch_status — Get the status and progress of a specific batch sending job
rcs_batch_cancel — Cancel a batch job. Only cancels messages not yet sent
rcs_jobs — List all jobs (scheduled, processing, completed, failed, cancelled) with filtering and pagination

Engagement & History

3 tools

list_rcs_interactions — List interactions (button clicks, replies) for campaigns. Track engagement by campaign, phone number, or date range
rcs_message_log — Query message history with filtering. Look up by ID or filter by date, phone number, campaign, status, and direction
rcs_conversation_status — Check if a phone number has an active 24-hour session. Follow-up messages within the window are free

Account

3 tools

list_sendernames — List all sender names (SMS and RCS) with status, type, and capabilities
rcs_timezones — Get available timezones for scheduling, including configured timezone and current local times
rcs_health — Quick health check for the RCS service

Message Types

All RCS Message Types Supported

Message Formats

Text — Rich text with optional suggestion chips
Text Basic — Plain text, no buttons, max 160 characters
Rich Card — Card with title, description, image/video, and up to 4 buttons
Carousel — Multiple swipeable cards (up to 10)
Media — Images, videos, audio files and documents

Interactive Buttons

Open URL — Opens a webpage
Dial — Starts a phone call
Postback — Sends a reply back for chatbot flows
Open in Webview — Opens a URL in an in-app browser
View Location — Opens a map location
Add to Calendar — Creates a calendar event
Reply Chip — Quick-reply button below the message

Features

Enterprise Features Built In

Batch Sending

Send to up to 10,000 recipients in a single command. Messages are queued for background processing.

SMS Fallback

Every RCS message can include an automatic SMS fallback for devices without RCS support. Just specify the fallback text and SMS sender.

Scheduling

Schedule messages for future delivery with timezone-aware scheduling. Supports all IANA timezones.

Conversation-Based Billing

Save credits with 24-hour conversation windows. The first message opens a window — all subsequent messages within 24 hours are free.

Campaign Analytics

Track engagement across campaigns: button clicks, user replies, URL opens, and dial actions. Filter by campaign, phone number, and date range.

Validation Before Sending

Validate any message before sending it. The AI assistant checks structure, character limits, button counts, and media constraints.

Safety First

Preview & Approve Before Sending

Every message sent via MCP goes through a preview step. You always see exactly what will be sent before it goes out.

1

Validate

AI checks message structure, limits, and constraints automatically

2

Preview

A visual preview page shows exactly how the message will look on a phone

3

Approve

Review the preview and approve it for sending — or save it as a template

4

Send

The AI sends the message only after preview verification and approval

Approval Setting

The “Approve before sending” setting is a checkbox in the web app under Settings → API & MCP → MCP Settings.

Enabled (recommended) — you must approve every message on the preview page before the AI can send it
Disabled — the AI can send immediately after creating a preview (preview step still required)

Save as Template

On the preview page, you can also save the message as a reusable template for later use in the web interface.

Compose with AI, preview it, save for campaigns
Add a template name and optional category

Message Limits

Limit	Value
Text message	Max 2,048 characters
Rich card title	Max 60 characters
Rich card description	Max 200 characters
Card action buttons	Max 4 per card, 25 characters each
Suggestion chips	Max 11, 25 characters each
Carousel cards	Max 10 cards
Batch recipients	Max 10,000 per request
Media file size	Max 1 MB
Campaign name	Max 100 characters
SMS fallback	Max 1,530 characters
Throughput	75 messages/second

Examples

What Can You Do With It?

Just tell your AI assistant what you want in plain language.

Inventory + campaign in one prompt

“Check our Shopify stock. If the blue sneakers are overstocked, create a beautiful RCS carousel with a 20% discount and send it to our ‘VIP’ segment in Berlin.”

Weather-triggered promo

“Check the weather in Munich this weekend. If it’s sunny, send our outdoor event guests a rich card with Saturday’s lineup and a ‘Reserve a Spot’ button.”

Property listings blast

“Take our 3 newest listings from the CRM, build a carousel with photos and prices, and send it to contacts tagged ‘house hunting’ in Copenhagen.”

Webinar re-engagement

“Find everyone who attended last month’s webinar but hasn’t signed up for the next one. Send them a rich card with the new speaker lineup and an early-bird link.”

Support ticket rescue

“Check Zendesk for tickets open longer than 48 hours. Send each customer a personal apology with a ‘Callback’ button that dials our support line.”

Gym membership renewal

“Find members whose membership expires this month. Send each one a rich card with their visit stats this year and a 15% early-renewal offer.”

Restaurant tonight

“Check tonight’s reservation list. Send everyone dining after 7pm a carousel with our new seasonal menu and a ‘Pre-order Now’ button.”

MCP vs REST API

Which one is right for you?

	MCP	REST API
Interface	Natural language (talk to your AI)	Code (HTTP requests)
Setup	Add URL to AI client	Integrate into your application
Authentication	OAuth or API Key	API Key
Best for	Business users, marketers, quick tasks	Developers, automated systems
Coding required	No	Yes
Batch sending	Yes (up to 10,000)	Yes (up to 10,000)
Scheduling	Yes	Yes
SMS Fallback	Yes	Yes
Analytics	Yes	Yes

Both methods access the same SendRCS platform and features. MCP is the no-code option — perfect for anyone who wants to control RCS messaging through conversation with an AI assistant.

Endpoint

URL:       https://api.sendrcs.eu/api/mcp
Protocol:  Streamable HTTP (JSON-RPC 2.0)
Standard:  Model Context Protocol (MCP) by Anthropic

Ready to Connect Your AI?

No subscription. No commitment. Free trial available.

Get started Documentation