Lightning Wallet MCP

What is Lightning Wallet MCP?

An MCP server and CLI that gives AI agents a Bitcoin wallet on the Lightning Network. It integrates with Claude Code, Cursor, Windsurf, and any agent framework, enabling agents to pay for APIs using L402 and X402 protocols.

How to use Lightning Wallet MCP?

Install globally via npm (npm install -g lightning-wallet-mcp) and use the lw CLI, or configure as an MCP server for agent frameworks. Registration, funding, and agent management are done via CLI commands or MCP tools.

Key features of Lightning Wallet MCP

• Instant Lightning Network payments settle in milliseconds.
• L402 and X402 protocol support for paid APIs.
• Operator/agent hierarchy with isolated funds and spending limits.
• Free 100 sats for new operators (first 100 installs).
• Webhook notifications for payments and events.
• Full transaction history export in JSON or CSV.

Use cases of Lightning Wallet MCP

• AI agent autonomously pays for premium API content per request.
• Developer manages multiple agents with individual budgets for different tasks.
• Operator receives real-time webhook notifications when agents make payments.
• Agent claims LNURL-withdraws or authenticates via LNURL-auth.
• Account recovery and API key rotation for operator security.

FAQ from Lightning Wallet MCP

How do I get a free 100 sats?

Register with an email, verify the link, then after your account is 3 hours old, run lw claim-promo or the claim_promo tool. One bonus per operator, first 100 installs only.

What protocols does Lightning Wallet MCP support for paid APIs?

It supports L402 (Lightning Network) as the primary protocol and X402 (USDC on Base) as an automatic fallback. The server auto-detects which protocol the API uses.

What are the different ways to use Lightning Wallet MCP?

Two ways: as a CLI (lw command) for any agent framework with Bash access, or as an MCP server configured in Claude Code, Cursor, or Windsurf using npx.

How are agent funds isolated from the operator?

Each agent has its own balance and spending limit set by the operator. Funds can be transferred between agents or swept back to the operator. Deleting an agent returns its balance to the operator.