MCP connections: initialization, tool discovery, and host setup

An MCP connection has a sequence that should be observable: the host loads a server definition, initializes the session, discovers capabilities and tool schemas, and only then invokes a bounded tool. The SUIBROKERS participant kit is a concrete example. It contains a read-only server, four skills, a participant AGENTS.md template, and a downloadable ZIP. Its tools expose status, history, season, Desk, Partner, and action preparation; they do not quote, build, sign, or send a transaction.

HTTP connection examples

For a Codex CLI host, the kit README documents this HTTP command:

codex mcp add suibrokers --url https://suibrokers.com/api/agents/mcp

For Claude Code, the kit README documents this HTTP form:

claude mcp add --transport http suibrokers https://suibrokers.com/api/agents/mcp

These commands add a remote MCP definition to the named host. They do not connect a wallet or authorise a transaction. The remote endpoint is usable only when the corresponding deployment and host support are available. Hosted ChatGPT Work follows its own plugin and remote-MCP connection path; it does not read a local Codex configuration automatically. ChatGPT web also should not be described as automatically reading a local AGENTS.md.

Local stdio installation

Extract the ZIP into a directory you control, install its pinned dependencies, and keep the extracted path in a shell variable:

PARTICIPANT_DIR="$PWD"
KIT_DIR="$PARTICIPANT_DIR/suibrokers-agent-kit"
test ! -e "$KIT_DIR" || { echo "Refusing to replace existing kit directory: $KIT_DIR" >&2; exit 1; }
mkdir "$KIT_DIR"
unzip ./agent-kit.zip -d "$KIT_DIR"
cd "$PARTICIPANT_DIR"
npm ci --prefix "$KIT_DIR"

The package entry is server.mjs. Codex CLI uses:

codex mcp add suibrokers-local --env API_SUIBROKERS_URL=https://suibrokers.com -- node "$KIT_DIR/server.mjs"

Claude Code uses:

claude mcp add --transport stdio --env API_SUIBROKERS_URL=https://suibrokers.com suibrokers-local -- node "$KIT_DIR/server.mjs"

Choose the real extracted path; do not overwrite an existing skill or AGENTS.md. API_SUIBROKERS_URL may point to the exact production, staging, or loopback origin used for the walkthrough. These commands start the review-only server and do not grant wallet authority.

The package's local protocol tests cover its spawned stdio and MCP paths; registration with a particular installed Codex or Claude CLI remains host-specific.

Check what the server actually exposes

After the host reports a connection, inspect the available tool names and parameters. The packaged server exposes:

• suibrokers_get_status for raw API status and current service state;
• suibrokers_get_season with an integer stage from 1 through 4, optional wallet, and limit;
• suibrokers_get_swap_history with wallet, limit, cursor, and optional digest;
• suibrokers_get_desk with optional wallet and history range;
• suibrokers_get_partner with wallet and limit;
• suibrokers_prepare_action with swap, desk_deposit, desk_withdraw, partner, or points, plus optional wallet and amount; swap may also provide assets {from, to}.

Preparation should return a proposed action, an actual SUIBROKERS app URL, or a checklist. A quote is reviewed in the app. The tool must not be presented as a signing or execution channel.

The verification boundary

A successful connection only proves tool availability. It does not produce Points. The user still checks the Sui mainnet wallet, action, asset, amount, output, fee, gas, slippage, and signing prompt in the app. Then the chain transaction must confirm and the service must verify eligible activity. Use history, Desk state, Partner state, and season data to label confirmed, pending, failed, estimated, and unavailable states separately.

Current Swap and The Desk do not require the planned SUIBROKERS token. Thresholds do not guarantee NFT allocation or a live mint.

Kit references

The package references are the participant kit README, downloadable kit, user AGENTS.md template, Swap skill, Desk skill, Partners skill, and Progress skill.

Sources

• ChatGPT MCP guide
• Claude MCP guide
• MCP introduction
• SUIBROKERS agent docs

The connection is ready only when the host reports the expected server and schemas. A successful initialization proves tool availability, not wallet authority or transaction completion. Use MCP for the documented read or preparation surface, then move to the product UI for quote review, signing, and confirmed evidence.