Telerivet

com.telerivetPublished by telerivet.comOfficial publisherv1.0.0Updated Oct 24, 2026

Send, automate, and orchestrate SMS, WhatsApp, Viber, IVR, and USSD messaging in 150+ countries.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant send and automate SMS, WhatsApp, Viber, IVR, and USSD messages through Telerivet in many countries.

What you can do
Telerivet exposes its messaging platform to an assistant over a remote MCP endpoint. According to the registry description, it covers sending, automating, and orchestrating SMS, WhatsApp, Viber, IVR, and USSD messaging in more than 150 countries. No individual tools are listed in the manifest, so the exact operations available are not documented here.
When to use it
Worth considering when an assistant needs to send or coordinate multi-channel messages, such as SMS or WhatsApp notifications, or interactive voice and USSD flows, across many countries. It is a hosted service, so it suits users who already use Telerivet or want a managed messaging provider rather than local tooling.
Requirements
A remote MCP endpoint at using streamable HTTP. Authentication is OAuth and is required. No environment variables, headers, or packages are declared.
Before you install
The server can send messages to real recipients, which may cost money and cannot be undone. OAuth grants access to a Telerivet account, so review the scopes requested. Message content and recipient data are handled by Telerivet as a third party.

Installation

In SourceWeft

  1. Open Telerivet in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.telerivet%2Ftelerivet/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "telerivet": {
      "type": "http",
      "url": "https://api.telerivet.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.