BSV MCP

BSV MCP connects your AI assistant to Bitcoin SV. Ask it to check a transaction, show your balance, send a payment, or create and trade ordinals (content recorded on the blockchain).

Documentation · Connect hosted · npm · Issues

Install in ChatGPT desktop or Codex

In Plugins, choose Add marketplace and enter b-open-io/claude-plugins. Leave Git ref and Sparse paths blank. Select BSV MCP in the bOpen marketplace and install it. Authenticate through Sigma Identity when prompted, then start a new chat and ask: “Run bsv_status and explain which services are available.”

The plugin uses hosted MCP, so you do not need Bun or a local wallet. Signing in does not authorize spending or connect a wallet on your computer. For wallet operations, use the local setup below. If you already have a manual BSV MCP connection, choose which connection to use to avoid duplicate tools.

Quick start

Install Bun. Set up an encrypted account with bunx bsv-mcp@latest init, or connect an existing signer as described in wallet setup. Then register the server:

# Codex
codex mcp add bsv-mcp -- bunx bsv-mcp@latest --stdio

# Claude Code
claude mcp add --transport stdio bsv-mcp -- bunx bsv-mcp@latest --stdio

Or install the Claude Code plugin from the b-open-io marketplace:

claude plugin install bsv-mcp@b-open-io

For other clients, use bunx bsv-mcp@latest --stdio as the MCP server command (stdio transport). For hosted access, connect to https://bsvmcp.com. See client setup.

Ask your agent: “Run bsv_status, then show my wallet balance.”

Bring your wallet and infrastructure

Connect a compatible existing wallet with BRC100_WALLET_URL, or select an encrypted account with BSV_MCP_ACCOUNT and unlock it with BSV_MCP_PASSWORD in the process environment. Startup never creates keys. An existing wallet keeps its keys and controls permissions. PRIVATE_KEY_WIF and IDENTITY_KEY_WIF are legacy compatibility inputs; they trigger a persistent Vault migration warning and should be removed after migration. See the wallet setup guide for the required wallet API and configuration.

The default 1Sat backend is https://api.1sat.app. Override ONESAT_API_URL to use a compatible deployment; configure wallet storage, explorer, content, and legacy services separately. Available tools depend on wallet mode and enabled modules.

• Wallet setup

• Backend configuration

• Tools and workflows

• Paid service requests

• Sponsorship and agent delegation

• Troubleshooting and development

Development

bun install
bun run dev          # Website
bun run build:all    # MCP server and dashboard
bun dist/index.js --stdio # Local stdio launch; npm publication is not required
bun test

Experimental software; APIs may change. Keep a wallet backup. If a transaction request times out, check whether it succeeded before sending it again. MIT licensed.