AgenticBTC MCP
The AgenticBTC MCP server lets AI agents manage Bitcoin payments and Lightning Network interactions under owner-controlled policies. It supports:
Agent wallet management: create, list, retrieve balances, and delete agent-specific Bitcoin wallets.
Lightning Network payments: create/pay invoices, send payments to Lightning addresses, and access L402-protected API endpoints.
Lightning Network information: get node info, check channel balances, list channels, and view transaction history.
Onboarding & setup: check status, configure Lightning, test payments, diagnose issues, create an initial wallet, get prompts, validate credentials, and complete onboarding.
Social media integration (X/Twitter): post tweets, get mentions, search posts, and retrieve the project's own timeline.
Provides integration with Lightning Network through LND, enabling agents to execute payments over Lightning
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., "@AgenticBTC MCP send $5 to alice@lightning.address"
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.
AgenticBTC MCP
Govern how AI agents pay and get paid.
AgenticBTC connects MCP-compatible agents to owner-controlled policies, payments, receivables, routing, and verifiable transaction evidence. Owners keep control of credentials and funds.
Try it safely first
The Payment Firewall test requires no account, wallet, signer, or payment credentials. It evaluates a supplied x402 or MCP payment request and returns an allow or block decision plus a downloadable evidence receipt. It does not move funds.
Related MCP server: ows-mcp-wallet
Requirements
Node.js 18 or newer
A free AgenticBTC owner account and API key for hosted tools
An MCP-compatible client such as OpenClaw or Claude Desktop
A connected payment rail only when you are ready to execute real payments
Install and verify with no account
npx agenticbtc-mcp@latest doctordoctor checks Node.js and the public AgenticBTC API. It uses no credentials, wallet, payment rail, or funds.
Connect your agent
npx agenticbtc-mcp@latest startThe guided setup shows the account-creation URL before asking for an API key. If you exit without a key, it makes no configuration changes.
Manual MCP configuration
{
"mcpServers": {
"agenticbtc": {
"command": "npx",
"args": ["-y", "agenticbtc-mcp@latest", "server"],
"env": {
"AGENTICBTC_API_URL": "https://agenticbtc.app",
"AGENTICBTC_API_KEY": "your-owner-api-key"
}
}
}
}Do not commit API keys, wallet credentials, macaroons, or private keys.
What requires an account
Public Payment Firewall test: no account, free, no funds
doctorand help: no account, free, no fundsSaved policies, scoped agent keys, hosted receipts, and connected AgenticBTC tools: free account and API key required
Real payments: configured owner-controlled rail and available funds required
Installing this package does not grant access to anyone else's funds and does not create or fund a wallet.
Optional Lightning configuration
Lightning is optional. For an LND-compatible node, set AGENTICBTC_LND_HOST and AGENTICBTC_LND_MACAROON using credentials scoped to the actions you intend to allow.
Environment variables
Variable | Purpose | Default |
| Hosted or self-hosted AgenticBTC API |
|
| Owner API key | Required for authenticated tools |
| Optional LND REST host | Unset |
| Optional LND macaroon | Unset |
Legacy AGENTBTC_* variable names remain accepted for compatibility. New setups should use AGENTICBTC_*.
Development
npm install
npm testbin/agentbtc.js CLI setup, status, and server launcher
src/server.js MCP server implementation
package.json npm package metadataSecurity and support
Security-sensitive reports:
support@agenticbtc.ioDocumentation: agenticbtc.io/docs
Issues: GitHub Issues
License
MIT. See LICENSE.
Available Tools
26 toolsaccess_l402_apiC
Access an L402-protected API endpoint with automatic Lightning payment
Inputs: endpoint (required), symbol.
check_channel_balanceB
Check available Lightning channel balance (outbound and inbound liquidity)
Inputs: no named parameters.
create_agent_walletB
Create a new Bitcoin wallet for an AI agent (owner access required)
Inputs: agent_name (required).
create_lightning_invoiceB
Create a Lightning Network invoice to receive Bitcoin payments
Inputs: amount_sats (required), agent, description.
decode_invoiceA
Decode a Lightning invoice to inspect amount, expiry, destination before paying
Inputs: invoice (required).
delete_agent_walletA
Delete an agent wallet by name or ID (owner access required)
Inputs: agent (required).
get_agent_balanceB
Get Bitcoin balance for an agent wallet
Inputs: agent_id (required).
get_mentionsA
Get recent @mentions and replies to @agentbtcio. Use to monitor engagement and find conversations to join.
Inputs: limit.
get_node_infoB
Get Lightning node connection status and info
Inputs: no named parameters.
get_own_timelineA
Get recent tweets posted by @agentbtcio. Use to review posting history before drafting new content.
Inputs: limit.
get_transaction_historyB
Get recent Lightning payment history
Inputs: max_payments.
list_agent_walletsB
List all agent wallets with their balances and status (agent key: own wallet only)
Inputs: no named parameters.
list_channelsA
List all Lightning channels with capacity, balance, and peer info
Inputs: no named parameters.
pay_lightning_invoiceA
Pay a Lightning Network invoice using agent wallet funds
Inputs: invoice (required), agent, fee_limit_sats.
post_tweetA
Post a tweet from @agentbtcio. Use for announcing launches, updates, or responding to relevant discussions. Keep under 280 chars.
Inputs: text (required), reply_to_tweet_id.
search_xA
Search recent X posts by keyword. Use to find conversations about AI agents, Lightning Network, Bitcoin payments, or AgenticBTC.
Inputs: query (required), limit.
send_paymentB
Send a payment to any recipient. Automatically detects recipient type: BOLT11 Lightning invoice (lnbc.../lntb...), Lightning address (user@domain.com), Strike handle ($username), or on-chain Bitcoin address (bc1.../1.../3...). Routes through the optimal payment rail.
Inputs: recipient (required), memo, agent, amount_usd, +1 more.
send_to_lightning_addressA
Send sats to a Lightning address (user@domain.com) using LNURL-pay protocol
Inputs: address (required), amount_sats (required), agent, comment.
setup_check_statusA
Check current AgenticBTC configuration status. Returns what's configured, what's missing, and the recommended next step.
Inputs: no named parameters.
setup_complete_onboardingB
Mark onboarding as complete. Returns a summary of everything that was configured.
Inputs: no named parameters.
setup_configure_lightningA
Configure Lightning node connection. Accepts lndconnect URL or host + macaroon. Validates before saving.
Inputs: host, macaroon, lndconnect_url.
setup_create_first_walletB
Create the user's first agent wallet with sensible defaults (1000 sat per-tx limit, 10000 sat daily budget).
Inputs: wallet_name.
setup_diagnose_issuesA
Diagnose AgenticBTC configuration problems. Returns specific error messages with fix instructions.
Inputs: no named parameters.
setup_get_onboarding_promptA
Returns a conversational prompt the AI should use to guide the user through AgenticBTC setup step by step.
Inputs: no named parameters.
setup_test_payment_capabilitiesB
Test that AgenticBTC payments work end to end. Checks API, Lightning, channels, and liquidity.
Inputs: no named parameters.
setup_validate_credentialsA
Validate API key and Lightning credentials without making any payments.
Inputs: api_key, lnd_host, lnd_macaroon.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 26 tools
Each tool targets a distinct operation, with clear separation between payment methods (pay_lightning_invoice, send_to_lightning_address, send_payment), wallet management, channel operations, and social media actions. The setup tools are cleanly prefixed with 'setup_' to avoid confusion.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_agent_wallet, post_tweet, get_mentions). Setup tools uniformly use the 'setup_' prefix, and social tools use common verbs like get, search, post.
26 tools is on the higher side but justified by the server's dual domain (Bitcoin/Lightning and X/Twitter). Each set of tools (setup, payments, wallet, social) has a purposeful number of endpoints. Slight overreach with 7 setup tools, but they streamline onboarding.
Covers the full lifecycle for wallet management, Lightning payments, and social media interaction. Includes onboarding, diagnostics, and testing. Minor gaps like replying to tweets or managing tweets beyond posting are absent but not critical for the core use case.
Maintenance
Related MCP Connectors
Give AI agents a wallet with a spending limit. Non-custodial USDC on Base, server-enforced limits.
Wallets and rails that let AI agents spend money safely.
Wallets and rails that let AI agents spend money safely.
Crypto wallet for AI agents: balances, payments, swaps and trading with owner controls.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables AI agents to manage USDC wallets on Solana, allowing them to send payments, create invoices, and access paid APIs within human-defined spending limits. It uses threshold signatures to provide agents with financial autonomy while ensuring secure oversight and transaction approval.3670 npm4Apache 2.0
- AlicenseAqualityDmaintenanceEnables AI agents to check balances and send transactions across multiple blockchains with automatic spending limit protection and policy enforcement.3MIT
- AlicenseAqualityDmaintenancePersistent memory and payment safety for AI agents on Lightning. Enables agents to remember purchases, track vendor reputations, enforce budgets, and share trust signals via Nostr.2212 PyPI9MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to make autonomous payments on Solana with on-chain enforced spending limits, preventing unauthorized fund drainage.1MIT