Lightning Tools MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| request_invoiceC | Request an invoice from a lightning address |
| fiat_to_satsB | Convert fiat amounts to sats |
| parse_invoiceC | Parse a BOLT-11 lightning invoice |
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 3 tools
Each tool has a clearly distinct purpose with no overlap: fiat_to_sats handles currency conversion, parse_invoice processes existing invoices, and request_invoice generates new invoices from lightning addresses. An agent can easily distinguish these functions without confusion.
All tool names follow a consistent snake_case pattern with clear verb_noun structures (e.g., parse_invoice, request_invoice). The naming is uniform and predictable across the set.
With only 3 tools, the server feels thin for a Lightning domain, as it lacks operations like sending payments, checking balances, or managing channels. However, the tools are well-scoped for basic invoice and conversion tasks, making it borderline but not severely lacking.
The tool surface is significantly incomplete for Lightning functionality; it covers invoice parsing/requesting and fiat conversion but misses core operations like pay_invoice, get_balance, list_transactions, or channel management. This will likely cause agent failures in broader workflows.