LnExchange MCP Node Service

You are about to run an MCP Server that connects to the LnExchange API to enable spot trading capabilities. This server acts as a bridge between your client applications and LnExchange, handling authentication, command routing, and data exchange so you can build reliable trading workflows.

How to use

You will run the MCP server locally and connect to it through an MCP client. The server exposes a stdio-based runtime that you launch with a command line, typically via an npx invocation that injects your private key. When you configure the MCP, you provide the key placeholder in place of your actual value. Once running, your client can request trading actions and data from LnExchange through the MCP interface.

How to install

Prerequisites: make sure you have Node.js installed (version 16 or higher recommended). You also need git to clone the project.

Step 1: Clone the project repository.

Step 2: Install dependencies.

Step 3: Build the project to compile TypeScript files to JavaScript.

Step 4: Start the service.

# Step 1
git clone <repository>
cd lnexchange-mcp-node-service

# Step 2
npm install

# Step 3
npm run build

# Step 4
npm start

Additional steps and configuration

Configure the MCP connection using the stdio command shown in the example. You will typically use npx to run the MCP package with your private key. The following configuration snippet demonstrates the required shape and values you will provide when you set up the MCP client.

{
  "mcpServers": {
    "lnexchange_mcp_node_test": {
      "command": "npx",
      "args": [
        "-y",
        "lnexchange-mcp-node-service-test",
        "xxxxxxxxxxxxxxxxxxxx"
      ]
    }
  }
}

Notes on configuration, security, and troubleshooting

You will replace the placeholder xxxxxxxxxxxxxxxxxxxx with your actual Nostr private key. Handle this key securely and avoid exposing it in logs or shared files.

Dependencies shown include the LnExchange API client, Zod for schema validation, and the Model Context Protocol SDK, which the server relies on for data integrity and type safety.