Finance · Local MCP server
Lightning Enable MCP Server
AI agent Lightning payments: L402, invoices, wallets, API discovery, budgets, self-serve signup.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.refined-element/lightning-enable-mcp- Version
- 2.0.5
- Status
- Active
- Category
- finance
- Transport
- stdio (local process)
- Package
- NuGet, PyPI, OCI image (Docker)
- Published
- 2026-09-25
- Updated
- 2026-09-25
- Publisher
- refined-element (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/refined-element) · how
- Website
- docs.lightningenable.com/products/agentic-commerce/mcp-complete-guide
- Repository
- github.com/refined-element/lightning-enable-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| NuGetruntime: dnx | LightningEnable.Mcp | 2.0.5 | stdio |
| PyPIruntime: uvx | lightning-enable-mcp | 2.0.5 | stdio |
| OCI image (Docker)runtime: docker | docker.io/refinedelement/lightning-enable-mcp:2.0.5 | - | stdio |
How to connect Lightning Enable MCP Server
Lightning Enable MCP Server runs locally from a .NET package published to NuGet: LightningEnable.Mcp version 2.0.5. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs the .NET SDK; run as a .NET tool; the entry names dnx as the runtime. It reads these environment variables: STRIKE_API_KEY (secret), NWC_CONNECTION_STRING (secret), LND_REST_HOST, LND_MACAROON_HEX (secret), OPENNODE_API_KEY (secret), OPENNODE_ENVIRONMENT, LIGHTNING_ENABLE_API_KEY (secret), LIGHTNING_ENABLE_TOOL_PROFILE and AGENT_RELAY_URL; set them in the client's configuration for this server.
Lightning Enable MCP Server runs locally from a Python package published to PyPI: lightning-enable-mcp version 2.0.5. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx lightning-enable-mcp. It reads these environment variables: STRIKE_API_KEY (secret), NWC_CONNECTION_STRING (secret), LND_REST_HOST, LND_MACAROON_HEX (secret), OPENNODE_API_KEY (secret), LIGHTNING_ENABLE_API_KEY (secret), LIGHTNING_ENABLE_TOOL_PROFILE and AGENT_RELAY_URL; set them in the client's configuration for this server.
Lightning Enable MCP Server runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/refinedelement/lightning-enable-mcp:2.0.5. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e STRIKE_API_KEY -e NWC_CONNECTION_STRING -e LND_REST_HOST -e LND_MACAROON_HEX -e OPENNODE_API_KEY -e LIGHTNING_ENABLE_API_KEY -e LIGHTNING_ENABLE_TOOL_PROFILE -e AGENT_RELAY_URL docker.io/refinedelement/lightning-enable-mcp:2.0.5. It reads these environment variables: STRIKE_API_KEY (secret), NWC_CONNECTION_STRING (secret), LND_REST_HOST, LND_MACAROON_HEX (secret), OPENNODE_API_KEY (secret), LIGHTNING_ENABLE_API_KEY (secret), LIGHTNING_ENABLE_TOOL_PROFILE and AGENT_RELAY_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"lightning-enable-mcp": {
"command": "uvx",
"args": [
"lightning-enable-mcp"
],
"env": {
"STRIKE_API_KEY": "<secret>",
"NWC_CONNECTION_STRING": "<secret>",
"LND_REST_HOST": "<value>",
"LND_MACAROON_HEX": "<secret>",
"OPENNODE_API_KEY": "<secret>",
"LIGHTNING_ENABLE_API_KEY": "<secret>",
"LIGHTNING_ENABLE_TOOL_PROFILE": "<value>",
"AGENT_RELAY_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More finance servers
| Server | Runs |
|---|---|
| LexwareMCP server for the Lexware Office API - invoices, contacts, articles, and vouchers. | Local · stdio |
| License Verify MCPVerify US contractor license + surety bond + insurance from official state data. WA live, CA beta. | Local · stdio |
| life. scored.Rebuilds the scores real systems run on you - credit, actuarial, lending - in the open, cited. | Remote · HTTPLive check: ✓ handshake |
| Light Horse SecuritiesAgentic brokerage access to a US brokerage account: quotes, orders, positions, cash and documents. | Remote · HTTPLive check: sign-in required |
| Lightning MemoryDecentralized agent memory for the Lightning economy. Nostr identity, L402 payments. | Local · stdio |
| Lightning WalletGive AI agents a Bitcoin wallet with Lightning Network payments and L402 support. | Local · stdio |
| lightningfaucet MCP-SERVERGive AI agents a Bitcoin wallet with Lightning Network payments and L402 support. | Local · stdio |
| LimurseFind, vet and budget bookable influencers, photographers and videographers for brand campaigns. | Remote · HTTPLive check: sign-in required |