Onchain Agent Wallets MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add onchain-agent-wallets -- npx -y @three-ws/onchain-agent-wallets

{
  "mcpServers": {
    "onchain-agent-wallets": {
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/onchain-agent-wallets"
      ]
    }
  }
}

[mcp_servers.onchain-agent-wallets]
command = "npx"
args = ["-y", "@three-ws/onchain-agent-wallets"]

{
  "mcpServers": {
    "onchain-agent-wallets": {
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/onchain-agent-wallets"
      ]
    }
  }
}

{
  "servers": {
    "onchain-agent-wallets": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/onchain-agent-wallets"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: OWNER_SECRET_KEY (Owner secret key, base58 or a JSON byte array. Optional: without it every owner action is returned as an unsigned transaction for Phantom, Solflare, Backpack, or a Ledger to sign), OAW_NETWORK (Cluster: mainnet or devnet. Defaults to mainnet. State is kept per network, so a devnet rehearsal never touches mainnet agents), SOLANA_RPC_URL (HTTPS Solana RPC endpoint. Defaults to the public endpoint for the configured network; bring your own (Helius / Quicknode / Triton) for production), OAW_STATE_DIR (Where agent keypairs, guardrails, and the spend ledger are stored. Defaults to ~/.onchain-agent-wallets, written 0600 inside a 0700 directory), REQUIRE_CONFIRM (Refuse to broadcast anything that moves value until the call is re-issued with confirm:true. Default true).