bolthub Marketplace
VerifiedMCP server exposing the bolthub marketplace for Lightning-paid API calls.
What is the bolthub Marketplace MCP server?
Built from the bolthub-sdk repository, this stdio MCP server surfaces the entire marketplace catalog so agents can find, pay for, and call third-party endpoints on a per-use basis over Lightning.
It supports multiple wallet backends through environment variables and works alongside companion packages such as @bolthub/agent for payment handling and origin verification.
Install & connect
Add this to your MCP client config. Pick your client below and copy.
{
"mcpServers": {
"registry": {
"command": "npx",
"args": [
"-y",
"@bolthub/mcp-registry"
],
"env": {
"LND_REST_HOST": "<LND_REST_HOST>",
"LND_MACAROON": "<YOUR_LND_MACAROON>",
"NWC_URI": "<YOUR_NWC_URI>",
"LNBITS_URL": "<LNBITS_URL>",
"LNBITS_ADMIN_KEY": "<YOUR_LNBITS_ADMIN_KEY>",
"PHOENIXD_URL": "<PHOENIXD_URL>",
"PHOENIXD_PASSWORD": "<YOUR_PHOENIXD_PASSWORD>",
"BUDGET_SATS": "<BUDGET_SATS>",
"BOLTHUB_AUTH_TOKEN": "<YOUR_BOLTHUB_AUTH_TOKEN>"
}
}
}
}Package: @bolthub/mcp-registry (npm)
Example prompts
Once connected, try asking your AI client:
Configuration
Environment variables this server needs.
| Variable | Required | Description |
|---|---|---|
LND_REST_HOST | No | LND REST API URL (recommended wallet; pair with LND_MACAROON). One wallet config is required. |
LND_MACAROONsecret | No | Hex-encoded macaroon for LND (use a pay-scoped macaroon in production). Required with LND_REST_HOST. |
NWC_URIsecret | No | Nostr Wallet Connect string — easiest setup, works with CoinOS, Alby Hub, Zeus, and more. Alternative to LND. |
LNBITS_URL | No | LNbits instance URL (pair with LNBITS_ADMIN_KEY). Alternative wallet. |
LNBITS_ADMIN_KEYsecret | No | Admin API key for LNbits. Required with LNBITS_URL. |
PHOENIXD_URL | No | Phoenixd HTTP API URL (pair with PHOENIXD_PASSWORD). Alternative wallet. |
PHOENIXD_PASSWORDsecret | No | HTTP password for Phoenixd. Required with PHOENIXD_URL. |
BUDGET_SATS | No | Maximum sats the server may spend per session (process lifetime). Unset = unlimited. |
BOLTHUB_AUTH_TOKENsecret | No | Optional bolthub API token, used only by the deploy_node / node_status Node Launcher tools. |
Security & permissions
Runs locally via stdio and requires wallet credentials (LND_REST_HOST, LND_MACAROON, NWC_URI, LNBITS_URL, LNBITS_ADMIN_KEY, PHOENIXD_URL, PHOENIXD_PASSWORD) plus BOLTHUB_AUTH_TOKEN and a spending budget in BUDGET_SATS.
What you can do with bolthub Marketplace
API discovery
List every paid endpoint available on bolthub so an agent can choose the right service without prior knowledge.
Automated payments
Execute calls to premium APIs while the server manages L402 challenges and Lightning settlement using the configured wallet.
Agent integration
Give coding or research agents on-demand access to paid data sources without manual billing or API-key management.
How to use bolthub Marketplace
- 1Install the @bolthub/mcp-registry package from npm.
- 2Set the required Lightning wallet and BOLTHUB_AUTH_TOKEN environment variables.
- 3Configure the MCP client to launch the server binary over stdio.
- 4Ask the agent to list or invoke marketplace endpoints.
- 5Monitor wallet balance and session cache for payment activity.
bolthub Marketplace: pros & cons
Pros
- +Gives agents unified access to many paid APIs through a single MCP interface.
- +Handles Lightning micropayments automatically without exposing keys to the model.
- +Supports multiple popular Lightning backends via environment configuration.
- +Open-source with verifiable provenance builds.
Cons
- –No tool schemas are publicly documented, limiting static inspection.
- –Requires live Lightning wallet funding and correct credential setup.
- –All usage incurs real per-call Lightning costs.
Frequently asked questions
It supports LND, LNbits, Phoenixd, NWC, and WebLN through the listed environment variables.
User reviews
Verified reviews from the community shape this listing's rating.
Loading reviews…