Bvcc Agent Wallet 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 bvcc-agent-wallet -- npx -y @bvcc/agent-mcp

{
  "mcpServers": {
    "bvcc-agent-wallet": {
      "args": [
        "-y",
        "@bvcc/agent-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.bvcc-agent-wallet]
command = "npx"
args = ["-y", "@bvcc/agent-mcp"]

{
  "mcpServers": {
    "bvcc-agent-wallet": {
      "args": [
        "-y",
        "@bvcc/agent-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "bvcc-agent-wallet": {
      "args": [
        "-y",
        "@bvcc/agent-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: AGENT_PRIVATE_KEY (Agent EOA private key (0x + 64 hex). Used locally to sign only; never transmitted.), WALLET_ADDRESS (The BVCC Agent Wallet address this agent operates (0x...).), CHAIN_ID (Default chain id: 42161 Arbitrum, 56 BNB Chain, 1 Ethereum, 8453 Base, 137 Polygon, 421614 Arbitrum Sepolia. Every tool also accepts an optional per-call network.), RPC_URL (Optional custom RPC for the default chain (comma-separated list allowed for failover). Public default used otherwise. Per-chain override via RPC_URL_<chainId>.), BVCC_MCP_READONLY (Set to 'true' to expose only read/simulate tools (no fund-moving writes).), BVCC_MCP_MODULES (Comma-separated capability modules to expose: core, aave. Unset exposes all.). The author declared them in the registry entry; get the values from the project itself.