SureSMS

com.suresmsPublished by suresms.comOfficial publisherv1.1.2Updated Oct 24, 2026

Send SMS, manage contacts and groups, and read delivery reports. OAuth 2.1 SureSMS login.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

SureSMS is a remote MCP server that lets an assistant send SMS messages, manage contacts and groups, and read delivery reports through a SureSMS account.

What you can do
Send SMS messages on your behalf through SureSMS. Create and manage contacts and contact groups. Read delivery reports for sent messages.
When to use it
Useful when you want an assistant to send text messages or look up delivery status and contact lists from a SureSMS account, for example for notifications or customer outreach.
Requirements
A remote MCP endpoint at mcp.suresms.com reached over streamable HTTP. Requires an OAuth 2.1 login to a SureSMS account; no API keys or environment variables are declared.
Before you install
The server can send SMS messages and change contacts and groups, which may incur messaging costs and reach real recipients. Grant access only to an account you are comfortable letting an assistant act through, and review outgoing messages before they are sent.

Installation

In SourceWeft

  1. Open SureSMS 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.suresms%2Fmcp/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": {
    "suresms": {
      "type": "http",
      "url": "https://mcp.suresms.com/mcp"
    }
  }
}

README

This repository has no README.

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.1.2LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.