Sprint Mail

io.sprintmailPublished by sprintmail.ioOfficial publisherv1.0.0Updated Nov 5, 2026

Print and mail US letters by USPS First-Class, with tracking.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Sprint Mail lets an assistant print and mail physical US letters via USPS First-Class mail, with tracking.

What you can do
  • Send letters for printing and mailing through USPS First-Class mail
  • Track the delivery status of mailed letters
  • No tool list is published, so the exact operations are not documented here; the server is described only as printing and mailing US letters with tracking.
When to use it
Use it when you want an assistant to turn content into a physical letter that is printed and mailed within the United States, and to follow its delivery, for example for correspondence or notices that must go out on paper.
Requirements
A remote MCP endpoint at api-production.sprintmail.io over streamable HTTP. OAuth authentication is required; no environment variables or headers are declared. A Sprint Mail account and a way to pay for printing and postage are implied by the service.
Before you install
Mailing is a real-world, irreversible action that costs money for printing and postage, so confirm recipients and content before sending. The server requires OAuth sign-in, granting it access to your Sprint Mail account. Letter contents and addresses are sent to Sprint Mail and USPS.

Installation

In SourceWeft

  1. Open Sprint Mail 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/io.sprintmail%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": {
    "sprint-mail": {
      "type": "http",
      "url": "https://api-production.sprintmail.io/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.0LatestNov 5, 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.