Mcp Server
Wire Claude Code or Cursor agents to Bitcoin and Stacks wallets, DeFi, sBTC, NFTs, and x402 payments without hand-rolling chain APIs.
Overview
io.github.aibtcdev/mcp-server is a Build-phase MCP server that lets AI coding agents operate Bitcoin and Stacks wallets, DeFi, sBTC, NFTs, and x402 payments through Model Context Protocol tools.
What is this MCP server?
- BTC and STX wallet operations exposed as MCP tools for agent-driven flows
- DeFi yield, sBTC peg, and NFT actions on Bitcoin-native stacks
- x402 payment protocol support for agentic micropayments
- stdio npm package @aibtc/mcp-server v1.17.0
- GitHub source at aibtcdev/aibtc-mcp-server
- Server version 1.17.0 in MCP schema
- Single npm package @aibtc/mcp-server with stdio transport
- Repository: github.com/aibtcdev/aibtc-mcp-server
Community signal: 10 GitHub stars.
What problem does it solve?
Solo builders waste days stitching wallet, DeFi, and payment APIs into agent projects instead of shipping features.
Who is it for?
Indie devs building Bitcoin- or Stacks-backed agents, DeFi dashboards, or x402 payment flows inside Claude Code or Cursor.
Skip if: Teams that need only traditional card payments, no on-chain surface, or regulated custody without their own compliance stack.
What do I get? / Deliverables
After you add the stdio server to your agent config, the model can invoke Bitcoin-native wallet, yield, NFT, and x402 tools from the same session where you write code.
- Registered stdio MCP server in agent config
- Callable tools for BTC/STX wallets, DeFi, NFTs, and x402 from the agent session
Recommended MCP Servers
Journey fit
Crypto and wallet integrations belong in Build when you are connecting the product and agent stack to live financial rails. Integrations is the canonical shelf for MCP servers that expose third-party protocols (here BTC/STX/DeFi) to your coding agent.
How it compares
On-chain finance MCP integration, not a generic web-scraping or company-research skill.
Common Questions / FAQ
Who is io.github.aibtcdev/mcp-server for?
Solo and indie builders shipping AI agents that must read or write on Bitcoin and Stacks—including wallets, DeFi, sBTC, NFTs, or x402 payments.
When should I use io.github.aibtcdev/mcp-server?
During the build phase when you are wiring agent tooling to live chain APIs and want MCP tools instead of custom SDK glue in every repo.
How do I add io.github.aibtcdev/mcp-server to my agent?
Install the npm package @aibtc/mcp-server (v1.17.0), configure stdio transport in Claude Code, Cursor, or another MCP host, and point it at your wallet or network settings per the GitHub repo.