Bortlesboat/bitcoin-mcp

Give any AI agent Bitcoin superpowers — fee intelligence, mempool analysis, and 50 tools backed by your Bitcoin node or compatible API.
**50 standard tools** · **6 prompts** · **8 resources** · **Bitcoin Core or compatible API backend** · **MIT licensed**
> If bitcoin-mcp is useful to you, consider giving it a star — it helps others discover the project.
bitcoin-mcp needs a Bitcoin data backend. It auto-detects a local Bitcoin Core/Knots node from its cookie or RPC settings. Without a local node, set SATOSHI_API_URL to a compatible deployment.
> **Service status:** the public Satoshi API previously hosted at bitcoinsapi.com is paused and should not be treated as a working default. Use a local node or an explicitly configured compatible API.
Install status
Version 0.5.2 includes the MCP SDK 1.x compatibility constraint and explicit backend selection. Upgrade older installations to receive these fixes.
Quick Start
Claude Desktop
Add to your claude_desktop_config.json:
Claude Code
Cursor
Add to .cursor/mcp.json:
VS Code
Add to .vscode/mcp.json:
Zed
Add to your Zed settings.json under context_servers:
See the Zed MCP docs for the current settings location and custom server flow.
Docker
Or with docker compose:
Pass environment variables to connect to a local Bitcoin Core node or a compatible API:
Ask whether to send Bitcoin now
Use this as the first useful activation path after install:
> "I need to send a Bitcoin transaction today. Use bitcoin-mcp to decide whether to send now or wait, and show the fee rate you used."
Expected path:
1. The agent calls get_fee_recommendation.
2. The answer gives a clear send now or wait recommendation with fee rates in sat/vB.
3. If the backend is unavailable, configure a local node or set SATOSHI_API_URL before retrying.
After it works, Star this repo and share a short showcase with the prompt, tool call, and outcome so other Bitcoin agent builders can see the path.
Agent Integration
For repos that need Bitcoin tools, add bitcoin-mcp to the agent's MCP config and configure one of its supported backends:
- Local Bitcoin Core/Knots RPC settings: BITCOIN_RPC_HOST, BITCOIN_RPC_PORT, and optional credentials or datadir
- Compatible remote API: SATOSHI_API_URL and, when required, SATOSHI_API_KEY
- Satoshi API source and integration reference: https://github.com/Bortlesboat/bitcoin-api/blob/master/docs/AGENT_INTEGRATION.md
Generated HTTP examples should use canonical Satoshi API /api/v1 paths.
Why bitcoin-mcp?
- **Fee intelligence that saves real money** — know the cheapest time to send, compare fee tiers, estimate exact costs before broadcasting
- **Backend choice** — use your own Bitcoin Core/Knots node or an explicitly configured compatible API
- **Open source MCP tooling** — tool definitions, tests, and client configuration examples are available in this repository
Top Use Cases
Ask your AI agent:
| Prompt | What it does |
|--------|-------------|
| "What's the cheapest time to send Bitcoin today?" | Fee recommendation with savings breakdown |
| "Analyze the current mempool congestion" | Real-time mempool depth, fee tiers, pending tx count |
| "How much would I save waiting 6 blocks vs next block?" | Side-by-side fee comparison across confirmation targets |
| "Search for this transaction: abc123..." | Full transaction decode with inscription detection |
| "Give me a situation summary of Bitcoin right now" | Price, fees, mempool, mining, difficulty — one call |
Full Tool Reference
All 50 standard tools by category
Fee Intelligence
| Tool | Description |
|------|-------------|
| get_fee_recommendation | Optimal fee rate with urgency tiers and savings tips |
| get_fee_estimates | Fee estimates across all confirmation targets |
| estimate_smart_fee | Fee estimate for a specific confirmation target |