bsl-agent-mcp
OfficialAllows an AI agent to operate a Bitcoin wallet on the Bitcoin-IPC testnet: deposit L1 BTC, pay wBTC within or across subnets, and fetch Bitcoin-anchored payment receipts with block height and txid.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
bsl-agent-mcp
MCP server that lets an AI agent (Claude Desktop, Claude Code, or any MCP
client) operate a user-owned wallet on the Bitcoin-IPC testnet: deposit L1 BTC
into subnet1, pay wBTC within subnet1 or across to subnet2, and fetch the
Bitcoin-anchored receipt for any payment. The agent never holds keys — it can
only request operations; the server signs locally and refuses any deposit or
payment above SPEND_CAP_SATS until the user explicitly approves it
(confirmed=true).
Disclaimer: this code is not audited and is meant for testnet use only. Do not use it with mainnet funds or keys that control real value.
Tools
Tool | What it does |
| L1 BTC balance + wBTC balances on subnet1/subnet2 + spending cap |
| L1 BTC → wBTC at the agent's address on subnet1 |
| wBTC to an address-book payee or user-supplied address; same-subnet (seconds) or subnet1→subnet2 (next checkpoint) |
| Known payees with address, subnet, and live wBTC balance |
| wBTC balance of any account (payee or raw address) on both subnets |
| The checkpoint anchoring a payment: Bitcoin block height + txid |
| Committee, threshold, multisig address, latest checkpoint of a subnet |
Related MCP server: aibtc-mcp-server
Requirements
A running bsl-client container — the public image is
ghcr.io/bitcoinscalinglabs/bsl-client:testnet — with its bsl.env
configuration file, which must also contain AGENT_PRIVATE_KEY (the EVM key
the server pays from).
Run with Docker
The image runs next to bsl-client and shares its network; the entrypoint
generates the ipc-cli config, imports AGENT_PRIVATE_KEY, runs connectivity
checks, and idles.
docker build -t ghcr.io/bitcoinscalinglabs/bsl-agent-mcp:testnet .
docker run -d --env-file ./bsl.env \
--network container:bsl-client \
--name bsl-agent-mcp \
ghcr.io/bitcoinscalinglabs/bsl-agent-mcp:testnet
docker logs bsl-agent-mcp # should end with "bsl-agent-mcp ready"Claude Desktop attaches MCP sessions to the standing container:
{
"mcpServers": {
"bsl-payments": {
"command": "docker",
"args": ["exec", "-i", "bsl-agent-mcp", "node", "/app/dist/index.js"]
}
}
}Run from source (development)
Node.js ≥ 20. The bsl-client container must publish the provider port
(-p 127.0.0.1:3030:3030) and have the agent key imported once:
docker exec bsl-client ipc-cli wallet import --wallet-type evm --private-key <key>
npm install && npm run build
cp .env.example .env # fill inClaude Desktop config: "command": "node",
"args": ["/ABS/PATH/bsl-agent-mcp/dist/index.js"]. Configuration comes from
the repo's .env; an env block in the Desktop config takes precedence.
Configuration
Var | Required | Meaning |
| yes | Access key for the L2 gateways and the bsl-client provider |
| yes | EVM key the server pays from (holds wBTC) |
| yes | Subnet ids ( |
| no | Gateway RPC endpoints (default: BSL testnet gateways) |
| no | bsl-client provider (default |
| no | Container name for |
| no | Per-operation cap; above it, user approval required (default 500000) |
Notes
Amounts are satoshis everywhere (1 BTC = 100,000,000 sats); wBTC has 18 decimals and the server converts internally.
Recipients are either payees from the built-in address book or addresses supplied by the user; the agent is instructed never to invent an address.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Bitcoin MCP for fee budgets, transaction proofs and address checks. Free service discovery.
MCP server for Boson Protocol — on-chain agentic commerce for physical & digital goods.
MCP server for the Z1N Protocol - on-chain identity for AI agents on Polygon
Testnet wallet for AI agents on Aether: pay, get paid and buy from paid APIs, with spending caps.
Related MCP Servers
- AlicenseBqualityBmaintenanceMCP server for managing Bitcoin, Liquid Network, and Lightning wallets through AI assistants, with unified seed support, secure encrypted storage, and both CLI and tool interfaces.736MIT

aibtc-mcp-serverofficial
AlicenseCqualityBmaintenanceA Bitcoin-native MCP server for AI agents that provides 150+ tools for BTC and Stacks operations. Supports wallets, DeFi yield, sBTC peg, NFTs, and x402 payments.3871,554 npm12MIT- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage Bitcoin micropayments, service offers, and escrow contracts through MCP tools, without requiring a Lightning node.7 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to send and receive Bitcoin over the Lightning Network using NWC or LND backends.MIT