Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@wdk-wallet-liquid-mcp What's my L-BTC balance?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
This repository is archived. All of its tools now ship in the unified
kaleido-mcp server (0.3.0+), together with
KaleidoSwap DEX, RLN, Spark, Liquid and MPP/L402 tools. Use npx -y kaleido-mcp instead.
MCP server exposing a Liquid network wallet to AI agents, backed by
@kaleidorg/wdk-wallet-liquid (an in-process LWK
wallet). No external daemon is required.
Tool | Description |
| Network, policy asset, receive address, chain tip. |
| A confidential (CT) receive address. |
| Spendable L-BTC balance (satoshis). |
| Balance of a specific Liquid asset. |
| All assets held with balances. |
| Transaction history. |
| Wallet UTXOs. |
| Send L-BTC to a CT address. |
| Send a Liquid asset (e.g. USDt-Liquid). |
| Suggested fee rates (sat/vB). |
Related MCP server: Lightning Wallet MCP
Env var | Default | Description |
| — (required) | BIP-39 mnemonic for the wallet. |
|
|
|
| network default | Esplora API base URL. |
| — | If set, serve over StreamableHTTP instead of stdio. |
| — | Optional bearer token for HTTP mode. |
npm install
npm run build
# stdio (Claude Desktop, kaleidoagent, …)
LIQUID_MNEMONIC="word word ..." node dist/index.js
# HTTP
PORT=3013 LIQUID_MNEMONIC="word word ..." node dist/index.jsApache-2.0
Get a Liquid confidential (CT) receive address for depositing L-BTC or Liquid assets.
Inputs: no named parameters.
Get the balance of a specific Liquid asset (e.g. USDt-Liquid) by its asset id, in the asset smallest unit.
Inputs: asset_id (required).
Get the spendable L-BTC balance of the Liquid wallet, in satoshis. Syncs with the chain before returning.
Inputs: no named parameters.
Get suggested Liquid fee rates in sat/vB. Liquid fees are low and stable — the network minimum is almost always sufficient.
Inputs: no named parameters.
Get the Liquid wallet network summary: network name, policy (L-BTC) asset id, current receive address, and the chain tip height. Call this first to confirm the wallet is reachable.
Inputs: no named parameters.
List every Liquid asset held by the wallet with its satoshi balance.
Inputs: no named parameters.
List the wallet transaction history (newest first): txid, type, fee, block height and timestamp.
Inputs: no named parameters.
List the wallet unspent transaction outputs (UTXOs): txid, vout, asset id, value and confirmation height.
Inputs: no named parameters.
Send a non-L-BTC Liquid asset (e.g. USDt-Liquid) to a confidential address. Returns the broadcast txid and fee.
Inputs: amount (required), asset_id (required), recipient (required), fee_rate.
Send L-BTC on the Liquid network to a confidential address. Returns the broadcast txid and fee.
Inputs: recipient (required), amount_sats (required), fee_rate.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 10 tools
Each tool targets a distinct resource and action: network info, address generation, L-BTC balance, asset-specific balance, asset list, transaction list, UTXO list, BTC send, asset send, and fee rates. No two tools overlap in purpose, and the descriptions make the boundaries clear.
All tools share the 'liquid_' prefix and follow a consistent verb_noun pattern (get_address, get_balance, list_assets, send_btc, etc.). The verbs are limited to get, list, and send, which are unambiguous, and the naming convention is perfectly uniform.
With 10 tools, the set is well-scoped for a Liquid wallet server, covering all essential wallet operations without unnecessary bloat. Each tool has a clear role and earns its place.
The tool set covers the full wallet lifecycle: address generation, balance queries for both L-BTC and assets, transaction history, UTXO management, sending both L-BTC and other assets, and fee estimation. There are no significant gaps for typical wallet operations.
Give AI agents a Bitcoin wallet with Lightning Network payments and L402 support.
Persistent memory, hybrid search and a goal graph for AI agents, over stdio or remote HTTP.
Crypto wallet for AI agents: balances, payments, swaps and trading with owner controls.
AI Agent Utility Layer for agent safety, web monitoring, crypto research and tool discovery.