lightning-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NWC_URL | No | Nostr Wallet Connect URL (required for payments). Alternatively use LIGHTNING_NWC_URL. | |
| LIGHTNING_RELAYS | No | Comma-separated Nostr relay URLs. Default: ai.wot defaults. | ai.wot defaults |
| LIGHTNING_NWC_URL | No | Alternative Nostr Wallet Connect URL (required for payments) instead of NWC_URL. | |
| LIGHTNING_MAX_SATS | No | Safety limit per payment. Default: 1000. | 1000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_balanceA | Check the current balance of the connected Lightning wallet (in sats). |
| pay_invoiceC | Pay a BOLT11 Lightning invoice. Returns the payment preimage on success. |
| create_invoiceB | Create a Lightning invoice to receive a payment. |
| pay_lightning_addressB | Pay a Lightning address (user@domain.com format). Resolves the address, creates an invoice, and pays it. |
| decode_invoiceB | Decode a BOLT11 invoice to inspect its amount, description, expiry, and payment hash. |
| access_l402A | Fetch a URL that may be behind an L402 (Lightning-gated) paywall. Automatically pays the invoice and retries with proof of payment. Returns the response data. |
| check_trustB | Look up the ai.wot (Web of Trust) trust score for a Nostr pubkey. Returns trust score (0-100), attestation count, and attester info. |
| discover_servicesB | Search for agent services on Nostr using decentralized service discovery. Filter by capability (e.g. "text-generation", "translation", "image-generation"). |
| resolve_lightning_addressA | Resolve a Lightning address (user@domain.com) to get LNURL metadata, min/max sendable amounts, and callback URL. |
| pay_batchB | Pay multiple Lightning invoices in parallel. Useful for distributing payments to multiple recipients. |
| pay_addressesC | Pay multiple Lightning addresses in parallel. Each payment specifies address and amount. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose: single vs batch payments, invoice vs address handling, and resolution vs payment are all separated by explicit resource and action. No two tools can be easily confused for the same task.
All tool names use snake_case and follow a verb_noun pattern (e.g., resolve_lightning_address, pay_invoice, create_invoice, check_balance). Compound nouns like lightning_address and l402 are handled consistently.
11 tools is well-scoped for a Lightning wallet plus Nostr discovery/trust consumer agent. Every tool covers a distinct operation without redundancy or trivial filler.
Core consumer workflows are covered: balance, invoice creation/decoding/payment, address resolution/payment, batch payments, L402 access, and Nostr trust/service discovery. Minor gaps exist, such as invoice status queries, transaction history, and write operations for trust attestations or service publication.