BTCFi API MCP Server

Bitcoin data for AI agents. 27 tools with x402 micropayments. No API keys needed.

Remote serverstreamable-httpTypeScript

What is the BTCFi API MCP server?

Bitcoin data for AI agents. 27 tools with x402 micropayments. No API keys needed. That is what the btcfi api mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

BTCFi API is an agent-native Bitcoin intelligence platform providing 80+ endpoints across Bitcoin, Ethereum, Solana, Lightning Network, Runes, and Taproot Assets. Powered by x402 micropayments — pay $0.01–$0.05 per query in USDC, no API keys or subscriptions required. CoinGecko integration provides multi-currency pricing (38 fiat currencies). AI agents discover endpoints at /llms.txt and integrate via MCP, SDK, or raw HTTP.

What it needs from you

Configuration is passed through the environment: UPSTASH_REDIS_REST_URL, UPSTASH_REDIS_REST_TOKEN, X402_FACILITATOR_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by aiindigo925; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against BTCFi API's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How to install the BTCFi API MCP server

{
  "mcpServers": {
    "btcfi": {
      "command": "npx",
      "args": ["-y", "@aiindigo/btcfi-mcp"],
      "env": {
        "UPSTASH_REDIS_REST_URL": "your-value",
        "UPSTASH_REDIS_REST_TOKEN": "your-value",
        "X402_FACILITATOR_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
UPSTASH_REDIS_REST_URLEndpoint or connection string the server talks to.Yes
UPSTASH_REDIS_REST_TOKENCredential the server authenticates with.Yes
X402_FACILITATOR_URLEndpoint or connection string the server talks to.Yes

Frequently asked questions

It connects BTCFi API to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with BTCFi API directly.