RCS Campaigns

com.rcs-campaignsPublished by rcs-campaigns.comv0.1.10Updated Oct 24, 2026

Send RCS & SMS campaigns: templates, audiences, surveys, inbox replies, delivery webhooks.

VerifiedSTDIODesktop onlyCommunication & Collaboration Business & Commerce

Server details

Identifier: com.rcs-campaigns/campaigns
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 21, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to rcs-campaigns.com. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.rcs-campaigns%2Fcampaigns.svg)](https://sourceweft.com/mcp/com.rcs-campaigns%2Fcampaigns?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Lets an assistant send RCS and SMS campaigns — templates, audiences, surveys, inbox replies and delivery webhooks — from a local npm process.

What you can do: Send RCS and SMS campaigns, including templates and audiences, through the RCS Campaigns platform. Work with surveys and reply to inbox messages. Manage delivery webhooks for campaign events. The manifest lists no individual tools, so exact operations are not documented here.
When to use it: Useful when you want an assistant to draft, target and send RCS or SMS campaigns, handle survey responses or inbox replies, and wire up delivery webhooks without leaving the chat.
Requirements: Runs locally via npx from the npm package @rcs-campaigns/agent-toolkit over stdio; desktop only. Requires an RCS Campaigns account and a scoped agent key in RCS_AGENT_KEY, created in Settings → API keys. RCS_GATEWAY_URL is optional and defaults to the hosted production gateway.

Before you install

RCS_AGENT_KEY is a live secret that should be treated like a password; it carries only the scopes chosen when minted, so grant the minimum. The server sends real messages to audiences, which can incur costs and reach customers, and it manages webhooks. A key is tied to the environment it was minted in, so pointing RCS_GATEWAY_URL elsewhere will not work with a production key.

Installation

In SourceWeft

Open RCS Campaigns in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.10LatestSep 30, 2026
v0.1.9Sep 22, 2026
v0.1.6Sep 21, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.