Cadence

com.cadencercsPublished by cadencercs.comv0.3.1Updated Oct 24, 2026

Send RCS messages from your agent and get typed replies. Automatic SMS fallback.

VerifiedSTDIODesktop onlyDeveloper Tools Communication & Collaboration

Server details

Identifier: com.cadencercs/cadence
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 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 cadencercs.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.cadencercs%2Fcadence.svg)](https://sourceweft.com/mcp/com.cadencercs%2Fcadence?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Cadence lets an assistant send RCS messages, with automatic SMS fallback, and read typed replies through a local MCP process.

What you can do: Send RCS messages from the assistant, with automatic SMS fallback when RCS is unavailable. Receive and read typed replies to those messages. Optionally expose three one-way-door tools: sync_google, request_verification and request_launch. Point the client at a sandbox key to simulate delivery end to end, or a live key to reach real handsets.
When to use it: Use it when an assistant should reach people over RCS or SMS, for example for notifications or conversational outreach, and you want to test the flow in a sandbox before sending real messages.
Requirements: Runs as a local npm package over stdio. Requires a Cadence API key in CADENCE_API_KEY; a sandbox key simulates delivery, a live key sends real messages. CADENCE_API_URL can override the API host, which defaults to the Cadence API. Network access to Cadence is needed.

Before you install

A live CADENCE_API_KEY sends real messages to real handsets, which may cost money; use a sandbox key to test. Setting CADENCE_ALLOW_IRREVERSIBLE to 1 exposes irreversible tools: sync_google creates a Google agent that can never be deleted, and request_launch freezes the launch questionnaire. Message content is sent to Cadence and to recipients.

Installation

In SourceWeft

Open Cadence 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.3.1LatestSep 16, 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.