Lightning Enable MCP Server

What the code does

We read the source, 3 d ago · rules 995398eba69f

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

            lowered in ("localhost", "metadata", "metadata.google.internal", "metadata.goog", "metadata.azure.com")

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

        result = subprocess.run(

ENV OPENNODE_API_KEY=""

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

            using var p = System.Diagnostics.Process.Start(psi);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add lightning-enable-mcp -- uvx lightning-enable-mcp

{
  "mcpServers": {
    "lightning-enable-mcp": {
      "command": "uvx",
      "args": [
        "lightning-enable-mcp"
      ]
    }
  }
}

[mcp_servers.lightning-enable-mcp]
command = "uvx"
args = ["lightning-enable-mcp"]

{
  "mcpServers": {
    "lightning-enable-mcp": {
      "command": "uvx",
      "args": [
        "lightning-enable-mcp"
      ]
    }
  }
}

{
  "servers": {
    "lightning-enable-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "lightning-enable-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: STRIKE_API_KEY (Strike API key for Lightning payments (recommended wallet)), NWC_CONNECTION_STRING (Nostr Wallet Connect URI (for NWC wallets like CoinOS, CLINK, Alby Hub)), LND_REST_HOST (LND REST API host (e.g., localhost:8080)), LND_MACAROON_HEX (LND admin macaroon in hex format), OPENNODE_API_KEY (OpenNode API key (direct payments only, no L402 support)), LIGHTNING_ENABLE_API_KEY (Lightning Enable API key (unlocks producer + ASA tools). Optional: no key? The create_lightning_enable_account tool self-provisions one for ~100 sats over Lightning — no card, no subscription required), LIGHTNING_ENABLE_TOOL_PROFILE (How many tools to advertise: lite (the wallet-setup and spend/read basics), standard (default), or full (adds the deprecated legacy names), or full (adds the pre-consolidation tool names)), AGENT_RELAY_URL (Nostr relay URL for agent events (default: wss://agents.lightningenable.com)).