MCP server exposing your self-hosted, non-custodial Conduit Lightning instance to any MCP-compatible AI agent
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"conduit-btc-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# conduit-btc-mcp Model Context Protocol server that exposes Conduit Lightning payments as tools to any MCP-compatible AI agent (Claude Desktop, Cursor, custom agents). > Installs as the PyPI package **`conduit-btc-mcp`**; the console command it > provides is **`conduit-mcp`** (that's what you put in `claude_desktop_config.json`). Conduit is **self-hosted and non-custodial**. This MCP server connects to **your own** Conduit instance — the one you run against **your own** LND node, with **your own** keys. It is *not* a hosted Conduit service and never touches your funds. You point it at your deployment with two environment variables: - `CONDUIT_API_KEY` — an API key you minted on **your** Conduit instance. - `CONDUIT_API_URL` — the base URL of **your** instance (e.g. `https://conduit.your-domain.com`). Optional; if unset it defaults to the hosted demo at `https://api.conduit.energy`. Set it to your own URL in production. Your node, your keys, your rules. ## Install ```bash pip install conduit-btc-mcp ``` ## Configure (Claude Desktop) Add to `claude_desktop_config.json`, pointing `CONDUIT_API_URL` at **your** self-hosted Conduit instance: ```json { "mcpServers": { "conduit": { "command": "conduit-mcp", "env": { "CONDUIT_API_KEY": "ck_live_xxxxxxxxxxxx", "CONDUIT_API_URL": "https://conduit.your-domain.com" } } } } ``` ## Tools exposed Each tool requires a particular API-key **scope**. Conduit enforces these scopes server-side: a key with an insufficient scope is rejected. Mint a key with the right scope on your instance (`read` < `write` < `admin`; higher scopes include lower ones). | Tool | Purpose | Required scope | | ---- | ------- | -------------- | | `conduit_create_wallet` | Create an agent wallet with a daily limit (sats) | `admin` | | `conduit_credit` | Fund an agent wallet from operator node liquidity (sats) | `admin` | | `conduit_attach_policy` | Set spending controls: per-tx, hourly, da…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.