opldotdev/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 · All tools · npm · Issues
## Install
Install Bun to run the server and Node.js for the npx commands below, then add it to your client:
sh
# Codex
codex mcp add bsv-mcp -- npx -y bsv-mcp@latest --stdio
# Claude Code
claude mcp add --transport stdio bsv-mcp -- npx -y bsv-mcp@latest --stdio
# Grok Build
grok plugin install b-open-io/bsv-mcp --trust
Choose one command. For Cursor or Claude Desktop, use this server configuration:
json
"mcpServers": {
"bsv-mcp": {
"command": "npx",
"args": ["-y", "bsv-mcp@latest", "--stdio"]
Restart your client, then ask: “Run bsvstatus and explain what is available.”
Local stdio needs no Sigma account or OAuth sign-in. It is also the default when
no transport is specified. Existing self-hosted HTTP remains opt-in through
TRANSPORT=http; the deployed hosted endpoint is unchanged.
For the Codex desktop plugin, add b-open-io/claude-plugins in the plugin
marketplace and install BSV MCP. The plugin starts the local npm executable
and requires Node.js and Bun. Claude Code and Grok plugins bundle the local server and
require Bun. Choose one registration to avoid duplicate tools.
## Connect a wallet
Ask your assistant to run walletonboarding. Create, import or unlock a Vault
in the local browser. Back it up before funding. Enter passwords only in the
local setup UI, never in chat. After a server restart, unlock it again.
To use an existing BRC-100 wallet, configure its signing API instead:
json
"mcpServers": {
"bsv-mcp": {
"command": "npx",
"args": ["-y", "bsv-mcp@latest", "--stdio"],
"env": {
"BRC100WALLETURL": "http://127.0.0.1:3321",
"BRC100WALLETORIGINATOR": "bsv-mcp.local"
The wallet keeps its keys and controls permission requests. Its signing API is
separate from a wallet-storage endpoint. See wallet setup
for network settings, account selection and project roles.
The package also includes the Bun-based bsv-mcp-local launcher for explicit external,
legacy embedded and project configurations. Source-checkout examples live in
the installation guide.
## MCP protocol compatibility
Protocol revision 2026-07-28 is preferred, with supported 2025 clients
accepted automatically on stdio and HTTP. No compatibility override is needed.
Set MCPLEGACYCOMPATIBILITY=false only to require modern clients. This
setting also passes through the local launcher. The installed desktop client
was verified using legacy requests; modern support is tested separately.
Modern clients support wallet operations and request-scoped approval. Approval
continuations retain the original operation and bind to its authenticated user,
arguments, and expiry. Decline, cancellation, or session revocation stops the
operation; replaying a continuation does not repeat a transaction. A client
without form elicitation cannot approve a spend. External wallets retain their
own signer permission flow. The hosted route exposes public reads only.
For the split SDK v2 client:
ts
const client = new Client(
{ name: "my-app", version: "1" },
{ versionNegotiation: { mode: "auto" }, capabilities: { elicitation: { form: {} } } },