Bitcoin MCP vs Comdirect
A side-by-side look at the Bitcoin MCP and Comdirect MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
ComdirectFinance & Fintech · Local subprocess (stdio)Read-only access to comdirect accounts, transactions, depots, orders and postbox documents.44FairAuth: otherVerdict: choose Bitcoin MCP for finance & fintech work as a local process; choose Comdirect for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Bitcoin MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
BITCOIN_RPC_HOST, BITCOIN_RPC_PORT, SATOSHI_API_URL, SATOSHI_API_KEY.
CChoose Comdirect when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Comdirect | |
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 59/100 · Good | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | other |
| Pricing | Free | Free |
| Required env vars | BITCOIN_RPC_HOSTBITCOIN_RPC_PORTSATOSHI_API_URL |
Tools & capabilities
Bitcoin MCP tools
No tool names declared yet. Check the project README from the listing page.
Comdirect tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Bitcoin MCP
{
"mcpServers": {
"bortlesboat-bitcoin-mcp": {
"command": "uvx",
"args": [
"--from",
"bitcoin-mcp>=0.5.2",
"bitcoin-mcp"
],
"env": {
"BITCOIN_RPC_HOST": "YOUR_BITCOIN_RPC_HOST_HERE",
"BITCOIN_RPC_PORT": "YOUR_BITCOIN_RPC_PORT_HERE",
"SATOSHI_API_URL": "YOUR_SATOSHI_API_URL_HERE",
"SATOSHI_API_KEY": "YOUR_SATOSHI_API_KEY_HERE"
}
}
}
}
Comdirect
{
"mcpServers": {
"comdirect": {
"command": "uvx",
"args": [
"comdirect-mcp@0.6.1"
]
}
}
}
Frequently asked questions
Bitcoin MCP is categorized under Finance & Fintech and uses a local stdio subprocess. Comdirect belongs to Finance & Fintech and uses a local stdio subprocess. Pick Bitcoin MCP for finance & fintech work and Comdirect for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Bitcoin MCP is listed as free. Auth: other. Comdirect is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add bortlesboat-bitcoin-mcp and comdirect as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Bitcoin MCP has a quality signal of 59/100 (Good) with 4 views, 0 installs and 5 GitHub stars. Comdirect has 44/100 (Fair) with 0 views, 0 installs and 3 GitHub stars.
