Cadence MCP Server

Cadence is an MCP integration. Send RCS messages from your agent and get typed replies. Automatic SMS fallback.

Packages and local setup

The published npm package is @cadencercs/mcp, version 0.3.1. Its declared MCP transport is stdio.

The package declares CADENCE_API_KEY (required): Your Cadence API key. A sandbox key (sk_sandbox_…) simulates delivery end to end and reaches no handset; a live key sends real messages. Get one free at https://cadencercs.com/app.html — no card, no compliance wait.; CADENCE_ALLOW_IRREVERSIBLE: Set to 1 to expose the three one-way-door tools: sync_google, request_verification and request_launch. They create an agent at Google that can never be deleted, and freeze the launch questionnaire. Left unset they are absent from tools/list entirely, so no model in this configuration can reach them.; CADENCE_API_URL: Override the API host. Defaults to https://api.cadencercs.com..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.3.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related communication MCP servers for tools that cover the same kind of work.