AgentBTC MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTBTC_API_KEY | No | Your owner API key for wallet management | |
| AGENTBTC_API_URL | No | AgentBTC server URL (default: http://localhost:8000) | http://localhost:8000 |
| AGENTBTC_LND_HOST | Yes | LND REST API endpoint (e.g., localhost:8080) | |
| AGENTBTC_LND_MACAROON | Yes | Path to LND macaroon file |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_agent_balanceC | Get Bitcoin balance for an agent wallet |
| list_agent_walletsB | List all agent wallets with their balances and status (agent key: own wallet only) |
| create_agent_walletA | Create a new Bitcoin wallet for an AI agent (owner access required) |
| create_lightning_invoiceC | Create a Lightning Network invoice to receive Bitcoin payments |
| pay_lightning_invoiceB | Pay a Lightning Network invoice using agent wallet funds |
| access_l402_apiC | Access an L402-protected API endpoint with automatic Lightning payment |
| get_node_infoB | Get Lightning node connection status and info |
| get_transaction_historyC | Get recent Lightning payment history |
| check_channel_balanceB | Check available Lightning channel balance (outbound and inbound liquidity) |
| delete_agent_walletB | Delete an agent wallet by name or ID (owner access required) |
| send_to_lightning_addressB | Send sats to a Lightning address (user@domain.com) using LNURL-pay protocol |
| decode_invoiceA | Decode a Lightning invoice to inspect amount, expiry, destination before paying |
| list_channelsA | List all Lightning channels with capacity, balance, and peer info |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool has a clearly distinct purpose with no overlap. For example, create_lightning_invoice is for receiving payments, pay_lightning_invoice is for sending payments, and decode_invoice is for inspection, making misselection unlikely. The separation between wallet management (create_agent_wallet, delete_agent_wallet), balance/status queries (get_agent_balance, check_channel_balance), and payment operations is well-defined.
The naming follows a consistent verb_noun pattern with snake_case throughout, such as create_lightning_invoice and get_agent_balance. There is one minor deviation: access_l402_api uses an acronym (L402) instead of a full noun, but this is understandable given the technical context and does not break the overall pattern.
With 13 tools, the count is well-scoped for a Bitcoin/Lightning server, covering key areas like wallet management, payments, and network status. Each tool earns its place by addressing specific needs in the domain, such as creating invoices, checking balances, and managing channels, without being excessive or sparse.
The tool set provides complete coverage for Bitcoin and Lightning Network operations, including CRUD for wallets (create, list, get balance, delete), payment lifecycle (create invoice, decode, pay, send via address), and network monitoring (node info, channel list, transaction history). No obvious gaps exist for core workflows in this domain.