MCP Server for Bitcoin Lightning

Created By
ehallmarka year ago
Overview

what is MCP Server for Bitcoin Lightning?

The MCP Server for Bitcoin Lightning is a server that facilitates communication with a local Lightning Network Daemon (lnd) using the Model Context Protocol (MCP). It allows Agentic systems to interact with the Lightning Network seamlessly.

how to use MCP Server for Bitcoin Lightning?

To use the MCP Server, ensure you have Python 3.10 or higher and a running instance of the Lightning Network Daemon (lnd). Set the necessary environment variables and run the server using the provided command.

key features of MCP Server for Bitcoin Lightning?

  • Integrates with the Lightning Network for efficient transactions.
  • Utilizes Model Context Protocol (MCP) for communication.
  • Supports Server-Sent Events (SSE) for real-time data transport.

use cases of MCP Server for Bitcoin Lightning?

  1. Enabling real-time interactions with the Lightning Network.
  2. Facilitating transactions in decentralized applications.
  3. Integrating with Agentic systems for enhanced functionality.

FAQ from MCP Server for Bitcoin Lightning?

  • What are the prerequisites for running the MCP Server?

You need Python >= 3.10 and a running instance of the Lightning Network Daemon (lnd).

  • How do I connect to the MCP Server?

You can connect using the LangGraph framework with the provided adapter code.

  • Is there any license for the MCP Server?

Yes, it is licensed under the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ehallmark
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Alloy

2 days ago
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)

8 hours ago
Crevio

a day ago