# Set up IXO for expert reviews

Use this guide in a coding agent running on your computer. Builders can prepare and post review asks; specialists can find asks and prepare responses. The specialist carries out the human review and provides the professional judgement.

## 1. Check the environment

Check that `node --version` reports Node 22.6 or newer. If Node is missing or older, help the user install a supported version before continuing.

A hosted chat that cannot run local commands cannot install this server. Give the user this guide to open in a local coding agent instead.

Ask which network the user wants. Use **testnet** unless they explicitly choose real-money use on **mainnet**. PAY on testnet has no monetary value. On mainnet, funding asks and other paid actions use real money.

## 2. Add the local MCP server

The working server package is `@ixo/openhands-mcp@1`. This package name and the environment key below are retained for compatibility. Use these technical identifiers exactly; IXO is the marketplace name.

Check the client's existing MCP configuration first. Reuse an existing equivalent server rather than creating a duplicate, and preserve unrelated configuration. The server name `ixo` below is a local configuration alias.

### Claude Code

For testnet:

```sh
claude mcp add ixo --env NEXT_PUBLIC_CHAIN_NETWORK=testnet -- npx -y @ixo/openhands-mcp@1
```

For mainnet, only after the user has chosen real-money use:

```sh
claude mcp add ixo --env NEXT_PUBLIC_CHAIN_NETWORK=mainnet -- npx -y @ixo/openhands-mcp@1
```

### Codex

Merge this entry into `~/.codex/config.toml` for testnet:

```toml
[mcp_servers.ixo]
command = "npx"
args = ["-y", "@ixo/openhands-mcp@1"]
env = { NEXT_PUBLIC_CHAIN_NETWORK = "testnet" }
```

For mainnet, change the environment value to `mainnet` only after the user chooses real-money use.

### Other local MCP clients

Use the client's documented configuration location with command `npx`, arguments `["-y", "@ixo/openhands-mcp@1"]`, and environment `NEXT_PUBLIC_CHAIN_NETWORK=testnet`. Set the environment value to `mainnet` only for explicitly chosen real-money use.

## 3. Restart and connect

Start a new coding agent session so the MCP tools load. Call `my_status` to check the active network, account and balance. Then call `connect_account` and show the user the connection link it returns. The user opens that link and approves the connection and its limits. Do not approve it on their behalf or claim the account is connected before checking the result.

The runtime may still return legacy service names or connection URLs. Retain those returned technical values; do not substitute an invented IXO endpoint. Never request seed phrases or private keys in chat.

## 4. Continue for the user's role

### Agent or app builder

Help the user describe the agent version, intended users, review scenarios, required specialist experience, evidence and access, acceptance criteria, deadline, follow-up, permitted use and the payment they want to offer. Show the complete proposed ask, payment, network and terms. Use `post_ask` only after the user approves the final details and any required funding. Follow the live tool's preview and confirmation requirements.

### Human specialist

Ask about the user's field, experience, qualifications, relevant users and tasks, availability, and the scope and payment terms they will consider. Use `list_asks` to find possible work and `read_ask` to inspect each ask's full requirements. Present suitable asks with their payment, acceptance criteria, deadline, follow-up and permitted use. Do not invent qualifications or imply that suitable asks are guaranteed to be available.

Help prepare a response that accurately represents the specialist's experience. The specialist conducts the review and supplies the observations and professional judgement; the agent helps organise evidence and prepare the submission. Get the user's approval before accepting work, sharing personal information, submitting a response through `submit_work` or publishing findings. Use `check_verdict` to inspect a submitted response's result when relevant.

## Approval and payment

Copying a setup prompt does not post an ask, accept work or authorise a payment. Inspect each live tool's schema and returned requirements before acting. Preview the exact action and total, and obtain the user's approval before committing funds. Do not treat account connection or a spending cap as blanket permission for every action. Confirm outcomes from returned tool results.