Phoenixd MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_HOST | No | Host of the phoenixd server | 127.0.0.1 |
| HTTP_PORT | No | Port of the phoenixd server | 9740 |
| HTTP_PASSWORD | Yes | Password from phoenix.conf for authentication | |
| HTTP_PROTOCOL | No | Protocol to use (http or https) | http |
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 |
|---|---|
| get-balanceA | Get the balance of the node |
| get-node-infoB | Get the node info |
| list-channelsB | List the node channels |
| close-channelB | Close a channel by ID, sending the funds to a specified address on chain, with a specified fee rate |
| decode-invoiceB | Decode an bolt11 invoice, the output amount is in milisatoshis |
| decode-offerC | Decode an bolt12 offer the output amount is in milisatoshis |
| create-invoiceC | Create a bolt11 invoice with a specified amount and description |
| pay-invoiceC | Pay a bolt11 invoice with a specified amount and description |
| create-offerB | Create a bolt12 offer with an optional description and amount |
| pay-offerC | Pay a bolt12 offer |
| pay-lightning-addressB | Pays an email-like Lightning address, either based on BIP-353 or LNURL |
| pay-on-chainB | Pay an on-chain address with a specified amount and fee rate |
| bump-feeA | Makes all your unconfirmed transactions use a higher fee rate, using CPFP. Returns the ID of the child transaction |
| list-incoming-paymentsC | List the incoming payments |
| get-incoming-paymentC | Get the incoming payment by payment hash |
| list-outgoing-paymentsB | List the outgoing payments |
| get-outgoing-paymentB | Get the outgoing payment by payment id |
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 17 tools
All 17 tools have clearly distinct purposes, targeting different Lightning operations like invoices, offers, payments (by various methods), channels, balance, and node info. No overlap or ambiguity.
Tool names consistently follow a verb-noun pattern with lowercase and hyphens (e.g., create-invoice, pay-on-chain, get-balance). No mixing of conventions or irregular variations.
17 tools is appropriate for a Lightning node management server, covering invoices, payments, channels, balance, and node info without being excessive or insufficient.
The tool set covers most core operations for node management and payments, but notably lacks a tool to open channels, which is a fundamental operation for a Lightning node, leaving a meaningful gap.