@getava-xyz/connect

One command for a stranger: session, MCP config in the coding-agent client, a Base EVM address, and an honest stop if the wallet is unfunded.

npx @getava-xyz/connect

Same as npx @getava-xyz/connect init. Default portal is Base. This CLI does not lend unless you pass --execute and the wallet is funded.

What it does

1. Calls ava_session against https://www.getava.xyz/mcp (https://api.getava.xyz is the same API).
2. Writes HTTP MCP config with Authorization: Bearer <token> to the documented user-scope files:
   • Claude Code: ~/.claude.json (type: "http"), same shape as claude mcp add --transport http
   • Cursor: ~/.cursor/mcp.json
   • Codex: ~/.codex/config.toml ([mcp_servers.ava])
3. Calls ava_create_agent with agentId=byo-external and a unique label.
4. Calls ava_provision_wallet with family=evm.
5. Prints the Base address and: fund USDC + ETH gas on Base. The live loop in your coding agent is ava_lend_execute (mandateId + two-phase previewHash). LEND_INSUFFICIENT_BALANCE is a stop, not a retry.

The bearer token is stored in those config files (mode 0600) and is not reprinted.

What it will not do

• Narrate an unfunded wallet as ready to lend.
• Default to Sui or copilot.
• Invent a wallet address when provision is pending.
• Treat amount as a JavaScript number.
• Sign. The LLM is never the signer; Turnkey holds the key on the server.

--execute

npx @getava-xyz/connect init --execute --mandate-id mdt_... --amount 1.5

Requires a mandate you already created. Runs the two-phase lend and stops on LEND_INSUFFICIENT_BALANCE. Do not pass this flag until the Base address holds USDC and gas.

Local dashboard

The hosted page at getava.xyz/dashboard cannot read ~/.claude.json, Cursor, or Codex. This CLI can, because it runs on the machine that holds those files.

npx @getava-xyz/connect dashboard

That scans known client files, calls GET /v1/users/me per token, and opens a picker. You select a wallet. Isolation per agent stays the default; reuse is that click. It does not mint a session when tokens already exist.

Wallets are keyed by Ava userId, not by GitHub or Claude login. To use an address such as 0x6485…e77c, resume the user that owns it. Email and passkey are the long-term human identity; this command is local discovery plus a picker.

npx @getava-xyz/connect dashboard     # picker; does not mint if tokens already exist
npx @getava-xyz/connect open          # same
npx @getava-xyz/connect --resume      # reuse the last pick / AVA_TOKEN; no new wallet
npx @getava-xyz/connect --resume --new-wallet   # provision another EVM wallet on that user

Do not paste ava_st_ tokens into the browser. A device-link from the picker opens getava.xyz for the same user without putting the token or the device code in a query string. The hosted tab receives a dashboard-scoped bearer; it cannot lend, swap, bridge, or execute a workflow. Spend stays on the original session token.

Flags

| Flag | Meaning | |---|---| | --mcp-url | Override. Default https://www.getava.xyz/mcp | | --home | Config home directory (default $HOME) | | --clients | claude,cursor,codex | | --json | Machine-readable result (still no token) | | --resume | Reuse last pick / AVA_TOKEN; print address; no mint | | --new-wallet | With --resume, provision another EVM wallet on that user | | --no-open | Print the local dashboard URL; do not spawn a browser | | --port | Bind port for the local dashboard | | --api | REST origin for dashboard/resume (default https://getava.xyz) |

Env: AVA_MCP_URL or AVA_API_BASE. Codex honors CODEX_HOME.