# SaturnZap [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/lqwdtech/SaturnZap  
**GitHub Stars:** 7  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/saturnzap

## Description
CLI-first, non-custodial Lightning Network wallet for autonomous AI agents.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "saturnzap": {
    "command": "uvx",
    "args": ["saturnzap"],
    "env": {
      "SZ_PASSPHRASE": ""
    }
  }
}
```

**Requires environment variables:** `SZ_PASSPHRASE` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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:

```bash
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.

_Full upstream README: https://allmcps.com/mcp/saturnzap/readme_