Bitcoin MCP vs Git
A side-by-side look at the Bitcoin MCP and Git MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Bitcoin MCP for finance & fintech work as a local process; choose Git for other tools and integrations 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.
Choose Git when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
create_entities, create_relations, add_observations.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Other Tools and Integrations |
| Quality signal | 59/100 · Good | 89/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | No auth required |
| 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.
Git tools 9
create_entitiesCreate multiple new entities in the knowledge graphcreate_relationsCreate multiple new relations between entities in the knowledge graph. Relations should be in active voiceadd_observationsAdd new observations to existing entities in the knowledge graphdelete_entitiesDelete multiple entities and their associated relations from the knowledge graphdelete_observationsDelete specific observations from entities in the knowledge graphdelete_relationsDelete multiple relations from the knowledge graphread_graphRead the entire knowledge graphsearch_nodesSearch for nodes in the knowledge graph based on a queryopen_nodesOpen specific nodes in the knowledge graph by their names
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"
}
}
}
}
Git
{
"mcpServers": {
"git": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}
}
Frequently asked questions
Bitcoin MCP is categorized under Finance & Fintech and uses a local stdio subprocess. Git belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick Bitcoin MCP for finance & fintech work and Git for other tools and integrations.
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. Git is listed as free. Auth: no auth required. 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 git 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. Git has 89/100 (Excellent) with 39 views, 0 installs and 91,289 GitHub stars.
