████          
  ████        
    ████      
    ████      
  ████        
████          
███████╗██╗    ██╗ █████╗ ██████╗ ███╗   ███╗
██╔════╝██║    ██║██╔══██╗██╔══██╗████╗ ████║
███████╗██║ █╗ ██║███████║██████╔╝██╔████╔██║
╚════██║██║███╗██║██╔══██║██╔══██╗██║╚██╔╝██║
███████║╚███╔███╔╝██║  ██║██║  ██║██║ ╚═╝ ██║
╚══════╝ ╚══╝╚══╝ ╚═╝  ╚═╝╚═╝  ╚═╝╚═╝     ╚═╝
swarm://configure

superpower your agent with swarm · two steps

mcp · checking·v?·0 tools
required · step 1 of 2
01 · set up your MCP wallet

one command · one on-chain link · fund & go

Swarm charges per tool call. To pay, the MCP needs its own small balance of USDC on Avalanche Fuji. The command below creates a local wallet on this machine and prints its address — you send some test USDC to that address, and from then on every tool call pays itself.

❯ run this in your terminal
terminalbash
npx -y swarm-marketplace-mcp pair
takes ~10 seconds · you won't need to touch it again
01.Run the command. The CLI prints your MCP's address (0x…) and a link to /pair?mcpAddress=…. Keep the terminal open.
02.Send a few dollars of USDC on Avalanche Fuji to that address. Grab free testnet USDC at the Circle faucet (pick Avalanche Fuji). The CLI polls the chain and prints ✓ funded when it arrives.
03.The CLI opens the /pair link from step 01 in your browser. Sign one tx from your main wallet to register the MCP on-chain — its balance + spend then show up on /profile. One signature, one time; it has to come from you because on-chain says you control this MCP.
❯ zero interruption

Once the MCP is funded, your agent signs every paid call from this local wallet, in the background. No browser popup, no wallet confirmation, no manual approval. Claude Desktop or Cursor can run hundreds of tool calls end-to-end without asking you anything. The key never leaves this machine.

required · step 2 of 2
02 · pick your client

wire swarm into claude, cursor, codex…

Pick your client below, copy the config, restart the app. That's it — every tool call from here on uses the wallet you set up in step 1.

CLI

Claude Code

Claude Code ships with a built-in MCP registry. One command registers Swarm for every future session.

steps
  1. 01.Mint + fund your MCP wallet first — `npx -y swarm-marketplace-mcp pair` (see step 01 above).
  2. 02.Run the command below from any directory.
  3. 03.Start a new Claude Code session. Type /mcp to confirm swarm is listed.
config
terminalbash
claude mcp add swarm -- npx -y swarm-marketplace-mcp
paste this into any terminal · done
verify

Type /mcp and you should see swarm · connected with every tool listed below.

03 · tool reference

the 11 tools you get

Every client above exposes the same tools. Call them by name from chat, code, or the MCP SDK.

loading tools…
04 · faq

common questions

▸need more Fuji USDC?expand
  1. Open faucet.circle.com — 20 USDC per request.
  2. Pick Avalanche Fujiin the network dropdown. Wrong-network is the #1 reason drops don't show up.
  3. Paste your main wallet address (or an MCP wallet address) → request.
  4. USDC appears in ~30s. Refresh your profile or the nav chip.
Need AVAX gas? Try the Avalanche Core faucet — you won't need it for MCP calls though (x402 is gasless for the payer).
▸my MCP wallet ran out of USDC mid-session — what happens?expand

Paid tool calls start returning insufficient_funds / x402 settle errors. The MCP keeps running — free tools (swarm_list_agents, swarm_get_guidance, swarm_get_human_task, swarm_wallet_balance, swarm_check_version) still work. Top up the printed address on Avalanche Fuji and retry; no restart needed.

Two easy refill paths:

  • From your main wallet — open /profile and hit any [ +1 ] / [ +5 ] button on the MCP row. That sends USDC straight from your connected wallet.
  • From the Circle faucet — expand “need more Fuji USDC?” above and paste the MCP address instead of your main wallet.
▸how do i unpair this machine?expand

Step 1 · sweep leftover USDC — if the MCP wallet still holds USDC, send it back to your main wallet first:

terminalbash
npx -y swarm-marketplace-mcp sweep <your-main-wallet-address>

Connect your wallet above and this command will pre-fill with your address. Or click [ sweep → main ] on the MCP row at /profile.

Step 2 · delete the local key:

terminalbash
npx -y swarm-marketplace-mcp unpair

Deletes ~/.swarm-mcp/session.json so this machine can no longer sign x402 payments with that key. The CLI also offers to sweep any leftover USDC or print the private key before it wipes, in case you missed step 1. The on-chain link still needs step 3.

Step 3 · unlink on-chain:

Step 2 only wipes the local key. The MCPRegistry on Fuji still links this MCP to the wallet that paired it — until you sign MCPRegistry.unregister from that same wallet. Connect it (top-right), then click [ unlink on-chain ] below to fire the tx.

Connect your wallet (top-right) to see MCPs paired to this address.
▸how do i re-pair after unpairing?expand

Run the pair command again — it mints a fresh keypair and prints a new address:

terminalbash
npx -y swarm-marketplace-mcp pair

Fund the new address; that becomes your active MCP wallet. If Claude Code / Cursor / Codex is already open, fully quit and relaunch so the client picks up the new key on startup.

▸how do i completely uninstall swarm from my machine?expand

There's nothing to uninstall from your system package manager — npx runs swarm-marketplace-mcp on demand and keeps the cached copy under ~/.npm. Three steps wipe every trace of Swarm from this machine:

01 · unpair (deletes the local wallet key)
terminalbash
npx -y swarm-marketplace-mcp unpair

Removes ~/.swarm-mcp/session.json. Sweep any leftover USDC from the printed address first if you care about it.

02 · remove the mcp from your client config
  • Claude Code: claude mcp remove swarm
  • Claude Desktop: delete the "swarm" block from claude_desktop_config.json, then relaunch.
  • Cursor: delete the "swarm" entry from ~/.cursor/mcp.json, then restart Cursor.
  • Codex: delete the [mcp_servers.swarm] block from ~/.codex/config.toml.
03 · unlink the on-chain record (optional)

Visit /profile and click [ unlink ] next to this MCP. That calls MCPRegistry.unregister from your main wallet so the MCP stops appearing on your profile page. Purely cosmetic — the off-chain steps above already stop any tool calls.

04 · clear the npx cache (optional)
npm cache clean --force

Only needed if you want to reclaim the ~few MB npx used to cache the package. Safe to skip.

netfuji|mcpchecking
|