Lightning Network MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Lightning Network MCP Server?

The Lightning Network MCP Server allows large language model (LLM) agents to query Lightning node data using natural language, implementing the Model Context Protocol (MCP) specification.

How to use Lightning Network MCP Server?

To use the server, connect it to your Lightning node using gRPC or Lightning Node Connect (LNC) and send natural language queries to retrieve data in both human-readable and structured JSON formats.

Key features of Lightning Network MCP Server?

  • Natural language processing for querying Lightning node data.
  • Returns both readable summaries and machine-readable JSON output.
  • Modular and extensible design to support various node types.

Use cases of Lightning Network MCP Server?

  1. Querying channel status and health.
  2. Retrieving invoice information.
  3. Analyzing routing data for transactions.

FAQ from Lightning Network MCP Server?

  • Can I connect to my node over Tor?

Yes, the server supports connections to LND nodes running as Tor hidden services.

  • What types of queries can I make?

You can ask about channels, invoices, nodes, and routing data using natural language.

  • Is the server compatible with other MCP agents?

Yes, it is compatible with MCP Inspector and other agents that follow the MCP specification.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago