Kindlesms

io.github.lexerAnnPublished by GitHub account lexerAnnv1.0.2Updated Oct 24, 2026

Send SMS, manage approved sender IDs, and check credits via KindleSMS.

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant send SMS messages, manage approved sender IDs, and check account credits through KindleSMS.

What you can do
This local MCP server connects an assistant to a KindleSMS account so it can send SMS messages, manage the approved sender IDs used for those messages, and check the account's remaining credits. It runs as a local process over stdio and exposes these actions as tools to the assistant.
When to use it
Use it when you want an assistant to send text messages or check SMS credit balance through KindleSMS as part of a workflow, rather than logging into the service manually.
Requirements
Runs as a local process on the user's machine, installed from the npm package kindlesms over stdio. Requires a KindleSMS Personal Connector Token supplied in the USER_TOKEN environment variable, obtained from Settings > Claude & API. Desktop only; no web execution.
Before you install
Requires the secret USER_TOKEN, which grants access to your KindleSMS account. Sending SMS can incur costs against your credits, and messages are sent to third parties. Sender ID changes affect how messages are identified.

Installation

In SourceWeft

  1. Open Kindlesms in the dashboard and add it to a workspace.
  2. 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.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 21, 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.