Magma MCP
MCP server for buying Lightning Network liquidity via Amboss Magma. Enables AI assistants to purchase inbound Lightning liquidity for a node.
README
Magma MCP
Node.js client library and Model Context Protocol (MCP) server for buying Lightning Network liquidity via Amboss Magma.
Overview
This package provides two ways to interact with the Amboss Magma API:
- Node.js Client Library: Programmatically buy Lightning liquidity from your Node.js applications
- MCP Server: Enable AI assistants like Claude to purchase inbound Lightning Network liquidity for your node
Both interfaces provide a seamless way to increase your node's receiving capacity through the Amboss Magma API.
Features
- Buy Lightning Liquidity: Purchase inbound liquidity for your Lightning node
- Anonymous Access: Works without an API key - the Magma API creates temporary accounts automatically
- Optional Authentication: Use your Amboss account API key for personalized access
- Input Validation: Comprehensive validation of all parameters
- Error Handling: Clear, user-friendly error messages
- Retry Logic: Automatic retry for transient network failures
Prerequisites
- Node.js >= 18.0.0
- pnpm (or npm/yarn)
- A Lightning Network node with accessible connection URI
- (Optional) Amboss Magma API key (Get one here)
Installation
From npm (Recommended)
npm install -g @ambosstech/magma-mcp
Or with pnpm:
pnpm add -g @ambosstech/magma-mcp
From source
git clone https://github.com/AmbossTech/magma-mcp.git
cd magma-mcp
pnpm install
pnpm build
Configure environment variables (Optional)
The Magma API supports anonymous access - you can use the server without an API key! The API will automatically create temporary accounts with session keys.
If you want to use your existing Amboss account, create a .env file:
cp .env.example .env
Edit .env and add your Magma API key:
MAGMA_API_KEY=your_api_key_here
Configuration
Environment Variables
| Variable | Required | Default | Description |
|---|---|---|---|
MAGMA_API_KEY |
No | - | Your Amboss Magma API key (optional - supports anonymous access) |
MAGMA_GRAPHQL_ENDPOINT |
No | https://magma.amboss.tech/graphql |
Magma GraphQL endpoint |
LOG_LEVEL |
No | info |
Logging level (debug, info, warn, error) |
Claude Desktop Integration
Add the following configuration to your Claude Desktop config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Option 1: Using npm package (anonymous access)
{
"mcpServers": {
"magma": {
"command": "npx",
"args": ["-y", "@ambosstech/magma-mcp"]
}
}
}
Option 2: Using npm package (with API key)
{
"mcpServers": {
"magma": {
"command": "npx",
"args": ["-y", "@ambosstech/magma-mcp"],
"env": {
"MAGMA_API_KEY": "your_api_key_here"
}
}
}
}
Option 3: From source (development)
{
"mcpServers": {
"magma": {
"command": "node",
"args": ["/absolute/path/to/magma-mcp/dist/server.js"],
"env": {
"MAGMA_API_KEY": "your_api_key_here"
}
}
}
}
After adding the configuration:
- Save the file
- Restart Claude Desktop
- The Magma MCP server will be available
Usage
Once configured, you can use natural language with Claude to buy Lightning liquidity:
Example Prompts
Basic purchase:
Buy $10 of Lightning liquidity for my node at 024ae5a5f0b0185...@12.34.56.78:9735
With options:
Buy $50 of Lightning liquidity for 024ae5a5f0b0185...@12.34.56.78:9735
using only Rails cluster nodes
Private channel:
Buy $25 of private channel liquidity for my node 024ae5a5f0b0185...@12.34.56.78:9735
Tool: buy_lightning_liquidity
Parameters:
connection_uri(required): Your node's connection string (either just pubkey or pubkey@host:port)- Just pubkey:
024ae5a5f0b01850983009489ca89c85... - With socket:
024ae5a5f0b01850983009489ca89c85...@12.34.56.78:9735
- Just pubkey:
usd_cents(required): Dollar amount in cents (minimum 500 = $5.00)redirect_url(optional): URL to redirect after paymentprivate_channel(optional): Create private channel (default: false)rails_cluster_only(optional): Source only from Rails cluster (default: false)
Returns:
{
"success": true,
"lightning_invoice": "lnbc10m1p3j8z9xpp5qqqsyqcyq5rqwzqfqqqsyqcyq5rqwzqfqqqsyqcyq5rqwzqfqypq..."
}
The Lightning invoice can be paid using any Lightning wallet to complete the liquidity purchase.
Using as a Node.js Library
In addition to the MCP server, this package can be used as a Node.js client library to programmatically interact with the Amboss Magma API.
Installation
npm install @ambosstech/magma-mcp
Quick Start
import { MagmaClient } from '@ambosstech/magma-mcp';
// Create client (anonymous access)
const client = new MagmaClient();
// Or with API key
const client = new MagmaClient({
apiKey: process.env.MAGMA_API_KEY
});
// Buy liquidity
const invoice = await client.buyLiquidity({
connectionUri: '024ae5a5f0b01850983009489ca89c85...@12.34.56.78:9735',
usdCents: 1000 // $10.00
});
console.log('Pay this Lightning invoice:', invoice);
API Reference
MagmaClient
Constructor:
new MagmaClient(config?: MagmaClientConfig)
Config options:
apiKey?: string- Your Amboss Magma API key (optional, supports anonymous access)endpoint?: string- GraphQL endpoint (default:https://magma.amboss.tech/graphql)logLevel?: 'debug' | 'info' | 'error'- Logging level (default:error)
Methods:
buyLiquidity(options: BuyLiquidityOptions): Promise<string>
Purchase inbound Lightning Network liquidity for a node.
Options:
connectionUri: string- Node connection string (pubkey or pubkey@host:port)usdCents: number- Amount in cents (minimum 500 = $5.00)redirectUrl?: string- Optional post-payment redirect URLprivateChannel?: boolean- Create private channel (default: false)railsClusterOnly?: boolean- Source only from Rails cluster (default: false)
Returns: Lightning invoice string to complete the payment
Throws: MagmaClientError on API or network errors
Examples
Basic purchase:
import { MagmaClient } from '@ambosstech/magma-mcp';
const client = new MagmaClient();
const invoice = await client.buyLiquidity({
connectionUri: '024ae5a5f0b01850983009489ca89c85...',
usdCents: 500 // $5.00 minimum
});
console.log('Invoice:', invoice);
With all options:
const invoice = await client.buyLiquidity({
connectionUri: '024ae5a5f0b01850983009489ca89c85...@12.34.56.78:9735',
usdCents: 5000, // $50.00
redirectUrl: 'https://myapp.com/payment-complete',
privateChannel: true,
railsClusterOnly: true
});
Error handling:
import { MagmaClient, ErrorCategory } from '@ambosstech/magma-mcp';
const client = new MagmaClient();
try {
const invoice = await client.buyLiquidity({
connectionUri: '024ae5a5f0b01850983009489ca89c85...',
usdCents: 1000
});
console.log('Success:', invoice);
} catch (error) {
if (error.category === ErrorCategory.NETWORK_ERROR) {
console.error('Network issue, please retry');
} else if (error.category === ErrorCategory.CLIENT_ERROR) {
console.error('Invalid request:', error.message);
} else {
console.error('Unexpected error:', error);
}
}
TypeScript types:
import type {
MagmaClientConfig,
BuyLiquidityOptions,
LiquidityOrderInput,
BuyLiquidityResponse
} from '@ambosstech/magma-mcp';
Advanced Usage
For advanced use cases, you can access the low-level GraphQL client:
import { MagmaGraphQLClient } from '@ambosstech/magma-mcp';
const client = new MagmaGraphQLClient({
magmaApiKey: 'your-api-key',
magmaEndpoint: 'https://magma.amboss.tech/graphql',
logLevel: 'debug'
});
const response = await client.buyLiquidity({
connection_uri: '024ae5a5f0b01850983009489ca89c85...',
usd_cents: '1000',
options: {
private: true
}
});
// Full response structure
console.log(response.liquidity.buy.payment.lightning_invoice);
Development
Run in development mode
pnpm dev
Build
pnpm build
Type checking
pnpm typecheck
Test with MCP Inspector
The MCP Inspector is a great tool for testing your server:
pnpm inspector
This will open a web interface where you can:
- View available tools
- Test tool execution
- Inspect requests and responses
- Debug errors
Testing
Manual Testing with Claude Desktop
- Configure Claude Desktop with the MCP server
- Restart Claude Desktop
- Ask Claude to buy Lightning liquidity
- Verify the response includes a Lightning invoice
Example Test Conversation
You: Can you buy $5 of Lightning liquidity for my node?
Claude: I'll help you buy Lightning liquidity. I need your node's connection URI in the format pubkey@host:port.
You: 024ae5a5f0b01850983009489ca89c85...@12.34.56.78:9735
Claude: [Executes buy_lightning_liquidity tool]
Claude: Successfully created liquidity order! Transaction ID: abc123...
Here's your Lightning invoice: lnbc...
Payment URL: https://checkout.btcpay.amboss.tech/...
Troubleshooting
Server won't start
Check environment variables:
node -e "require('dotenv').config(); console.log(process.env.MAGMA_API_KEY)"
Check build output:
ls -la dist/
Authentication errors
Error: Authentication failed. Please check your MAGMA_API_KEY.
Solution:
- If using an API key, verify it at https://account.amboss.tech/settings/api-keys
- Ensure the key is correctly set in your
.envfile or Claude config - Check for extra spaces or quotes around the API key
- Alternatively, remove the API key to use anonymous access (the API will create a temporary account automatically)
Connection URI validation errors
Error: Connection URI must be either a 66-character pubkey or pubkey@host:port format
Solution:
- Ensure pubkey is exactly 66 hexadecimal characters
- Accepted formats:
- Just pubkey:
024ae5a5f0b01850983009489ca89c85...(no spaces) - With socket:
pubkey@host:port(e.g.,024ae5...@12.34.56.78:9735)
- Just pubkey:
- If using socket format, port must be between 1-65535
Minimum purchase amount error
Error: Minimum purchase amount is $5.00 (500 cents)
Solution: Use at least 500 cents ($5.00) for the usd_cents parameter.
Project Structure
magma-mcp/
├── src/
│ ├── index.ts # Main MCP server entry point
│ ├── config.ts # Configuration with validation
│ ├── lib/
│ │ ├── graphql-client.ts # Magma API client
│ │ ├── tools/
│ │ │ └── buy-liquidity.ts # Buy liquidity tool handler
│ │ └── schemas/
│ │ ├── common-schemas.ts # Shared validation schemas
│ │ └── buy-liquidity-schema.ts # Buy tool schema
│ └── types/
│ └── magma.ts # TypeScript types
├── dist/ # Compiled JavaScript (generated)
├── package.json
├── tsconfig.json
└── README.md
Security
- API keys are never logged - All logging goes to stderr and keys are sanitized
- Environment-based configuration - API keys stored in
.envor MCP config - Input validation - All inputs are validated before processing
- Error sanitization - Errors never expose sensitive information
Contributing
Contributions are welcome! Please:
- Fork the repository
- Create a feature branch
- Make your changes
- Add tests if applicable
- Submit a pull request
License
MIT License - see LICENSE file for details.
Links
Support
- Issues: GitHub Issues
- Documentation: Amboss Docs
Made with ⚡ by Amboss Technologies
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.