Bvcc Agent Wallet

What bvcc-agent-wallet MCP server does

The bvcc-agent-wallet MCP server connects an MCP-speaking runtime to a BVCC Agent Wallet. It can inspect wallet status, balances, capabilities, remaining limits, and approval requirements; prepare or simulate actions; and submit authorized transactions. Supported operations include native and token transfers, Uniswap v3/v4 swaps, Uniswap liquidity positions, and Aave v3 supply, borrow, repayment, collateral, and position-management workflows.

The wallet is non-custodial from the server’s perspective. The agent’s private key is loaded from the environment, used locally for signing, and not sent to BVCC. The wallet contract remains the enforcement point for native and token spending caps, daily and total limits, allowed assets and protocols, recipient restrictions, and the global pause state.

How it works

Tools are generated from the capability catalog in @bvcc/agent-sdk. The server groups them into core, aave, and lp modules, while the meta guide tools remain available. Read tools inspect current state, simulation tools plan or test an action, and write tools submit transactions. Write tools carry MCP destructive-action annotations so a client can request confirmation.

Each operation can accept an optional network, using a chain ID or a supported name such as ethereum, bsc, arbitrum, base, polygon, or arbitrum-sepolia. The default comes from CHAIN_ID, and the same wallet address can be used across networks when the agent is authorized on each one.

Aave position-closing and deleveraging operations may submit multiple transactions. They re-evaluate live state between steps and stop when the health factor would fall below the configured floor, pricing moves beyond the Aave oracle tolerance, progress stops, or the authorized budget is insufficient. The matching planning tools should be called first.

Setup and configuration

Install dependencies and build the project with npm install and npm run build; npm test runs the build and a stdio smoke test without chain calls. Configure the MCP host with AGENT_PRIVATE_KEY, WALLET_ADDRESS, and CHAIN_ID. AGENT_PRIVATE_KEY must be the agent EOA key in 0x plus 64 hexadecimal characters, and WALLET_ADDRESS identifies the BVCC Agent Wallet.

For safer host configuration, place these values in a dedicated file and set BVCC_ENV_FILE to its path. The README recommends restricting that file’s permissions and keeping it outside cloud-synced storage. Host environment values take precedence over values loaded from the file.

Set RPC_URL for a custom default-chain endpoint or RPC_URL_<chainId> for a per-network override. Set BVCC_MCP_READONLY=true to expose only read and simulation tools. Use BVCC_MCP_MODULES to limit the exposed feature groups, such as core, aave, or lp; unrecognized module names are ignored.

Tools and capabilities

The bvcc-agent-wallet MCP server includes these capability areas:

• Core wallet and trading: status, balances, limits, approvals, native and token transfers, swap planning, simulations, and Uniswap v3/v4 swaps.
• Aave v3: market and position reads, supply, withdrawal, borrowing, repayment, collateral settings, efficiency mode, and planned or executed position unwinding.
• Uniswap liquidity: v3 and v4 position reads, add/remove simulations, position creation, liquidity removal, fee collection, and burns.
• Guides: listGuides and getGuide provide workflows for setup, swaps, lending, and liquidity. These guides are also exposed as prompts.

A 0.15% BVCC agent fee applies automatically to agent actions, separately from gas and the configured spending budget. Aave deposits and borrows are for the wallet itself; the tools do not accept a beneficiary or onBehalfOf destination. Uniswap v4 operations involving native ETH require the v4 PositionManager’s DEEP validator to be active for the agent.