bitcoin-mcp
Give any AI agent Bitcoin superpowers — fee intelligence, mempool analysis, and 50 tools backed by your Bitcoin node or compatible API.
接入你的智能体
發布者自己的指令。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
uvx bitcoin-mcp==0.5.1Claude Code 沒有本機指令的安裝連結。複製下方指令並在終端機中執行。
BITCOIN_RPC_HOST=<value> BITCOIN_RPC_PORT=<value> BITCOIN_NETWORK=<value> SATOSHI_API_URL=<value> SATOSHI_API_KEY=<secret> claude mcp add io.github.bortlesboat-bitcoin-mcp -- uvx bitcoin-mcp==0.5.1在終端機中執行。
{ "mcpServers": { "io.github.bortlesboat-bitcoin-mcp": { "command": "uvx", "args": [ "bitcoin-mcp==0.5.1" ], "env": { "BITCOIN_RPC_HOST": "<value>", "BITCOIN_RPC_PORT": "<value>", "BITCOIN_NETWORK": "<value>", "SATOSHI_API_URL": "<value>", "SATOSHI_API_KEY": "<secret>" } } }}claude_desktop_config.json
遠端 URL 還是本機指令? 兩種安裝方式的差異
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.
pip install "bitcoin-mcp>=0.5.2"
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.comis paused and should not be treated as a working default. Use a local node or an explicitly configured compatible API.
Version 0.5.2 includes the MCP SDK 1.x compatibility constraint and explicit backend selection. Upgrade older installations to receive these fixes.
Add to your claude_desktop_config.json:
{
"mcpServers": {
"bitcoin": {
"command": "uvx",
"args": ["--from", "bitcoin-mcp>=0.5.2", "bitcoin-mcp"]
}
}
}
claude mcp add bitcoin -- uvx --from "bitcoin-mcp>=0.5.2" bitcoin-mcp
Add to .cursor/mcp.json:
{
"mcpServers": {
"bitcoin": {
"command": "uvx",
"args": ["--from", "bitcoin-mcp>=0.5.2", "bitcoin-mcp"]
}
}
}
Add to .vscode/mcp.json:
{
"servers": {
"bitcoin": {
"command": "uvx",
"args": ["--from", "bitcoin-mcp>=0.5.2", "bitcoin-mcp"]
}
}
}
Add to your Zed settings.json under context_servers:
{
"context_servers": {
"bitcoin": {
"command": "uvx",
"args": ["--from", "bitcoin-mcp>=0.5.2", "bitcoin-mcp"]
}
}
}
See the Zed MCP docs for the current settings location and custom server flow.
docker build -t bitcoin-mcp .
docker run -i bitcoin-mcp
Or with docker compose:
docker compose up
Pass environment variables to connect to a local Bitcoin Core node or a compatible API:
docker run -i -e BITCOIN_RPC_HOST=host.docker.internal -e BITCOIN_RPC_PORT=8332 bitcoin-mcp
# or
docker run -i -e SATOSHI_API_URL=https://your-api.example bitcoin-mcp
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:
get_fee_recommendation.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.
For repos that need Bitcoin tools, add bitcoin-mcp to the agent's MCP config and configure one of its supported backends:
BITCOIN_RPC_HOST, BITCOIN_RPC_PORT, and optional credentials or datadirSATOSHI_API_URL and, when required, SATOSHI_API_KEYGenerated HTTP examples should use canonical Satoshi API /api/v1 paths.
Ask your AI agent:
query_remote_api is registered only when SATOSHI_API_URL is set and the l402 extra is installed. It queries canonical /api/v1 routes on that explicitly configured endpoint.
Configure either a local Bitcoin Core/Knots node or a compatible remote API. If neither is available, bitcoin-mcp exits its connection check with a setup error instead of silently selecting an unavailable public service.
bitcoin-mcp supports the following runtime flags:
Example:
bitcoin-mcp --transport sse --host 127.0.0.1 --port 8000 --log-level DEBUG
To connect to a local Bitcoin Core node:
{
"mcpServers": {
"bitcoin": {
"command": "uvx",
"args": ["--from", "bitcoin-mcp>=0.5.2", "bitcoin-mcp"],
"env": {
"BITCOIN_RPC_HOST": "127.0.0.1",
"BITCOIN_RPC_PORT": "8332"
}
}
}
}
6 built-in prompts for common workflows:
analyze_fee_environment, investigate_transaction, monitor_mempool_fees, taproot_adoption_report, network_health_report, track_transaction
8 resources for context injection:
bitcoin://connection/status, bitcoin://node/status, bitcoin://fees/current, bitcoin://fees/history, bitcoin://mempool/snapshot, bitcoin://protocol/script-opcodes, bitcoin://protocol/address-types, bitcoin://protocol/sighash-types
io.github.Bortlesboat/bitcoin-mcpSee the examples/ folder for documented usage patterns:
bitcoin-mcp is free, open-source Bitcoin infrastructure. Support development through GitHub Sponsors, reproducible issue reports, documentation improvements, and tested patches.
Run the unit suite with python -m pytest tests/. For the optional Core/Knots
checks over the MCP interface, see real-node integration tests.
Contributions are welcome. See CONTRIBUTING.md for guidelines, including how to add new tools and the PR checklist.
Please report security vulnerabilities privately — see SECURITY.md.
bitcoin-mcp is created and maintained by Andrew Barnes, bridging AI agents and Bitcoin infrastructure through the Model Context Protocol.
Related projects:
49 Bitcoin tools for AI agents: fees, mempool, blocks, mining, price. Zero config.
{ "mcpServers": { "io.github.bortlesboat-bitcoin-mcp": { "command": "uvx", "args": [ "bitcoin-mcp==0.5.1" ], "env": { "BITCOIN_RPC_HOST": "<value>", "BITCOIN_RPC_PORT": "<value>", "BITCOIN_NETWORK": "<value>", "SATOSHI_API_URL": "<value>", "SATOSHI_API_KEY": "<secret>" } } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
發布者列出了以下環境變數:BITCOIN_RPC_HOST, BITCOIN_RPC_PORT, BITCOIN_NETWORK, SATOSHI_API_URL, SATOSHI_API_KEY。
Bitcoin MCP 透過 stdio 在本機執行。
上次檢查時間:2026-11-08。 49 Bitcoin tools for AI agents: fees, mempool, blocks, mining, price. Zero config.