Saperly

io.github.idanbier999Published by GitHub account idanbier999v0.1.2Updated Oct 24, 2026

Phone carrier for AI agents. Provision numbers, make calls, send SMS, TCPA compliance built-in.

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

Saperly is a phone carrier for AI agents, letting an assistant provision phone numbers, place calls and send SMS with built-in TCPA compliance.

What you can do
Provision and manage phone numbers for agents, according to the description's carrier model. Place outbound calls and send SMS messages from those numbers. Rely on built-in TCPA compliance handling. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Use it when an assistant needs a real phone presence: making calls, sending text messages, or obtaining numbers for agent-driven telephony, with compliance handled by the provider.
Requirements
Runs as a local process via the npm package @saperly/mcp over stdio, desktop only. Requires a Saperly API key in the SAPERLY_API_KEY environment variable (live or test key), obtained from the Saperly portal. An optional SAPERLY_BASE_URL variable overrides the API base URL for local dev or staging.
Before you install
The API key is a secret passed by environment variable and grants access to the account, including live keys that may incur real charges; the description mentions 500 free credits on signup, so paid usage is likely. Sending SMS and placing calls are outward-facing actions that reach real recipients and may carry legal obligations, though TCPA compliance is described as built in.

Installation

In SourceWeft

  1. Open Saperly 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.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

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

Version history

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