Bitcoin MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| setup_walletD | – |
| get_balanceD | – |
| send_bitcoinD | – |
| get_addressD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| status | |
| address |
TDQS
Scored across 4 tools
Each tool targets a distinct operation: wallet setup, balance query, transaction sending, and address retrieval. There is no overlap in their purposes.
All tool names follow a consistent verb_noun snake_case pattern: setup_wallet, get_balance, send_bitcoin, get_address. The naming is uniform and predictable.
With four tools, the set is well-scoped for a Bitcoin wallet server. Each tool covers an essential function without redundancy or unnecessary bloat.
The core wallet lifecycle is covered: setup, balance check, sending, and address generation. A minor gap is the lack of transaction history or receive mechanisms, but the essential operations are present.