BSV blockchainBSV blockchain

Coding with agents

Set up an AI coding agent, such as Claude Code, Cursor, Windsurf or VS Code, so it builds BSV blockchain apps the way these docs describe. It takes three pieces: the BSV blockchain docs server gives the agent these pages, the bsv-dev skill gives it the decisions, and @bsv/mcp gives it tools. In Claude Code, one plugin installs all three. Use it when an agent writes your code for the BSV blockchain. At the end, the agent reads the docs, builds on testnet, keeps keys out of the code and checks its work against the BSV blockchain guardrails.

How it works

Each piece gives the agent something different:

  • BSV docs server
    Gives the agent
    Search and full pages of these docs, as Markdown
    Use it for
    Answers and code that follow these guides
  • bsv-dev skill
    Gives the agent
    The decisions: who holds the keys, payments and channels, BSV Broadcaster and finality, testnet to Mainnet, the guardrail review
    Use it for
    Building the way these docs do
  • @bsv/mcp
    Gives the agent
    Tools for BSV Broadcaster, a guardrail check, BRCs and versions, with dated facts
    Use it for
    Actions and live values, on testnet by default

Everything starts on testnet, where the coins have no value and come free from the faucet. Where the wallet lives is the app’s choice, and the skill makes it per money path. In shape A, the app asks the user’s BRC-100The standard interface between an app and a wallet wallet to sign. The skill gives every new app a login with two paths: BSV Desktop on the same computer, and a phone wallet such as BSV Browser, paired by QR code. BSV Desktop signs within the small monthly allowance the user granted to the app, and prompts for anything above it. In shape B, the app runs its own server wallet, which pays with no user present. No tool takes a private key, and the skill never asks for one.

What you can ask

With the pieces set up, try requests like these:

  • Add tipping to my React app on BSV. Use BSV Desktop on testnet.
  • Check the status of transaction TXID on BSV Broadcaster and tell me whether it is final. Replace TXID with the transaction ID.
  • Review this project against the BSV guardrails and fix every error.
  • Which wallet shape fits an app that pays creators automatically every night?
  • Should my game use a payment channel or one payment per move?
  • Send my first BSV payment from a small Node.js script. Build it and run it. Send a payment with an AI agent walks through this one.

Set up your agent

In Claude Code, install the plugin. Without it, add each piece on its own. The next two pages show each command with its output.

Install the plugin in Claude Code

The bsv-dev plugin holds the skill and both MCP servers, bsv-docs and bsv-mcp. It starts @bsv/mcp on your machine through npx, which needs Node.js 22 or newer:

claude plugin marketplace add bsv-blockchain/bsv-ai-toolkit && claude plugin install bsv-dev@bsv

With the plugin, do not also add the servers with claude mcp add, or Claude Code starts a second copy of bsv-mcp. If you added them before, remove them first, as Install the BSV blockchain agent skill shows.

Set up without the plugin

To connect only the two servers in Claude Code, without the skill, run these commands in your project folder instead of installing the plugin. The docs server runs on this site and needs no login, and @bsv/mcp runs through npx and needs Node.js 22 or newer:

claude mcp add --transport http bsv-docs https://bsvblockchain.com/docs/mcp
claude mcp add bsv-mcp -e BSV_NETWORK=testnet -- npx -y @bsv/mcp

In any other agent that reads Agent Skills, install the skill on its own, then add the two servers as JSON, as in Use another AI tool:

npx skills add bsv-blockchain/bsv-ai-toolkit

Skills library

The official skill is bsv-dev, maintained by BSV Association in bsv-blockchain/bsv-ai-toolkit.

Skills from other authors are listed in community-skills.yaml in the same repository. Each one is added by pull request, with every link pinned to the commit that was reviewed. The list is empty today.

Next steps

With the agent set up, start from a working app, let the agent send a first testnet payment, or read the docs the way it does: