Robase SMS

dev.robasePublished by robase.devOfficial publisherv1.0.0Updated Oct 26, 2026

Prepaid SMS OTP and transactional SMS API. Eight priced markets: NG, GH, KE, ZA, GB, BJ, CI, US.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Remote Robase endpoint that lets an assistant send prepaid SMS OTP and transactional messages to eight priced markets.

What you can do
  • Send prepaid SMS OTP and transactional SMS messages through the Robase API.
  • Target recipients in eight priced markets: NG, GH, KE, ZA, GB, BJ, CI and US.
  • Authenticate each request with a Robase workspace API key, ideally a dedicated Agent key.
  • Access can be cut off at any time by revoking the key in the Robase dashboard.
  • No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Use it when an assistant needs to deliver one-time passcodes or transactional text messages to phone numbers in the supported markets, and you already have a Robase workspace with prepaid credit.
Requirements
A remote streamable HTTP endpoint at api.robase.dev; no local package or runtime. A Robase workspace API key sent as the Authorization bearer header, ideally a dedicated Agent key. Prepaid balance on the Robase account, since messaging is prepaid and priced per market. Network access to the Robase API.
Before you install
The API key is a secret sent in the Authorization header; store it safely and prefer a dedicated Agent key so it can be revoked independently. Sending SMS spends prepaid credit, and pricing differs by market. The assistant can send real messages to real phone numbers, which may incur cost and reach third parties. Revoking the key in the dashboard cuts access on the next request.

Installation

In SourceWeft

  1. Open Robase SMS in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/dev.robase%2Fsms/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.

{
  "mcpServers": {
    "robase-sms": {
      "type": "http",
      "url": "https://api.robase.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 20, 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.