Lightningfaucet MCP MCP Server

Most payments and commerce work still happens through a UI a human drives. Lightningfaucet MCP MCP server moves it into the conversation instead. Lightning wallet for AI agents. MCP server + CLI. Works with Claude Code, OpenClaw, Cursor, and any agent framework.

The short version

1. lw register --email you@example.com (or the register_operator MCP tool with an email) 2. Click the verification link we email you 3. After your account is 3 hours old: lw claim-promo (or the claim_promo MCP tool)

• Instant Payments — - Lightning Network transactions settle in milliseconds
• L402 + X402 Protocol Support — - Access any paid API automatically (Lightning or USDC)
• Operator/Agent Hierarchy — - Manage multiple agents with spending limits
• No Custody Risk — - Each agent has isolated funds with operator oversight
• Production Ready — - Battle-tested infrastructure powering real transactions
• Webhook Notifications — - Get notified instantly when payments arrive

The tools it exposes

The server publishes 11 tools. What each one is for:

• url — string
• method — string
• body — string
• max_payment_sats — number
• Webhooks — The Webhooks tool exposed by this server
• get_info — The get_info tool exposed by this server
• whoami — The whoami tool exposed by this server
• pay_l402_api — Access paid APIs with automatic payment. Supports both L402 (Lightning) and X402 (USDC on Base) protocols. Protocol is auto-detected from the 402
• keysend — The keysend tool exposed by this server
• register_webhook — The register_webhook tool exposed by this server
• Configuration — The Configuration tool exposed by this server

Getting it running

Installation goes through your MCP client rather than a global install: point it at lightning-wallet-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What it needs from you

Configuration is passed through the environment: LIGHTNING_WALLET_API_KEY, PRE_PAYMENT_HOOK_URL, AGENT_ID, AGENT_KEY, LIGHTNING_FAUCET_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Among the payments and commerce options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Lightningfaucet MCP's toolset — url, method, body and 8 more — is a fair guide to whether it matches your workflow. It is maintained by lightningfaucet; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Lightningfaucet MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• 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 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Lightningfaucet MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.