Sats4ai MCP Server

Permissionless communication supercharger MCP server — 40+ Lightning-paid tools: AI phone calls in any language, voice in 602 languages, translation across 119 plus 452 rare languages frontier models don't serve, fax, SMS, transcription. Exposed over MCP by the sats4ai mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

A remote MCP (Model Context Protocol) server that gives AI agents access to AI phone calls in any language, voice in 602 languages, translation across 119, fax, SMS, transcription, audiobooks, image generation, music, document extraction, and more — all paid per-use with Lightning Network micropayments.

Its toolset

Everything the assistant can do here goes through one of these:

• list_models — Browse available AI models and pricing
• get_model_pricing — Get pricing for a specific model
• create_payment — Create a Lightning invoice for a service
• check_payment_status — Check if payment was received
• check_job_status — Poll async jobs (video, 3D, audiobook)
• get_job_result — Get completed job results
• request_refund — Request a refund for a failed service
• vote_on_service — Upvote or downvote a planned service
• list_planned_services — See upcoming services and vote
• Cursor — Restart Cursor. In a new chat, ask "what Sats4AI tools are available?" to confirm tool discovery. For autonomous payments, pair with a Lightning
• Windsurf — Edit ~/.codeium/windsurf/mcp_config.json (create it if missing). Important: Windsurf uses serverUrl (not url) for remote HTTP MCP servers:
• Communication — The Communication tool exposed by this server

Adding it to your client

sats4ai-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration

You will need one environment variable: SERVER_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Sats4ai's toolset — list_models, get_model_pricing, create_payment and 9 more — is a fair guide to whether it matches your workflow. It is maintained by cnghockey; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Sats4ai.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the sats4ai mcp server does with a few real requests.