CLN MCP Server

CLN MCP MCP server exists for a simple reason — assistants are far more useful when they can act on CLN MCP directly instead of describing what you should do. A Rust-based gRPC server that provides a standardized interface to Core Lightning nodes. This server implements the MCP (Model Context Protocol) specification to enable control of the Core Lightning node using LLM.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What the assistant can call

Once CLN MCP is connected, these are the calls the assistant has available:

• ca.pem — CA certificate
• client.pem — Client certificate
• client-key.pem — Client private key

Configuration and credentials

• Rust 1.80 or higher - Protocol Buffers Compiler (protoc) - Core Lightning (with gRPC enabled) - MCP clients (Claude, Goose, etc.)

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the cln mcp mcp server does with a few real requests.

Choosing this one

Among the AI and media services options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. CLN MCP's toolset — ca.pem, client.pem, client-key.pem — is a fair guide to whether it matches your workflow. It is maintained by adi2011; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.