SaturnZap logo

SaturnZap

Non-custodial Lightning wallet with 25 MCP tools for agent-managed payments, channels, liquidity, and L402 API access.

Install SaturnZap

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "saturnzap": {
      "command": "uvx",
      "args": [
        "saturnzap"
      ],
      "env": {
        "SZ_PASSPHRASE": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

SaturnZap MCP server gives AI agents stdio access to a local, non-custodial Lightning wallet and its own Lightning node. It routes MCP requests through the SaturnZap daemon over a Unix domain socket, with JSON responses designed for machine use. Agents can manage payments, receive Bitcoin, interact with channels, and pay for L402-gated APIs. Reach for it when an agent needs to control Lightning funds locally without operating a full Bitcoin node.

Use cases

  • Send Lightning payments from an agent workflow
  • Receive Bitcoin through a locally controlled node
  • Pay L402-gated APIs during automated tasks
  • Open channels to Lightning Network peers
  • Fetch paid API data with invoice settlement

Key features

  • 25 MCP tools over stdio
  • Non-custodial encrypted BIP39 wallet
  • Local LDK Lightning node
  • JSON-first CLI and IPC architecture
  • Esplora chain-sync fallback
  • L402 payment support

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

6/6 checks healthy over the last 41d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · saturnzap (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars7Stargazers on the source repository.
Last commit28d agoMost recent push to the default branch.

How SaturnZap works

What SaturnZap MCP server does

SaturnZap MCP server exposes a local Lightning wallet to AI agents through Model Context Protocol over stdio. The wallet is non-custodial: its BIP39 seed is encrypted on the agent's machine, and SaturnZap does not hold or access the private keys. The software runs its own Lightning node, so the agent controls its wallet and peer relationships.

The server is intended for autonomous workflows that need to send or receive Bitcoin payments, manage Lightning connectivity, or pay for APIs protected by L402. It is a local CLI and MCP integration rather than a hosted wallet, custodial service, or web application.

How it works

The MCP process communicates with the SaturnZap daemon through a Unix domain socket. The daemon owns the LDK-based Lightning node and provides the wallet and payment operations behind the MCP interface. CLI commands and MCP requests can use the same daemon, which avoids separate database locks and network port conflicts.

If no daemon is running, SaturnZap can fall back to an ephemeral node for commands. Chain synchronization uses Esplora REST APIs, with automatic fallback among LQWD, Blockstream, and mempool.space endpoints. A full Bitcoin node is therefore not required.

On mainnet, new installations are configured to use LQWD as the default Lightning Service Provider. This is a default peer relationship rather than a requirement; agents can connect to other Lightning nodes and control their own channels.

Setup and configuration

Install the package with the provided shell installer, or use uv tool install with the SaturnZap release link that supplies the vendored LDK Node wheel. Set SZ_PASSPHRASE before initialization, then run the setup command to generate a seed, start the node, and select the default LQWD peer. Installing the service keeps the node running across reboots.

Typical setup commands include:

server.ts
export SZ_PASSPHRASE="your-secure-passphrase"
sz setup --auto
sz service install
sz connect-info --check

The connection-information command can verify and share the node URI with peers or LSPs. SZ_REGION=NEAREST can select a regional LQWD peer using timezone-based selection instead of the default agent-focused peer.

Tools and capabilities

SaturnZap MCP server includes 25 tools over stdio. The documented wallet capabilities include:

  • Sending Lightning payments from invoices, with a maximum-sats limit available in the CLI.
  • Receiving Bitcoin through the node's Lightning connectivity.
  • Opening channels and connecting to peers on the Lightning Network.
  • Using LQWD or other Lightning peers for channel and liquidity access.
  • Fetching L402-protected URLs while paying the required invoice.
  • Returning structured JSON suitable for agent runtimes and orchestration scripts.

Mainnet spending commands require confirmation unless the relevant non-interactive --yes option is supplied when using the CLI.

Limitations and notes

The MCP transport documented by the project is stdio, so the daemon and wallet run on the agent's machine. Protect the passphrase and local wallet data accordingly. First-time chain synchronization can take several minutes; later starts are expected to be faster.

SaturnZap is not custodial and does not provide a hosted account. Network access, peer availability, channel liquidity, Esplora endpoints, and Lightning payment conditions can affect operation. The software is MIT-licensed, while fees may apply when using LQWD infrastructure or Lightning routing and channel services.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about SaturnZap

SaturnZap is an MCP server that connects AI agents to a locally controlled Lightning Network wallet and node. Its tools support wallet operations, sending and receiving Lightning payments, channel and peer connectivity, and paying L402-gated APIs. It runs over stdio and keeps the wallet's encrypted seed on the agent's machine.

Install it with the project's shell installer or with `uv tool install` using the SaturnZap release link for the vendored LDK Node wheel. Then set `SZ_PASSPHRASE`, run `sz setup --auto`, and configure the MCP client to launch the stdio server.

Yes, SaturnZap supports Cursor through its stdio MCP server. The README also names Claude and VS Code as compatible MCP clients; configure the client to start SaturnZap locally and allow it to access the wallet tools.

No, SaturnZap does not require a full Bitcoin node. Its LDK node obtains chain data through Esplora REST APIs and can fall back among LQWD, Blockstream, and mempool.space endpoints.

Yes, SaturnZap can pay L402-gated APIs. Its fetch workflow retrieves a URL and can settle the required Lightning invoice, subject to the wallet having usable funds and Lightning connectivity.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSaturnZap AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/saturnzap?style=directory)](https://allmcps.com/mcp/saturnzap)
HTML Embed
<a href="https://allmcps.com/mcp/saturnzap"><img src="https://allmcps.com/api/badge/saturnzap?style=directory" alt="SaturnZap on AllMCPs" /></a>