avaConnect

first session

Connected means your agent can list Ava's 15 tools

Three steps, each one you can verify yourself. No signup, no funding, nothing spent. The whole session ends with your own agent proving the connection to you.

  1. Run one command

    npx @getava-xyz/connect

    Writes the MCP config for Claude Code, Cursor, and Codex, mints a session, and shows your Base wallet address. Nothing is spent.

    checkThe command prints the wallet address and the exact config paths it wrote.

  2. Ask your agent to list Ava tools

    Do not take this page's word for the connection. Ask the agent itself.

    Open a new Claude Code session so it rereads ~/.claude.json. Typing /mcp there also shows the ava server directly.

    List the tools on the ava MCP server.

    check15 tools. If you see them, you are connected.

  3. First bounded action

    Paste this into the same agent. It writes a mandate, previews a real lend against it, and stops at the line the mandate draws.

    Create a tight lend-only USDC mandate on Base for 5 USDC, preview the lend, and stop before executing.

    Expected halt: the preview, then LEND_INSUFFICIENT_BALANCE if the wallet is unfunded. That refusal is correct behavior. The agent hit the boundary you wrote, with no money in play.

    checkA mandate id, a lend preview, and a stop. No transaction was signed or sent.

fund it when ready

The local dashboard reads the configs already on your disk and shows balances across Base, Arbitrum, Avalanche, and BNB. Send USDC on Base to the printed address when you want that same lend to fill instead of halt.

npx @getava-xyz/connect dashboard

Prefer to write the config by hand? The manual config reference has the three exact snippets. The reference lists every endpoint and tool.