claude mcp add lightning-enable-mcp -- npx -y lightning-enable-mcp
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
9 ★ · refined-element/lightning-enable-mcp · read from the repository page · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 9 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository refined-element/lightning-enable-mcp;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
Third-party quality signals
Part of Lightning Enable — infrastructure for agent commerce over Lightning.
Lightning Enable MCP Server Monetize your own API — 30-day free trial Agents pay your API per request over Lightning — flat subscription at $49/mo, and you keep 100% of every sat. - **Start free trial** — 30 days, no charge today - **Fast Lane** — pay 100 sats over Lightning, no card - **Pricing** Or sign up without leaving your agent: call the create_lightning_enable_account tool. An open-source MCP (Model Context Protocol) server that enables AI agents to make Lightning Network payments and participate in agent-to-agent commerce. Wallet, invoice, L402, budget, and API-discovery tools work out of the box with just a wallet. Producer tools (sell access via L402) and Agent Service Agreement (ASA) tools (agent-to-agent discovery, request, settlement, and attestation over Nostr) unlock with an Agentic Commerce subscription. See the full tool list. Available in **.NET** and **Python**. What It Does Give your AI agent a Lightning wallet and it can: - **Pay invoices** — Send Bitcoin via Lightning to any BOLT11 invoice - **Access L402 APIs** — Automatically pay L402 challenges for seamless API access - **Discover APIs** — Search the L402 API registry to find paid APIs by keyword or category, or fetch a specific API's manifest for full endpoint details and pricing - **Track spending** — Budget limits, a durable receipt log, and balance checks - **Create invoices** — Generate invoices to receive payments - **Run wallet operations** — BTC price, currency exchange, and on-chain sends (Strike; on-chain also LND) - **Self-bootstrap a Lightning Enable account** — create_lightning_enable_account pays a ~100-sat activation fee over L402 and returns a merchant API key: the free→paid signup form that *is* the protocol, unlocking the producer + ASA tools with no browser or checkout page. - **Sell services (L402 Producer)** — Set up the seller account, put an API behind L402, price its routes, list it publicly, mint payment challenges and verify payer tokens — all from one tool, so an agent can go from an API key to a paid endpoint without touching REST - **Agent commerce (ASA)** — Discover, request, settle, and review agent-to-agent services on Nostr Quick Start 1. Install 2. First run — setup_wallet Nothing else works without a wallet, so start there. Ask your agent: With no arguments it reports which wallet is configured and where the credential came from — the provider and the source, never the credential itself. If there is no wallet, it hands back the setup steps. **The shortest path is NWC.** In your wallet app (Alby Hub, CoinOS, or any NIP-47 wallet) create a Nostr Wallet Connect connection, copy the nostr+walletconnect:// string, and give it to the agent: setup_wallet validates the string, connects to the wallet to prove it answers, then writes it to ~/.lightning-enable/config.json with the file's permissions restricted to your user. It reports the wallet's declared methods and balance. Restart the server afterwards so it picks up the new wallet. **Or set an environment variable** (in the Claude Desktop config below, say). L402 — the whole point of this server — needs a wallet that returns the payment **preimage**: - **Strike** — STRIKE_API_KEY, from https://dashboard.strike.me - **NWC** — NWC_CONNECTION_STRING, from CoinOS / CLINK / Alby Hub - **LND** (your own node — always returns a preimage) — LND_REST_HOST + LND_MACAROON_HEX - Self-signed node cert? Set LND_TLS_CERT_PATH to the node's tls.cert (pins TLS to that cert). LND_SKIP_TLS_VERIFY=true is the escape hatch, not the recommendation. Optional: LND_FEE_LIMIT_SATS, LND_PAYMENT_TIMEOUT_SECONDS. > ⚠️ **OpenNode** (OPENNODE_API_KEY) works for **invoicing / direct payments only — it never returns a preimage, so it cannot pay L402 challenges.** Don't make it your only wallet if you want L402 (the core use case). If several are set, priority is: **LND > NWC > Strike > OpenNode**, and **environment variables win over the config file** — setup_wallet refuses to write a connection string that an env var would override, and tells you which variable to unset. See Supported Wallets for the full compatibility matrix. 3. Prove the whole loop works — test_l402_payment Ask your agent: This pays a public **1-sat** L402 endpoint end to end, proving your wallet is connected, returns a preimage, and can complete a real L402 payment. It's the one-line answer to "is my wallet actually working?" — and it costs about 1 satoshi. 4. Then have some fun — buy a t-shirt