How do I install Bolthub?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Bolthub need an API key?

The publisher lists these environment variables: LND_REST_HOST, LND_MACAROON, NWC_URI, LNBITS_URL, LNBITS_ADMIN_KEY, PHOENIXD_URL, PHOENIXD_PASSWORD, BUDGET_SATS, BOLTHUB_ACCOUNT_TOKEN.

What transport does Bolthub use?

Bolthub runs locally over stdio.

When was Bolthub last checked?

Last checked 2026-11-07. The bolthub API marketplace, L402 gateways, and your other MCP servers, on one Lightning budget.

Bolthub MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y @bolthub/[email protected]

Credentials from the publisher

LND_REST_HOST — LND REST API URL (recommended wallet; pair with LND_MACAROON). A wallet is optional — without one, free tools and marketplace search still work; paid calls return their payment challenge.
LND_MACAROON — Hex-encoded macaroon for LND (use a pay-scoped macaroon in production). Required with LND_REST_HOST.
NWC_URI — Nostr Wallet Connect string — easiest setup, works with CoinOS, Alby Hub, Zeus, and more. Alternative to LND.
LNBITS_URL — LNbits instance URL (pair with LNBITS_ADMIN_KEY). Alternative wallet.
LNBITS_ADMIN_KEY — Admin API key for LNbits. Required with LNBITS_URL.
PHOENIXD_URL — Phoenixd HTTP API URL (pair with PHOENIXD_PASSWORD). Alternative wallet.
PHOENIXD_PASSWORD — HTTP password for Phoenixd. Required with PHOENIXD_URL.
BUDGET_SATS — Maximum sats the server may spend per session (process lifetime), across ALL sources. Unset = unlimited; 0 = free tools only. The config file's budget.sat takes precedence.
BOLTHUB_ACCOUNT_TOKEN — Account token for tools that act on YOUR bolthub account (workspace, listing, audit, earnings, and node tools). Optional even for those: the connect_account tool pairs via the browser instead. Never needed to discover, call, or pay for APIs — buying is account-less.

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1LND_REST_HOST=<value> LND_MACAROON=<secret> NWC_URI=<secret> LNBITS_URL=<value> LNBITS_ADMIN_KEY=<secret> PHOENIXD_URL=<value> PHOENIXD_PASSWORD=<secret> BUDGET_SATS=<value> BOLTHUB_ACCOUNT_TOKEN=<secret> claude mcp add ai.bolthub-mcp -- npx -y @bolthub/mcp@0.7.2

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "ai.bolthub-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "@bolthub/[email protected]"8      ],9      "env": {10        "LND_REST_HOST": "<value>",11        "LND_MACAROON": "<secret>",12        "NWC_URI": "<secret>",13        "LNBITS_URL": "<value>",14        "LNBITS_ADMIN_KEY": "<secret>",15        "PHOENIXD_URL": "<value>",16        "PHOENIXD_PASSWORD": "<secret>",17        "BUDGET_SATS": "<value>",18        "BOLTHUB_ACCOUNT_TOKEN": "<secret>"19      }20    }21  }22}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

bolthub SDK

Source code for every publicly published bolthub.ai package: the npm @bolthub/* scope and the bolthub / bolthub-verify PyPI packages.

bolthub is a payment layer for agent-to-tool commerce: charge agents for your MCP tools and APIs per call, settling straight to your wallet over Lightning (L402), with bolthub never in the funds path. These packages are the open-source side of that: the tool-payment SDK, payment clients, MCP servers, a CLI, and origin-verification middleware.

Package	Registry	Directory	What it is
`@bolthub/pay`	npm	`packages/pay`	The payments SDK, both sides: price an MCP tool or HTTP endpoint (`createPaywall`), pay for tools within a budget (`ToolClient` for MCP, `L402Client` for HTTP), wallet adapters (LND, LNbits, Phoenixd, NWC, WebLN); rails: L402, facilitator. Zero runtime dependencies
`@bolthub/mcp`	npm	`packages/mcp`	The bolthub MCP server: marketplace + specific gateways + your other MCP servers behind one config entry, with one shared Lightning budget
`@bolthub/cli`	npm	`packages/cli`	Terminal client for the marketplace
`@bolthub/verify`	npm	`packages/verify`	Gateway signature verification middleware (Express/Fastify/Node)
`bolthub`	PyPI	`packages/agent-python`	The payments SDK in Python: L402 client + wallets, and the seller-side paywall
`bolthub-verify`	PyPI	`packages/verify-python`	Python gateway signature verification (Flask/Django/FastAPI)

packages/shared is internal (never published); it is here because @bolthub/mcp bundles it.

Consolidation (2026-07): @bolthub/agent merged into @bolthub/pay (≥0.4.0); @bolthub/mcp-registry and @bolthub/mcp-bridge merged into @bolthub/mcp. The old names are deprecated on npm and point here.

Relationship to the bolthub platform

The bolthub platform (gateway, API, web app) lives in a private monorepo. The SDK packages above are developed there and synced to this repository, which is the publish origin: releases are tagged here and built + published by CI with npm provenance, so what's on npm is verifiably built from this public source.

Issues and PRs are welcome here, but note that this repo is a generated mirror: PRs are never merged directly. Accepted changes are applied to the monorepo first (with attribution), then sync back out with the next release. See CONTRIBUTING.md before opening a PR.

Verifying what you install

Published dist/ bundles are built with Bun from this source and ship source maps with embedded sources, so the tarball itself is readable.

# provenance: confirm the tarball was built from this repo by GitHub Actions
npm audit signatures

# or rebuild and compare yourself
git clone https://github.com/signaltech-org/bolthub-sdk
cd bolthub-sdk && bun install
cd packages/mcp && bun run build

See SECURITY.md for the trust model (what touches your wallet credentials and what doesn't) and how to report vulnerabilities.

Development

bun install
bun test

Each TypeScript package builds with bun run build from its directory (@bolthub/pay must be built before the packages that bundle it).

License

MIT

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Bolthub?

Does Bolthub need an API key?

What transport does Bolthub use?

When was Bolthub last checked?

Documentation

bolthub SDK

Relationship to the bolthub platform

Verifying what you install

Development

License