Lightning Network MCP Server

What is Lightning Network MCP Server?

Lightning Network MCP Server lets large language model (LLM) agents query Lightning node data using natural language. It implements the Model Context Protocol (MCP) specification version 2025-03-26, connects to your node via gRPC or Lightning Node Connect (LNC), and returns both readable summaries and machine-readable JSON output.

How to use Lightning Network MCP Server?

Copy .env.example to .env and configure with your LND credentials, then run npm run mcp:prod. For connections over Tor, configure SOCKS proxy settings and ensure your TLS certificate is in PEM format. Use the provided credential extraction script to convert lndconnect URLs into the required configuration files.

Key features of Lightning Network MCP Server

• Natural‑language queries for Lightning node data
• Human‑readable summaries and structured JSON output
• gRPC and Lightning Node Connect (LNC) support
• Credential extraction from lndconnect URLs
• Tor hidden service support for remote nodes
• Compatible with MCP Inspector 1.7.0 and Goose

Use cases of Lightning Network MCP Server

• Ask “Show me my channels” for a plain‑language channel list
• Query channel health and inactivity status
• Retrieve invoice and payment statistics
• Analyze routing activity over a time period

FAQ from Lightning Network MCP Server

What runtime dependencies are required?

Node.js, an LND node accessible via gRPC or LNC, and (for Tor connections) a running Tor SOCKS proxy.

How does it authenticate to my Lightning node?

Using TLS certificate and macaroon files (admin.macaroon) configured in the .env file, or via LNC credentials extracted from an lndconnect URL.

Where does my Lightning node data live?

Data remains on your own LND node; the server only queries it in real time – no data is stored or forwarded elsewhere.

What transport and security protocols are supported?

Direct gRPC (optionally over Tor SOCKS5) and LNC (Lightning Node Connect) for secure remote access.

What are the current limitations?

Only basic channel queries are fully implemented; invoices, routing, and extended node queries are under active development.